Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct typos in documentation #1065

Merged
merged 1 commit into from
Oct 17, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Sources/DistributedActors/Docs.docc/Clustering.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,11 +55,11 @@ Forming a cluster is the first step towards making use of distributed clusters a

Once a node joins at least one other node of an already established cluster, it will receive information about all other nodes
which participate in this cluster. This is why often it is not necessary to give all nodes the information about all other nodes in a cluster,
but only attempt to join one or a few o them. The first join "wins" and the cluster welcome the new node into the ``Cluster/Membership``.
but only attempt to join one or a few of them. The first join "wins" and the cluster welcome the new node into the ``Cluster/Membership``.

### Joining existing nodes

In the simplest scenario we already about some existing node that we can join to form a cluster, or become part of a cluster that node already is in.
In the simplest scenario we already know about some existing node that we can join to form a cluster, or become part of a cluster that node already is in.

This is done using the system's ``ClusterControl`` object, like this:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ import Logging
/// A _cluster singleton_ is a conceptual distributed actor that is guaranteed to have at-most one
/// instance within the cluster system among all of its ``Cluster/MemberStatus/up`` members.
///
/// > Note: This guarantee does not extend to _down_ members, because a down member is not part of the cluster anymore, and
/// > Note: This guarantee does not extend to _down_ members, because a down member is not part of the cluster anymore.
///
/// To create a managed singleton you must use the ``ClusterSingletonPlugin``,
/// and have the instantiation and lifecycle of the actor be managed by the plugin.
Expand Down