LUDOC-387 rpc: fix typo in max_rpcs_in_flight

This is a trivial patch that fixes the following two
lctl set_param examples:
client$ lctl set_param mdc.*.max_rpcs_in_flight=16
client$ lctl set_param mdc.*.max_mod_rpcs_in_flight=12

Signed-off-by: Joseph Gmitter <joseph.gmitter@intel.com>
Change-Id: If0ac0b1a99be8f13a702d1f7f2a8e28b48ea223b
Reviewed-on: https://review.whamcloud.com/28327
Tested-by: Jenkins

diff --git a/LustreProc.xml b/LustreProc.xml
index a5916a0..e52b1f6 100644 (file)
--- a/LustreProc.xml
+++ b/LustreProc.xml
@@ -1544,7 +1544,7 @@ obdfilter.lol-OST0001.sync_on_lock_cancel=never</screen>
           minimum setting is 1 and maximum setting is 256.</para>
         <para>To set the <literal>max_rpcs_in_flight</literal> parameter, run
           the following command on the Lustre client:</para>
-        <screen>client$ lctl set_param mdc.*.max_rcps_in_flight=16</screen>
+        <screen>client$ lctl set_param mdc.*.max_rpcs_in_flight=16</screen>
         <para>The MDC <literal>max_mod_rpcs_in_flight</literal> parameter
           defines the maximum number of file system modifying RPCs that can be
           sent in parallel by a client to a MDT target. For example, the Lustre
@@ -1554,7 +1554,7 @@ obdfilter.lol-OST0001.sync_on_lock_cancel=never</screen>
           256.</para>
         <para>To set the <literal>max_mod_rpcs_in_flight</literal> parameter,
           run the following command on the Lustre client:</para>
-        <screen>client$ lctl set_param mdc.*.max_mod_rcps_in_flight=12</screen>
+        <screen>client$ lctl set_param mdc.*.max_mod_rpcs_in_flight=12</screen>
         <para>The <literal>max_mod_rpcs_in_flight</literal> value must be
           strictly less than the <literal>max_rpcs_in_flight</literal> value.
           It must also be less or equal to the MDT