[deployment-guide: 117/185] Minor adjustments.

[Jaromir Hradilek]

commit 37e24a9262509014326e372d17aeb2a99e9a7ea4
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Mar 11 14:27:52 2011 +0100

    Minor adjustments.

 en-US/The_kdump_Crash_Recovery_Service.xml |   28 ++++++++++++++--------------
 1 files changed, 14 insertions(+), 14 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index b8b3513..abe6d38 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -21,7 +21,11 @@
     <note>
       <title>Note: Make Sure You Have <package>kexec-tools</package> Installed</title>
       <para>
-        To use the <systemitem class="service">kdump</systemitem> service, you must have the <package>kexec-tools</package> package installed. Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+        To use the <systemitem class="service">kdump</systemitem> service, you must have the <package>kexec-tools</package> package installed. To do so, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
+      </para>
+      <screen><command>yum install kexec-tools</command></screen>
+      <para>
+        For more information on how to install new packages in &MAJOROS;, refer to <xref linkend="sec-Installing" />.
       </para>
     </note>
     <section id="s2-kdump-configuration-firstboot">
@@ -266,10 +270,9 @@
     <section id="s2-kdump-configuration-cli">
       <title>Configuring <systemitem class="service">kdump</systemitem> on the Command Line</title>
       <para>
-        To perform actions described in this section, you have to be logged in as a superuser:
+        To perform actions described in this section, you have to be logged in as <systemitem class="username">root</systemitem>. To do so, run the following command:
       </para>
-      <screen>~]$ <command>su -</command>
-Password:</screen>
+      <screen><command>su -</command></screen>
       <section id="s3-kdump-configuration-cli-memory">
         <title>Configuring the Memory Usage</title>
         <indexterm>
@@ -527,7 +530,7 @@ path /usr/local/cores</screen>
         <para>
           To start the <systemitem class="service">kdump</systemitem> daemon at boot time, type the following at a shell prompt:
         </para>
-        <screen>~]# <command>chkconfig kdump on</command></screen>
+        <screen><command>chkconfig kdump on</command></screen>
         <para>
           This will enable the service for runlevels <literal>2</literal>, <literal>3</literal>, <literal>4</literal>, and <literal>5</literal>. Similarly, typing <command>chkconfig kdump off</command> will disable it for all runlevels. To start the service in the current session, use the following command:
         </para>
@@ -535,10 +538,7 @@ path /usr/local/cores</screen>
           <primary><systemitem class="service">kdump</systemitem></primary>
           <secondary>running the service</secondary>
         </indexterm>
-        <screen>~]# <command>service kdump start</command>
-No kdump initial ramdisk found.                            [WARNING]
-Rebuilding /boot/initrd-2.6.32-54.el6.i686kdump.img
-Starting kdump:                                            [  OK  ]</screen>
+        <screen><command>service kdump start</command></screen>
         <para>
           For more information on runlevels and configuring services in general, refer to <xref linkend="ch-Services_and_Daemons" />.
         </para>
@@ -557,15 +557,15 @@ Starting kdump:                                            [  OK  ]</screen>
         </para>
       </warning>
       <para>
-        To test the configuration, reboot the system with <systemitem class="service">kdump</systemitem> enabled, and make sure that the service is running (refer to <xref linkend="s1-services-running" /> for more information on how to run a service in &MAJOROS;):
+        To test the configuration, reboot the system with <systemitem class="service">kdump</systemitem> enabled, and make sure that the service is running (refer to <xref linkend="s1-services-running" /> for more information on how to run a service in &MAJOROS;). For example:
       </para>
       <screen>~]# <command>service kdump status</command>
 Kdump is operational</screen>
       <para>
         Then type the following commands at a shell prompt:
       </para>
-      <screen>~]# <command>echo 1 &gt; /proc/sys/kernel/sysrq</command>
-~]# <command>echo c &gt; /proc/sysrq-trigger</command></screen>
+      <screen><command>echo 1 &gt; /proc/sys/kernel/sysrq</command>
+<command>echo c &gt; /proc/sysrq-trigger</command></screen>
       <para>
         This will force the Linux kernel to crash, and the <filename><replaceable>address</replaceable>-<replaceable>YYYY-MM-DD</replaceable>-<replaceable>HH:MM:SS</replaceable>/vmcore</filename> file will be copied to the location you have selected in the configuration (that is, to <filename class="directory">/var/crash/</filename> by default).
       </para>
@@ -599,9 +599,9 @@ Kdump is operational</screen>
       <para>
         To analyze the <filename>vmcore</filename> dump file, you must have the <package>crash</package> and <package>kernel-debuginfo</package> packages installed. To do so, type the following at a shell prompt:
       </para>
-      <screen>~]# <command>yum install --enablerepo=rhel-debuginfo crash kernel-debuginfo</command></screen>
+      <screen><command>yum install --enablerepo=rhel-debuginfo crash kernel-debuginfo</command></screen>
       <para>
-        Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+        For more information on how to install new packages in &MAJOROS;, refer to <xref linkend="sec-Installing" />.
       </para>
     </note>
     <indexterm>