[system-administrators-guide] refer to >> see

stephenw stephenw at fedoraproject.org
Tue Jul 29 07:08:57 UTC 2014


commit 6255556ba3f5b38e5fc4a9594f59ed9ed29fd5ec
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Tue Jul 29 09:08:06 2014 +0200

    refer to >> see

 en-US/Working_with_Kernel_Modules.xml |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)
---
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index 6988ab4..800b813 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -46,7 +46,7 @@
     <para>In order to use the kernel module utilities described in this chapter, first ensure the <package>kmod</package> package is installed on your system by running, as root:</para>
     <screen>~]#&nbsp;<command>yum install kmod</command>
     </screen>
-    <para>For more information on installing packages with Yum, refer to <xref
+    <para>For more information on installing packages with Yum, see <xref
         linkend="sec-Installing"/>.</para>
   </note>
   <section
@@ -112,7 +112,7 @@ kvm                   253162  1 kvm_intel
         <para>the amount of memory it uses; and,</para>
       </listitem>
       <listitem>
-        <para>the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, refer to <xref
+        <para>the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, see <xref
             linkend="sec-Unloading_a_Module"/>.</para>
       </listitem>
     </itemizedlist>
@@ -336,7 +336,7 @@ insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</scree
             class="resource">wacom</systemitem>, through the dependency tree, depends on indirectly.</para>
       </listitem>
     </itemizedlist>
-    <para>Refer to <xref linkend="sec-Listing_Currently-Loaded_Modules"/> for more information about using <command>lsmod</command> to obtain the names of the modules which are preventing you from unloading a certain module.</para>
+    <para>See <xref linkend="sec-Listing_Currently-Loaded_Modules"/> for more information about using <command>lsmod</command> to obtain the names of the modules which are preventing you from unloading a certain module.</para>
     <example id="ex-unloading_a_kernel_module">
       <title>Unloading a kernel module</title>
       <para>For example, if you want to unload the <systemitem class="resource">firewire_ohci</systemitem> module (because you believe there is a bug in it that is affecting system stability, for example), your terminal session might look similar to this:</para>
@@ -430,7 +430,7 @@ rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</screen>
       </step>
       <step
         id="proc-step2-Loading_a_Kernel_Module_with_Custom_Parameters">
-        <para>Load the module and list all custom parameters after the module name. For example, if you wanted to load the Intel PRO/1000 network driver with   the interrupt throttle rate set to 3000 interrupts per second for the first, second and third instances of the driver, and Energy Efficient Ethernet (EEE) turned on<footnote
+        <para>Load the module and list all custom parameters after the module name. For example, if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate set to 3000 interrupts per second for the first, second and third instances of the driver, and Energy Efficient Ethernet (EEE) turned on<footnote
             id="footnote-Energy_Efficient_Ethernet"><para>Despite what the example might imply, Energy Efficient Ethernet is turned on by default in the <systemitem
                 class="resource">e1000e</systemitem> driver.</para>
           </footnote>
@@ -486,7 +486,7 @@ fi</programlisting>
   <section
     id="s1-kernel-modules-additional-resources">
     <title>Additional Resources</title>
-    <para>For more information on kernel modules and their utilities, refer to the following resources.</para>
+    <para>For more information on kernel modules and their utilities, see the following resources.</para>
     <section id="s2-kernel-modules-additional-resources-installed">
       <title>Installed Documentation</title>
       <para>There are a number of manual pages for various utilities related to kernel modules:</para>
@@ -556,7 +556,7 @@ fi</programlisting>
 <section
     id="sec-Setting_Module_Parameters">
     <title>Setting Module Parameters</title>
-    <para>This section lists modules used for a common hardware, and their respective parameters. Refer to <xref
+    <para>This section lists modules used for a common hardware, and their respective parameters. See <xref
         linkend="s2-kernel-module-utils-modprobe" /> for information on how to load them to the running kernel, and <xref
         linkend="s2-kernel-modules-persistent" /> for instructions on how to load them automatically at boot time. Note that to view parameters for a certain module, you can use the <command>modinfo</command> command as described in <xref
         linkend="sec-Displaying_Information_About_a_Module" />.</para>
@@ -856,7 +856,7 @@ fi</programlisting>
         <primary>kernel module</primary>
         <secondary>NIC module</secondary>
       </indexterm>
-      <para>The preferred way to configure most modern Ethernet-based network interface cards (NICs) is to use <command>ethtool</command> or <command>mii-tool</command>. Only after these tools fail to work should module parameters be adjusted. Refer to manual pages for <command>ethtool</command> and <command>mii-tool</command> for more information on their usage.</para>
+      <para>The preferred way to configure most modern Ethernet-based network interface cards (NICs) is to use <command>ethtool</command> or <command>mii-tool</command>. Only after these tools fail to work should module parameters be adjusted. See manual pages for <command>ethtool</command> and <command>mii-tool</command> for more information on their usage.</para>
       <table
         id="tb-modules-ethernet">
         <title>Ethernet Module Parameters</title>


More information about the docs-commits mailing list