svn commit: r38933 - head/en_US.ISO8859-1/books/porters-handbook

[Warren Block]

Author: wblock
Date: Tue May 29 19:35:59 2012
New Revision: 38933
URL: http://svn.freebsd.org/changeset/doc/38933

Log:
  Expand some contractions and fix minor punctuation and usage problems.

Modified:
  head/en_US.ISO8859-1/books/porters-handbook/book.sgml

Modified: head/en_US.ISO8859-1/books/porters-handbook/book.sgml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/book.sgml	Tue May 29 19:24:26 2012	(r38932)
+++ head/en_US.ISO8859-1/books/porters-handbook/book.sgml	Tue May 29 19:35:59 2012	(r38933)
@@ -4265,7 +4265,7 @@ OPT6_DESC=	Describe OPT6</programlisting
 	      not just repeat the name.  For example, describing the
 	      <literal>NLS</literal> option as
 	      <quote>include NLS support</quote> does not help the
-	      user who can already see the option name but may not
+	      user, who can already see the option name but may not
 	      know what it means.  Describing it as <quote>Native
 		Language Support via gettext utilities</quote> is
 	      much more helpful.</para>
@@ -4413,12 +4413,12 @@ CONFIGURE_ARGS+=	--enable-foo
 	</example>
 
 	<para>In the example above, imagine a library libfoo is
-	  installed on the system.  User does not want this
+	  installed on the system.  The user does not want this
 	  application to use libfoo, so he toggled the option off in
 	  the <literal>make config</literal> dialog.  But the
 	  application's configure script detects the library present
 	  in the system and includes its support in the resulting
-	  executable.  Now when user decides to remove libfoo from the
+	  executable.  Now when the user decides to remove libfoo from the
 	  system, the ports system does not protest (no dependency on
 	  libfoo was recorded) but the application breaks.</para>
 
@@ -6356,7 +6356,7 @@ do-configure:
 	  <maketarget>build</maketarget> target.</para>
 
 	<para>Qt applications often are written to be cross-platform
-	  and often X11/Unix isn't the platform they are developed on,
+	  and often X11/Unix is not the platform they are developed on,
 	  which in turn often leads to certain loose ends,
 	  like:</para>
 
@@ -6377,7 +6377,7 @@ do-configure:
 	  <listitem>
 	    <para><emphasis>Bogus installation paths.</emphasis>
 	      Sometimes data such as icons or .desktop files are by
-	      default installed into directories which aren't scanned
+	      default installed into directories which are not scanned
 	      by XDG-compatible applications.  <filename
 		role="package">editors/texmaker</filename> is an
 	      example for this - look at
@@ -8909,7 +8909,7 @@ CFLAGS+=	-DLUA_VERSION_STRING="${VER_STR
 	      <entry>The port requires SeaMonkey as a runtime
 		dependency.  Possible values: <literal>yes</literal>
 		(get default version), <literal>20</literal>,
-		<literal>11</literal> (deprecated, shouldn't be used
+		<literal>11</literal> (deprecated, should not be used
 		any more).  Default dependency is on version
 		<literal>20</literal>.</entry>
 	    </row>
@@ -8927,7 +8927,7 @@ CFLAGS+=	-DLUA_VERSION_STRING="${VER_STR
 	      <entry>The port requires Thunderbird as a runtime
 		dependency.  Possible values: <literal>yes</literal>
 		(get default version), <literal>31</literal>,
-		<literal>30</literal> (deprecated, shouldn't be used
+		<literal>30</literal> (deprecated, should not be used
 		any more).  Default dependency is on version
 		<literal>31</literal>.</entry>
 	    </row>
@@ -10075,7 +10075,7 @@ as .putsy.conf and edit it.</programlist
     <sect1 id="testing-tinderbox">
       <title>Tinderbox</title>
 
-      <para>If you're an avid ports contributor, you might want to
+      <para>If you are an avid ports contributor, you might want to
 	take a look at <application>Tinderbox</application>.  It is a
 	powerful system for building and testing ports based on the
 	scripts used on <link
@@ -13608,7 +13608,7 @@ Reference: &lt;http://www.freebsd.org/po
 	      <entry>7.0-RELEASE, and 7.0-CURRENT after ABI backwards
 		compatibility to the FreeBSD 4/5/6 versions of the
 		PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs was
-		MFC'ed, which required the ABI of the PCIOCGETCONF
+		MFCed, which required the ABI of the PCIOCGETCONF
 		IOCTL to be broken again</entry>
 	    </row>