[deployment-guide/comm-rel: 270/727] Fixed the spelling of the `crash' utility.

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 12:47:16 UTC 2010


commit 77515939a08db62708e4cb24acf1781a2a745c50
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Aug 6 13:00:25 2010 +0200

    Fixed the spelling of the `crash' utility.

 en-US/The_kdump_Crash_Recovery_Service.xml |   26 +++++++++++++-------------
 1 files changed, 13 insertions(+), 13 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index b007406..ad04d9b 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -7,7 +7,7 @@
     <systemitem class="service">kdump</systemitem> is an advanced crash dumping mechanism. When enabled, the system is booted from the context of another kernel. This second kernel reserves a small amount of memory, and its only purpose is to capture the core dump image in case the system crashes. Since being able to analyze the core dump helps significantly to determine the exact cause of the system failure, it is strongly recommended to have this feature enabled.
   </para>
   <para>
-    This chapter explains how to configure, test, and use the <systemitem class="service">kdump</systemitem> service in &MAJOROS;, and provides a brief overview of how to analyze the resulting core dump using the <application>Crash</application> debugging utility.
+    This chapter explains how to configure, test, and use the <systemitem class="service">kdump</systemitem> service in &MAJOROS;, and provides a brief overview of how to analyze the resulting core dump using the <application>crash</application> debugging utility.
   </para>
   <section id="s1-kdump-configuration">
     <title>Configuring the <systemitem class="service">kdump</systemitem> Service</title>
@@ -526,10 +526,10 @@ Kdump is operational</screen>
     <indexterm>
       <primary><systemitem class="service">kdump</systemitem></primary>
       <secondary>analyzing the dump</secondary>
-      <see><application>Crash</application></see>
+      <see><application>crash</application></see>
     </indexterm>
     <indexterm>
-      <primary><application>Crash</application></primary>
+      <primary><application>crash</application></primary>
       <secondary>system requirements</secondary>
     </indexterm>
     <note>
@@ -543,10 +543,10 @@ Kdump is operational</screen>
       </para>
     </note>
     <para>
-      To determine the cause of the system crash, you can use the <application>Crash</application> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
+      To determine the cause of the system crash, you can use the <application>crash</application> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
     </para>
     <indexterm>
-      <primary><application>Crash</application></primary>
+      <primary><application>crash</application></primary>
       <secondary>opening the dump image</secondary>
     </indexterm>
     <para>
@@ -605,12 +605,12 @@ LOAD AVERAGE: 0.64, 0.27, 0.12
 crash&gt;</screen>
     </example>
     <para>
-      To exit the interactive prompt and terminate <application>Crash</application>, type <command>exit</command>.
+      To exit the interactive prompt and terminate <application>crash</application>, type <command>exit</command>.
     </para>
     <section id="s2-kdump-crash-log">
       <title>Displaying the Message Buffer</title>
       <indexterm>
-        <primary><application>Crash</application></primary>
+        <primary><application>crash</application></primary>
         <secondary>analyzing the dump</secondary>
         <tertiary>message buffer</tertiary>
       </indexterm>
@@ -652,7 +652,7 @@ CR2: 0000000000000000</screen>
     <section id="s2-kdump-crash-backtrace">
       <title>Displaying a Backtrace</title>
       <indexterm>
-        <primary><application>Crash</application></primary>
+        <primary><application>crash</application></primary>
         <secondary>analyzing the dump</secondary>
         <tertiary>stack trace</tertiary>
       </indexterm>
@@ -678,7 +678,7 @@ PID: 5108   TASK: ee939980  CPU: 0   COMMAND: "bash"
     <section id="s2-kdump-crash-processes">
       <title>Displaying a Process Status</title>
       <indexterm>
-        <primary><application>Crash</application></primary>
+        <primary><application>crash</application></primary>
         <secondary>analyzing the dump</secondary>
         <tertiary>processes</tertiary>
       </indexterm>
@@ -708,7 +708,7 @@ PID: 5108   TASK: ee939980  CPU: 0   COMMAND: "bash"
     <section id="s2-kdump-crash-memory">
       <title>Displaying Virtual Memory Information</title>
       <indexterm>
-        <primary><application>Crash</application></primary>
+        <primary><application>crash</application></primary>
         <secondary>analyzing the dump</secondary>
         <tertiary>virtual memory</tertiary>
       </indexterm>
@@ -751,7 +751,7 @@ eea68420   811d000   8122000 100073
     <section id="s2-kdump-crash-files">
       <title>Displaying Open Files</title>
       <indexterm>
-        <primary><application>Crash</application></primary>
+        <primary><application>crash</application></primary>
         <secondary>analyzing the dump</secondary>
         <tertiary>open files</tertiary>
       </indexterm>
@@ -818,7 +818,7 @@ ROOT: /    CWD: /root
           <term><command>man crash</command></term>
           <listitem>
             <para>
-              The manual page for the <application>Crash</application> utility containing the full documentation on its usage.
+              The manual page for the <application>crash</application> utility containing the full documentation on its usage.
             </para>
           </listitem>
         </varlistentry>
@@ -852,7 +852,7 @@ ROOT: /    CWD: /root
           <term><ulink url="http://people.redhat.com/anderson/" /></term>
           <listitem>
             <para>
-              The <application>Crash</application> utility homepage.
+              The <application>crash</application> utility homepage.
             </para>
           </listitem>
         </varlistentry>


More information about the docs-commits mailing list