Various grammatical improvements.

1 files changed, 16 insertions, 16 deletions

diff --git a/en_US.ISO8859-1/articles/pr-guidelines/article.sgml b/en_US.ISO8859-1/articles/pr-guidelines/article.sgml
index 634c46d156..e29f3295d8 100644
--- a/en_US.ISO8859-1/articles/pr-guidelines/article.sgml
+++ b/en_US.ISO8859-1/articles/pr-guidelines/article.sgml
@@ -331,9 +331,9 @@
 
       <para>GNATS is picky about the format of a submitted bug report.
 	This is why a lot of PRs end up being <quote>misfiled</quote> if
-	the submitter forgets to fill a field or puts the wrong sort of
-	data some of the PR fields.  This section aims to provide most
-	of the necessary details for FreeBSD developers that can help
+	the submitter forgets to fill in a field or puts the wrong sort of
+	data in some of the PR fields.  This section aims to provide most
+	of the necessary details for FreeBSD developers that can help them to
 	close or refile these PRs.</para>
 
       <para>When GNATS cannot deduce what to do with a problem report
@@ -341,7 +341,7 @@
 	<literal>gnats-admin</literal> and files it under the
 	<literal>pending</literal> category.  This is now a
 	<quote>misfiled</quote> PR and will not appear in bug report
-	listings, unless someone explicitly asks a list of all the
+	listings, unless someone explicitly asks for a list of all the
 	misfiled PRs.  If you have access to the FreeBSD cluster
 	machines, you can use <command>query-pr</command> to view a
 	listing of PRs that have been misfiled:</para>
@@ -363,7 +363,7 @@
 	</listitem>
 
 	<listitem>
-	  <para>When filling the &man.send-pr.1; template, the submitter
+	  <para>When completing the &man.send-pr.1; template, the submitter
 	    forgot to set the category or class of the PR to a proper
 	    value.</para>
 	</listitem>
@@ -444,7 +444,7 @@ This was misfiled because the subject didn't have the format:
 	<title>PRs misfiled because of missing fields</title>
 
 	<para>The second type of misfiled PRs is usually the result of a
-	  submitter who forgot to fill all the necessary fields when
+	  submitter forgetting to fill all the necessary fields when
 	  writing the original PR.</para>
 
 	<para>Missing or bogus <quote>category</quote> or
@@ -456,7 +456,7 @@ This was misfiled because the subject didn't have the format:
 	<para>Another common cause of misfiled PRs because of formatting
 	  issues is quoting, changes or removal of the
 	  <command>send-pr</command> template, either by the user who
-	  edits the template or by mailers who do strange things to
+	  edits the template or by mailers which do strange things to
 	  plain text messages.  This doesn't happen a lot of the time,
 	  but it can be fixed with <command>edit-pr</command> too; it
 	  does require a bit of work from the developer who refiles the
@@ -466,17 +466,17 @@ This was misfiled because the subject didn't have the format:
       <section id="pr-misfiled-notpr">
 	<title>Misfiled PRs that are not really problem reports</title>
 
-	<para>Some times a user wants to submit a report for a problem
+	<para>Sometimes a user wants to submit a report for a problem
 	  and sends a simple email message to GNATS.  The GNATS scripts
 	  will recognize bug reports that are formatted using the
 	  &man.send-pr.1; template.  They cannot parse any sort of email
-	  though.  This is why submissions of bug reports that are send
+	  though.  This is why submissions of bug reports that are sent
 	  to <email>freebsd-gnats-submit@freebsd.org</email> have to
-	  follow the template of <command>send-pr</command> but email
-	  reports sent to &a.bugs;.</para>
+	  follow the template of <command>send-pr</command>, but email
+	  reports can be sent to &a.bugs;.</para>
 
-	<para>Developers that come across PRs that look like they should
-	  be posted to &a.bugs.name; or some other list should close the
+	<para>Developers that come across PRs that look like they should have
+	  been posted to &a.bugs.name; or some other list should close the
 	  PR, informing the submitter in their state-change log why this
 	  is not really a PR and where the message should be posted.</para>
 
@@ -491,18 +491,18 @@ This was misfiled because the subject didn't have the format:
 	  the sender's address of spam mail is never valid these days.
 	  Bounces will come back for each PR that is closed.</para>
 
-	<para>Currently, with the installation of some antispam filters,
+	<para>Currently, with the installation of some antispam filters
 	  that check all submissions to the GNATS database, the amount
 	  of spam that reaches the <quote>pending</quote> state is very
 	  small.</para>
 
 	<para>All developers who have access to the FreeBSD.org cluster
-	  machines are encouraged to check for misfiled PRs immediately
+	  machines are encouraged to check for misfiled PRs and immediately
 	  close those that are spam mail.  Whenever you close one of
 	  these PRs it is also a good idea to set its category to
 	  <quote><literal>junk</literal></quote>.  Junk PRs are not
 	  backed up, so filing spam mail under this category makes it
-	  obvious that we do not care to keep around and waste disk
+	  obvious that we do not care to keep it around or waste disk
 	  space for it.</para>
       </section>
     </section>