[release-notes] more info on contacting docs

[Pete Travis]

commit fc8d9285b595a43787b9523f3a57ba6cd45ce666
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sat Aug 30 11:54:14 2014 -0600

    more info on contacting docs

 en-US/prerelease.xml |   17 +++++++++++------
 1 files changed, 11 insertions(+), 6 deletions(-)
---
diff --git a/en-US/prerelease.xml b/en-US/prerelease.xml
index 8ebcb7b..65385de 100644
--- a/en-US/prerelease.xml
+++ b/en-US/prerelease.xml
@@ -28,7 +28,7 @@
     <formalpara>
       <title>Rawhide</title>
       <para>
-        <ulink url="https://fedoraproject.org/wiki/Releases/Rawhide">Rawhide</ulink> is the development branch of Fedora.  It is used by testers and maintaners to test compatibility between packages, identify and correct problems with unreleased packages, and test updates too minor or major to go into a stable release.
+        <ulink url="https://fedoraproject.org/wiki/Releases/Rawhide">Rawhide</ulink> is the development branch of Fedora.  It is used by testers and maintainers to test compatibility between packages, identify and correct problems with unreleased packages, and test updates too minor or major to go into a stable release.
       </para>
     </formalpara>
     <para>
@@ -37,7 +37,7 @@
     <formalpara>
       <title>Branched</title>
       <para>
-        The <ulink url="https://fedoraproject.org/wiki/Releases/Branched">Branched</ulink> repository is created from Rawhide during the beginning of the release cycle. It creates the basis for what will become the next version of Fedora, and is used to create pre-releases.
+        The <ulink url="https://fedoraproject.org/wiki/Releases/Branched">Branched</ulink> repository is created from Rawhide near the beginning of the release cycle. It creates the basis for what will become the next version of Fedora, and is used to create pre-releases.
       </para>
     </formalpara>
     <note>
@@ -52,7 +52,7 @@
     <formalpara>
       <title>Alpha</title>
       <para>
-        Installation images and package builds are composed and tested from the Branched repository.  The Fedora QA team works first with <literal>Test Candidate</literal> images, then with <literal>Release Candidate</literal> images, to refine the product.  Once the appropriate criteria are met, an Alpha release is provided to the general public for feedback and testing.
+        Installation images and package builds are composed and tested from the Branched repository.  The Fedora QA team works first with <literal>Test Compose</literal> images, then with <literal>Release Candidate</literal> images, to refine the product.  Once the appropriate criteria are met, an Alpha release is provided to the general public for feedback and testing.
       </para>
     </formalpara>
     <formalpara>
@@ -64,7 +64,7 @@
     <formalpara>
       <title>GA</title>
       <para>
-        The general availability release is made available to the public after rigorous testing and another set of more stringent release criteria are met.  At this time, packages held in <literal>updates-testing</literal> are moved into the general updates repository.  Other groups in the project make their work available at this time; websites are switched to the new version, announcements and press releases are sent, support volunteers are engaged, and more.
+        The general availability release is made available to the public after rigorous testing and another set of more stringent release criteria are met.  At this time, packages that were held in <literal>updates-testing</literal> during the release freeze are moved into the general updates repository.  Other groups in the project make their work available at this time; websites are switched to the new version, announcements and press releases are sent, support volunteers are engaged, and more.
       </para>
     </formalpara>
     <formalpara>
@@ -124,10 +124,15 @@
       If you are testing the Alpha release of Fedora and encounter notable changes, you can help improve the Release Notes by adding to the <ulink url="https://fedoraproject.org/wiki/Category:Documentation_beats">appropriate beat</ulink>. Don't worry too much about presentation or writing ability; the Docs team will appreciate your help in identifying changes and can refine the copy further.
     </para>
     <para>
-      During the Beta release or at any time during the release cycle, you can file a bug against the Release Notes.
+      During the Beta release or at any time during the release cycle, you can <ulink url="https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Documentation&component=release-notes">file a bug</ulink> against the Release Notes to request an addition or correction.
     </para>
     <para>
-      You can mail the Fedora Docs mailing list to provide feedback on the Release Notes or any Fedora documentation.
+      In an existing bug, you can set the <literal>fedora_requires_release_note</literal> flag to <literal>?</literal> to bring the issue to the attention of the Docs team for review.
+    <para>
+      You can mail the <ulink url="https://lists.fedoraproject.org/pipermail/docs/">Fedora Docs mailing list</ulink> to provide feedback on the Release Notes or any Fedora documentation.
+    </para>
+    <para>
+      You can also provide feedback and meet with Docs team members in #fedora-docs on Freenode.
     </para>
   </section>
 </section>