From c6c8bac49bedcfd18027d0e60827ac5a7d856404 Mon Sep 17 00:00:00 2001
From: Gabor Pali <pgj@FreeBSD.org>
Date: Sun, 19 Sep 2010 15:06:42 +0000
Subject: [PATCH] - Minor fixes in the "slow porting/patching" subsection

PR:		docs/150708
Submitted by:	Ben Kaduk <kaduk@mit.edu>
---
 en_US.ISO8859-1/books/porters-handbook/book.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml
index f7eff225c4..ff2bd6972c 100644
--- a/en_US.ISO8859-1/books/porters-handbook/book.sgml
+++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml
@@ -673,7 +673,7 @@ PLIST_DIRS=     lib/X11/oneko</programlisting>
 	<para>Please only use characters <literal>[-+._a-zA-Z0-9]</literal> for
 	  naming your patches.  Do not use any other characters besides them.
 	  Do not name your patches like <filename>patch-aa</filename> or
-	  <filename>patch-ab</filename> etc, always mention path and file name
+	  <filename>patch-ab</filename> etc, always mention the path and file name
 	  in patch names.</para>
 
 	<para>Do not put RCS strings in patches.  CVS will mangle them when we
@@ -745,8 +745,8 @@ DOS2UNIX_REGEX=  .*\.(c|cpp|h)</programlisting>
 	<para>If you want to create a patch file based off of an
 	  existing file, you can copy it with an
 	  <filename>.orig</filename> extension, and then modify the
-	  original one.  Run <maketarget>makepatch</maketarget>, and
-	  this will write out an appropriate patch file to the <filename
+	  original one.  The <maketarget>makepatch</maketarget> target
+	  will write out an appropriate patch file to the <filename
 	    class="directory">files</filename> directory of the
 	  port.</para>
       </sect1>