added Why to report section.

(Logical change 1.315)


git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1283 ce84e21b-d406-0410-9b95-82705330c041

1 files changed, 16 insertions, 8 deletions

diff --git a/doc/reports.xml b/doc/reports.xml
index 9f9a46516..76f609fb8 100644
--- a/doc/reports.xml
+++ b/doc/reports.xml
@@ -50,14 +50,22 @@
 </section>
 
   <section>
-    <title>Concepts -- Why to report, big picture</title>
+    <title>Concepts; Why to report</title>
 
-    <para>So you'll recive a report-- however you might get it--and
-      it'll contain any sort of info, like general net health, or specific
-      node broken packages, or... whatever. You choose. This will help you
-      correct your configuratin file, and audit things, and fix any nodes
-      that got all hosed.
-    </para>
+    <para>Reports play an important role in effectively managing systems
+      with BCFG. There are two primary functions they fulfill; providing 
+      otherwise unobtainable information, and presenting additional
+      helpful information to allow for easier admistration. Reports
+      can contain information including system statistics, discrepancies
+      between specified and actual configuration, invalid configuration,
+      and auditing information among other things.</para>
+
+    <para>The flexible XML configuration file allows reports to be configured
+      to deliver only the information that is important. Additional reports 
+      can easily be created, providing site-specific capability to manage
+      at record effiency. The capability to harvest information regarding
+      statistics, configuration, and problems in a single location should
+      prove to be powerful.</para>
   </section>
 
   <section>
@@ -172,7 +180,7 @@
       </varlistentry>
     </variablelist>
 
-    <para>Here is a list of possible delivery mechanisms.</para>
+    <para>A list of delivery mechanisms follows:</para>
 
     <variablelist>
       <varlistentry>