[deployment-guide/comm-rel: 349/727] minor modification in ABRT chapter

[Jaromir Hradilek]

commit 9b9bc7de76fe17bd5d287c98b4b11d9048d1cf75
Author: Martin Prpic <mprpic at redhat.com>
Date:   Thu Aug 12 15:34:43 2010 +0200

    minor modification in ABRT chapter

 en-US/ABRT.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/ABRT.xml b/en-US/ABRT.xml
index 3813fb3..6b8c8d8 100644
--- a/en-US/ABRT.xml
+++ b/en-US/ABRT.xml
@@ -205,7 +205,7 @@ Starting abrt daemon:                                      [  OK  ]</screen>
     </variablelist>
     <variablelist>
       <title>[ AnalyzerActionsAndReporters ] Section Directives</title>
-      <para>This section allows you to associate certain analyzer actions and reporter actions to run when <application>ABRT</application> catches kernel oopses or crashes in C, C++ or Python programs. The actions and reporters specified in any of the directives below will run only if you run <command>abrt-gui</command> or <command>abrt-cli</command> and report the crash that occurred. If you do not specify any actions and reporters in these directives, you will not be able to report a crash via <command>abrt-gui</command> or <command>abrt-cli</command>. The order of actions and reporters is important.</para>
+      <para>This section allows you to associate certain analyzer actions and reporter actions to run when <application>ABRT</application> catches kernel oopses or crashes in C, C++ or Python programs. The actions and reporters specified in any of the directives below will run only if you run <command>abrt-gui</command> or <command>abrt-cli</command> and report the crash that occurred. If you do not specify any actions and reporters in these directives, you will not be able to report a crash via <command>abrt-gui</command> or <command>abrt-cli</command>. The order of actions and reporters is important. Commenting out a directive, will cause <application>ABRT</application> not to catch the crashes associated with that directive. For example, commenting out the Kerneloops line will cause <application>ABRT</application> not to catch kernel oopses.</para>
       <varlistentry>
         <term>Kerneloops = TicketUploader, Bugzilla</term>
         <listitem>