From 42e257c18ccdad28e7cc9baf87bc1a6d76cc4afa Mon Sep 17 00:00:00 2001
From: Alain Reguera Delgado <alain.reguera@gmail.com>
Date: Sep 19 2011 17:12:03 +0000
Subject: Update `Preface/feedback.docbook'.


---

diff --git a/Manuals/Tcar-ug/Preface/feedback.docbook b/Manuals/Tcar-ug/Preface/feedback.docbook
index f8054e4..842298e 100644
--- a/Manuals/Tcar-ug/Preface/feedback.docbook
+++ b/Manuals/Tcar-ug/Preface/feedback.docbook
@@ -3,24 +3,45 @@
     <title>Send In Your Feedback</title>
 
     <para>
-        When you find an error in &TCAR; we want to hear about it.  To
-        report the errors you find, the following mailing lists are
-        available for you to write:
+        When you find a bug in &TCAR; we want to hear about it.  The
+        following suggestions are intended to assist you in forming
+        bug reports that can be handled in an effective fashion. No
+        one is required to follow them but doing so tends to be to
+        everyone's advantage. 
     </para>
 
-    <itemizedlist>
-    <listitem>
     <para>
-        <ulink url="mailto:centos-artwork@centos.org">centos-artwork@centos.org</ulink>
+        We cannot promise to fix every error or implement every
+        feature right away. If a problem is obvious, critical, or
+        affects a lot of users, chances are good that someone will
+        look into it. It could also happen that we tell you to update
+        your working copy to a newer revision to see if the problem
+        happens there. Or we might decide that the problem cannot be
+        fixed before some major rewrite we might be planning is done.
+        Or perhaps it is simply too hard and there are more important
+        things on the agenda. If you need help immediately, consider
+        obtaining a commercial support contract. 
     </para>
-    </listitem>
-    </itemizedlist>
 
+    <section>
+    <title>Identifying bugs</title>
     <para>
-        When you make a suggestion, try to be as specific as possible.
-        For example, if you have found an error in this manual (which
-        is part of &TCAR;, by the way), include the section number and
-        some of the surrounding text so we can find it easily.
+        ...
     </para>
+    </section>
 
+    <section>
+    <title>What to report</title>
+    <para>
+        ...
+    </para>
+    </section>
+
+    <section>
+    <title>Where to report bugs</title>
+    <para>
+        ...
+    </para>
+    </section>
+ 
 </section>