[deployment-guide/comm-rel: 215/727] Minor correction.

[Jaromir Hradilek]

commit 9504e13470c8e5eb08525ad816095fc675b88f39
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 2 12:53:15 2010 +0200

    Minor correction.

 en-US/The_kdump_Crash_Recovery_Service.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index ace894e..b7873c0 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -161,7 +161,7 @@ Password:</screen>
       <section id="s3-kdump-configuration-cli-target">
         <title>Configuring the Target Type</title>
         <para>
-          When the kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Note that only one of these options can be set at the moment. The default option is to store the <filename>vmcore</filename> file in the <filename class="directory">/var/crash/</filename> directory of the local file system.
+          When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Note that only one of these options can be set in the <filename>/etc/kdump.conf</filename> at the moment. The default option is to store the <filename>vmcore</filename> file in the <filename class="directory">/var/crash/</filename> directory of the local file system.
         </para>
         <para>
           To change the local directory in which the core dump is to be saved, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#path /var/crash</literal> line, and replace the value with a desired directory path. Optionally, if you wish to write the file to a different partition, follow the same procedure with the <literal>#ext4 /dev/sda3</literal> line as well, and change both the file system type and the device (a device name, a filesystem label, and UUID are all supported) accordingly. For example: