summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrancesco Mazzoli <francesco@rabbitmq.com>2012-08-21 18:23:33 +0100
committerFrancesco Mazzoli <francesco@rabbitmq.com>2012-08-21 18:23:33 +0100
commit40a804ceefa01a1931501c9b20b6d1a639af9805 (patch)
tree6d526c4c107af40999b57604f591f1006a33d8f8
parent7a0ca3ef325035d83133ed07234d63d25b3d7ec0 (diff)
downloadrabbitmq-server-40a804ceefa01a1931501c9b20b6d1a639af9805.tar.gz
more manpage fixes
-rw-r--r--docs/rabbitmqctl.1.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index ae39effa..720df077 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -321,7 +321,7 @@
have at least one disk node. Note that the queue data will always
be on disc, including on ram nodes. This makes ram nodes more
performant only when managing resources (e.g. adding/removing
- queues, exhanges, or bindings).
+ queues, exchanges, or bindings).
</para>
<para>
The node will be a disk node by default. If you wish to wish to
@@ -444,7 +444,7 @@
<term>clusternode</term>
<listitem>
<para>
- The node to update_cluster_nodes with.
+ The node to consult for up to date information.
</para>
</listitem>
</varlistentry>
@@ -462,8 +462,8 @@
which node A and B are clustered. A goes down, C clusters with C,
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 this
- situation.
+ anymore. <command>update_cluster_nodes -n A C</command> will solve
+ this situation.
</para>
</listitem>
</varlistentry>