summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrancesco Mazzoli <francesco@rabbitmq.com>2012-09-05 12:50:03 +0100
committerFrancesco Mazzoli <francesco@rabbitmq.com>2012-09-05 12:50:03 +0100
commitb6cb093e42aaa53f1ffcf3f5fe7b4d54a7873274 (patch)
tree79dca3262219faa153f9a3718598d76d17f7cee0
parent7f1963c18af2952ba18826dcb0afeff17720c40e (diff)
downloadrabbitmq-server-git-b6cb093e42aaa53f1ffcf3f5fe7b4d54a7873274.tar.gz
typo in rabbitmqctl man page
-rw-r--r--docs/rabbitmqctl.1.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index 834e7b818e..b476f4865c 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -459,7 +459,7 @@
<para>
The need for this command is motivated by the fact that clusters
can change while a node is offline. Consider the situation in
- which node A and B are clustered. A goes down, C clusters with C,
+ which node A and B are clustered. A goes down, C clusters with B,
and then B leaves the cluster. When A wakes up, it'll try to
contact B, but this will fail since B is not in the cluster
anymore. <command>update_cluster_nodes -n A C</command> will solve