svn commit: r45578 - head/en_US.ISO8859-1/books/porters-handbook/keeping-up

Author: mat (ports committer)
Date: Tue Sep  9 15:40:40 2014
New Revision: 45578
URL: http://svnweb.freebsd.org/changeset/doc/45578

Log:
  igor -Ry and some other rewording and fixes.
  
  Differential Revision:	https://reviews.freebsd.org/D642
  Reviewed by:	wblock
  Sponsored by:	Absolight

Modified:
  head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml

Modified: head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml	Tue Sep  9 15:32:10 2014	(r45577)
+++ head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml	Tue Sep  9 15:40:40 2014	(r45578)
@@ -19,30 +19,29 @@
     <para>One of the easiest ways to learn about updates that have
       already been committed is by subscribing to <link
 	xlink:href="http://www.FreshPorts.org/">FreshPorts</link>.
-      You can select multiple ports to monitor.  Maintainers are
+      Multiple ports can be monitored.  Maintainers are
       strongly encouraged to subscribe, because they will receive
       notification of not only their own changes, but also any changes
       that any other &os; committer has made.  (These are often
       necessary to keep up with changes in the underlying ports
       framework&mdash;although it would be most polite to receive an
       advance heads-up from those committing such changes, sometimes
-      this is overlooked or just simply impractical.  Also, in some
+      this is overlooked or impractical.  Also, in some
       cases, the changes are very minor in nature.  We expect everyone
       to use their best judgement in these cases.)</para>
 
-    <para>If you wish to use FreshPorts, all you need is an account.
-      If your registered email address is
-      <literal>@FreeBSD.org</literal>, you will see the opt-in link on
-      the right hand side of the webpages.  For those of you who
-      already have a FreshPorts account, but are not using your
-      <literal>@FreeBSD.org</literal> email address, just change your
-      email to <literal>@FreeBSD.org</literal>, subscribe, then change
-      it back again.</para>
+    <para>To use FreshPorts, an account is required.  Those with
+      registered email addresses at <literal>@FreeBSD.org</literal>
+      will see the opt-in link on the right-hand side of the web
+      pages.  Those who already have a FreshPorts account but are not
+      using a <literal>@FreeBSD.org</literal> email address can change
+      the email to <literal>@FreeBSD.org</literal>, subscribe, then
+      change it back again.</para>
 
     <para>FreshPorts also has a sanity test feature which
       automatically tests each commit to the &os; ports tree.  If
-      subscribed to this service, you will be notified of any errors
-      which FreshPorts detects during sanity testing of your
+      subscribed to this service, a committer will receive notifications
+      of any errors which FreshPorts detects during sanity testing of their
       commits.</para>
   </sect1>
 
@@ -65,14 +64,14 @@
   <sect1 xml:id="ports-mailing-list">
     <title>The &os; Ports Mailing List</title>
 
-    <para>If you maintain ports, you should consider following the
+    <para>As a ports maintainer, consider subscribing to
       &a.ports;.  Important changes to the way ports work will be
       announced there, and then committed to
       <filename>CHANGES</filename>.</para>
 
-    <para>If this mailing list is too high volume you may consider
-      following &a.ports-announce; which is moderated and has no
-      discussion.</para>
+    <para>If the volume of messages on this mailing list is too high,
+      consider following &a.ports-announce; which contains only
+      announcements.</para>
   </sect1>
 
   <sect1 xml:id="build-cluster">
@@ -113,8 +112,8 @@
       the maintainer is responsible for, the number of those ports
       with new distfiles, and the percentage of those ports that are
       out-of-date.  The search function allows for searching by email
-      address for a specific maintainer, and for selecting whether or
-      not only out-of-date ports should be shown.</para>
+      address for a specific maintainer, and for selecting whether
+      only out-of-date ports are shown.</para>
 
     <para>Upon clicking on a maintainer's email address, a list of
       all of their ports is displayed, along with port category,
@@ -142,18 +141,18 @@
       future, this will be expanded to include the distfile survey, as
       well as other sources.</para>
 
-    <para>To get started, you can view all information about a
-      particular port by using the <link
+    <para>To get started, use the <link
 	xlink:href="http://portsmon.FreeBSD.org/portoverview.py">Overview
-	of One Port</link>.</para>
+	of One Port</link> search page to find all the information
+      about a port.</para>
 
-    <para>As of this writing, this is the only resource available that
-      maps GNATS PR entries to portnames.  (PR submitters do not
+    <para>This is the only resource available that
+      maps PR entries to portnames.  PR submitters do not
       always include the portname in their Synopsis, although we would
-      prefer that they did.)  So, <literal>portsmon</literal> is a
-      good place to start if you want to find out whether an existing
-      port has any PRs filed against it and/or any build errors; or,
-      to find out if a new port that you may be thinking about
+      prefer that they did.  So, <literal>portsmon</literal> is a
+      good place to find out whether an existing
+      port has any PRs filed against it, any build errors, or
+      if a new port the porter is considering
       creating has already been submitted.</para>
   </sect1>
 </chapter>
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"