- Clean up some grammar

- Document ports-mgmt/genplist

PR:		docs/121197
Submitted by:	Chess Griffin <chess chessgriffin.com>
Reviewed by:	pav
Approved by:	trhodes

en_US.ISO8859-1/books/porters-handbook/book.sgml

@@ -2412,10 +2412,10 @@ EXTRACT_ONLY=  source.tar.gz</programlisting>
 	  hereon.</para>
 
 	<para>A little background first.  OpenBSD has a neat feature
-	  inside both <makevar>DISTFILES</makevar> and
-	  <makevar>PATCHFILES</makevar> variables, both files and
-	  patches can be postfixed with <literal>:n</literal>
-	  identifiers where <literal>n</literal> both can be
+	  inside the <makevar>DISTFILES</makevar> and
+	  <makevar>PATCHFILES</makevar> variables which allows files and
+	  patches to be postfixed with <literal>:n</literal>
+	  identifiers. Here, <literal>n</literal> can be both 
 	  <literal>[0-9]</literal> and denote a group designation.
 	  For example:</para>
 
@@ -2436,7 +2436,7 @@ EXTRACT_ONLY=  source.tar.gz</programlisting>
 	  as hell where <filename>beta</filename> is carried by all
 	  sites in <makevar>MASTER_SITES</makevar>, and
 	  <filename>alpha</filename> can only be found in the 20th
-	  site.  It would be such a waste to check all of them if
+	  site.  It would be such a waste to check all of them if the
 	  maintainer knew this beforehand, would it not?  Not a good
 	  start for that lovely weekend!</para>
 
@@ -3121,7 +3121,7 @@ ALWAYS_KEEP_DISTFILES=  yes
 	  challenge for port maintainers</ulink> section.</para>
 
 	<para>Changes to the port will be sent to the maintainer of
-	  a port for a review and an approval before being committed.
+	  a port for review and approval before being committed.
 	  If the maintainer does not respond to an update
 	  request after two weeks (excluding major public
 	  holidays), then that is considered a maintainer timeout, and the
@@ -3137,8 +3137,8 @@ ALWAYS_KEEP_DISTFILES=  yes
 	  to better match existing policies and style of the Ports
 	  Collection without explicit blessing from the submitter.
 	  Also, large infrastructural changes can result in
-	  a port being modified without maintainer's consent.
-	  This kind of changes will never affect the port's
+	  a port being modified without the maintainer's consent.
+	  These kinds of changes will never affect the port's
 	  functionality.</para>
 
 	<para>The &a.portmgr; reserves the right to revoke or override
@@ -4090,7 +4090,7 @@ PORTVERSION=   1.0</programlisting>
 
 	<para>Two macros exists for this situation.  The advantage of using
 	  these macros instead of <command>cp</command> is that they guarantee
-	  proper file ownership and permissions on target files.  First macro,
+	  proper file ownership and permissions on target files.  The first macro,
 	  <makevar>COPYTREE_BIN</makevar>, will set all the installed files to
 	  be executable, thus being suitable for installing into
 	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The second
@@ -8645,6 +8645,11 @@ etc/orbit.conf.sample
       <para>The packing list still has to be tidied up by hand as
 	stated above.</para>
 
+      <para>Another tool that might be used to create an initial
+	<filename>pkg-plist</filename> is <filename
+	role="package">ports-mgmt/genplist</filename>.  As with any
+	automated tool, the resulting <filename>pkg-plist</filename>
+	should be checked and manually edited as needed.</para>
     </sect1>
 
     </chapter>
@@ -11882,7 +11887,7 @@ Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
 		  <row>
 		    <entry>7.0-CURRENT after
 		      RFC 3678 API support added to the IPv4 stack.
-		      Legacy RFC 1724 behaviour of the IP_MULTICAST_IF
+		      Legacy RFC 1724 behavior of the IP_MULTICAST_IF
 		      ioctl has now been removed; 0.0.0.0/8 may no longer
 		      be used to specify an interface index.
 		      struct ipmreqn should be used instead.</entry>