summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2012-10-22 15:05:49 +0100
committerSimon MacMullen <simon@rabbitmq.com>2012-10-22 15:05:49 +0100
commit1400865c9a9b996b9137953ed882fc41d7c0dc64 (patch)
treee5ff9d19a3222065b5c37359497d3773f684ae59 /docs
parent3cd89a4583d5e06d8a6cd08f50512736aa66e96b (diff)
downloadrabbitmq-server-1400865c9a9b996b9137953ed882fc41d7c0dc64.tar.gz
s/key/name/, and a couple of other minor tidyups that I noticed at the same time.bug25142
Diffstat (limited to 'docs')
-rw-r--r--docs/rabbitmqctl.1.xml34
1 files changed, 17 insertions, 17 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index 522a51ee..53411d8b 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -806,8 +806,8 @@
Certain features of RabbitMQ (such as the federation plugin)
are controlled by dynamic,
cluster-wide <emphasis>parameters</emphasis>. Each parameter
- consists of a component name, a key and a value, and is
- associated with a virtual host. The component name and key are
+ consists of a component name, a name and a value, and is
+ associated with a virtual host. The component name and name are
strings, and the value is an Erlang term. Parameters can be
set, cleared and listed. In general you should refer to the
documentation for the feature in question to see how to set
@@ -815,7 +815,7 @@
</para>
<variablelist>
<varlistentry>
- <term><cmdsynopsis><command>set_parameter</command> <arg choice="opt">-p <replaceable>vhostpath</replaceable></arg> <arg choice="req"><replaceable>component_name</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg> <arg choice="req"><replaceable>value</replaceable></arg></cmdsynopsis></term>
+ <term><cmdsynopsis><command>set_parameter</command> <arg choice="opt">-p <replaceable>vhostpath</replaceable></arg> <arg choice="req"><replaceable>component_name</replaceable></arg> <arg choice="req"><replaceable>name</replaceable></arg> <arg choice="req"><replaceable>value</replaceable></arg></cmdsynopsis></term>
<listitem>
<para>
Sets a parameter.
@@ -829,24 +829,24 @@
</para></listitem>
</varlistentry>
<varlistentry>
- <term>key</term>
+ <term>name</term>
<listitem><para>
- The key for which the parameter is being set.
+ The name of the parameter being set.
</para></listitem>
</varlistentry>
<varlistentry>
<term>value</term>
<listitem><para>
- The value for the parameter, as an
- Erlang term. In most shells you are very likely to
+ The value for the parameter, as a
+ JSON term. In most shells you are very likely to
need to quote this.
</para></listitem>
</varlistentry>
</variablelist>
<para role="example-prefix">For example:</para>
- <screen role="example">rabbitmqctl set_parameter federation local_username '&lt;&lt;"guest">>'</screen>
+ <screen role="example">rabbitmqctl set_parameter federation local_username '"guest"'</screen>
<para role="example">
- This command sets the parameter <command>local_username</command> for the <command>federation</command> component in the default virtual host to the Erlang term <command>&lt;&lt;"guest">></command>.
+ This command sets the parameter <command>local_username</command> for the <command>federation</command> component in the default virtual host to the JSON term <command>"guest"</command>.
</para>
</listitem>
</varlistentry>
@@ -865,9 +865,9 @@
</para></listitem>
</varlistentry>
<varlistentry>
- <term>key</term>
+ <term>name</term>
<listitem><para>
- The key for which the parameter is being cleared.
+ The name of the parameter being cleared.
</para></listitem>
</varlistentry>
</variablelist>
@@ -899,19 +899,19 @@
<para>
Policies are used to control and modify the behaviour of queues
and exchanges on a cluster-wide basis. Policies apply within a
- given vhost, and consist of a key, pattern, definition and an
+ given vhost, and consist of a name, pattern, definition and an
optional priority. Policies can be set, cleared and listed.
</para>
<variablelist>
<varlistentry>
- <term><cmdsynopsis><command>set_policy</command> <arg choice="opt">-p <replaceable>vhostpath</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg> <arg choice="req"><replaceable>pattern</replaceable></arg> <arg choice="req"><replaceable>definition</replaceable></arg> <arg choice="opt"><replaceable>priority</replaceable></arg> </cmdsynopsis></term>
+ <term><cmdsynopsis><command>set_policy</command> <arg choice="opt">-p <replaceable>vhostpath</replaceable></arg> <arg choice="req"><replaceable>name</replaceable></arg> <arg choice="req"><replaceable>pattern</replaceable></arg> <arg choice="req"><replaceable>definition</replaceable></arg> <arg choice="opt"><replaceable>priority</replaceable></arg> </cmdsynopsis></term>
<listitem>
<para>
Sets a policy.
</para>
<variablelist>
<varlistentry>
- <term>key</term>
+ <term>name</term>
<listitem><para>
The name of the policy.
</para></listitem>
@@ -926,7 +926,7 @@
<term>definition</term>
<listitem><para>
The definition of the policy, as a
- JSON string. In most shells you are very likely to
+ JSON term. In most shells you are very likely to
need to quote this.
</para></listitem>
</varlistentry>
@@ -945,14 +945,14 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><cmdsynopsis><command>clear_policy</command> <arg choice="opt">-p <replaceable>vhostpath</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg></cmdsynopsis></term>
+ <term><cmdsynopsis><command>clear_policy</command> <arg choice="opt">-p <replaceable>vhostpath</replaceable></arg> <arg choice="req"><replaceable>name</replaceable></arg></cmdsynopsis></term>
<listitem>
<para>
Clears a policy.
</para>
<variablelist>
<varlistentry>
- <term>key</term>
+ <term>name</term>
<listitem><para>
The name of the policy being cleared.
</para></listitem>