From 070aa0da56bb55763356d2a794f28f759020da9f Mon Sep 17 00:00:00 2001
From: Tom Rhodes <trhodes@FreeBSD.org>
Date: Wed, 17 Jul 2002 19:10:53 +0000
Subject: [PATCH] Structure change to the PR-Guidelines article.

PR:		39055
Submitted by:	Chris Pepper <pepper@rockefeller.edu>
---
 .../articles/pr-guidelines/article.sgml           | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/en_US.ISO8859-1/articles/pr-guidelines/article.sgml b/en_US.ISO8859-1/articles/pr-guidelines/article.sgml
index 1fde432784..777f3f524d 100644
--- a/en_US.ISO8859-1/articles/pr-guidelines/article.sgml
+++ b/en_US.ISO8859-1/articles/pr-guidelines/article.sgml
@@ -60,14 +60,14 @@
 
     <itemizedlist>
       <listitem>
-	<para>The originator submits a PR and receives a confirmation
-	  message.</para>
+	<para>The Reporter submits a PR and receives a confirmation
+	  message, most likely via &man.send-pr.1; or the Problem Report web form at <ulink url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink>.</para>
       </listitem>
 
       <listitem>
 	<para>Joe Random Committer takes interest in the PR and
 	  assigns it to himself, or Jane Random BugBuster decides that
-	  Joe is the best suited to handle it and assigns it to
+	  Joe is best suited to handle it and assigns it to
 	  him.</para>
       </listitem>
 
@@ -240,22 +240,21 @@
 	choose the one that contains the largest amount of useful
 	information and close the others, stating clearly the number
 	of the superseding PR.  If several PRs contain non-overlapping
-	useful information, submit whatever is missing from the one
-	you keep open in a followup, with references to the PRs you
-	close.</para>
+	useful information, submit all the missing information to one
+	in a followup, including references to the others; then close the other PRs (which are now completely superseded).</para>
     </section>
 
     <section>
       <title>Stale PRs</title>
 
       <para>A PR is considered stale if it hasn't been modified in
-	more than six months.  Apply the following procedure:</para>
+	more than six months.  Apply the following procedure to deal with stale PRs:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>If the PR contains sufficient detail, try to reproduce
 	    the problem in <literal>-CURRENT</literal> and
-	    <literal>-STABLE</literal>.  if you succeed, submit a
+	    <literal>-STABLE</literal>.  If you succeed, submit a
 	    followup detailing your findings and try to find someone
 	    to assign it to.  Set the state to <quote>analyzed</quote>
 	    if appropriate.</para>