Index: chapter.xml
===================================================================
--- chapter.xml
+++ chapter.xml
@@ -93,18 +93,6 @@
       </step>
     </procedure>
 
-    <para>If the software package was not deliberately ported, or
-      tested to work, on &os;, the source code may need editing in
-      order for it to install and run properly.  At the time of this
-      writing, over &os.numports; third-party applications have been
-      ported to &os;.</para>
-
-    <para>A &os; package contains pre-compiled copies of all the
-      commands for an application, as well as any configuration files
-      and documentation.  A package can be manipulated with the
-      <application>pkg</application> commands, such as
-      <command>pkg install</command>.</para>
-
     <para>A &os; port is a collection of files designed to automate
       the process of compiling an application from source code.  The
       files that comprise a port contain all the necessary information
@@ -111,7 +99,15 @@
       to automatically download, extract, patch, compile, and install
       the application.</para>
 
-    <para>The ports system can also be used to generate packages which
+    <para>If the software has not already been adapated and tested
+      on &os;, the source code may need editing in
+      order for it to install and run properly.</para>
+
+    <para>However, over &os.numports; third-party applications have already been
+      ported to &os;.  When feasible, these applications are made
+      available for download as pre-compiled <emphasis>packages</emphasis>.</para>
+
+    <para>Packages
       can be manipulated with the &os; package management
       commands.</para>
 
@@ -120,6 +116,12 @@
       dependent library is not already installed, the library will
       automatically be installed first.</para>
 
+    <para>A &os; package contains pre-compiled copies of all the
+      commands for an application, as well as any configuration files
+      and documentation.  A package can be manipulated with the
+      &man.pkg.8; commands, such as
+      <command>pkg install</command>.</para>
+
     <para>While the two technologies are similar, packages and
       ports each have their own strengths.  Select the technology that
       meets your requirements for installing a particular
@@ -714,9 +718,14 @@
     <title>Using the Ports Collection</title>
 
     <para>The Ports Collection is a set of
-      <filename>Makefiles</filename>, patches, and description files
-      stored in <filename>/usr/ports</filename>.  This set of files is
-      used to compile and install applications on &os;.  Before an
+      <filename>Makefiles</filename>, patches, and description files.
+      Each set of these files is used to compile and install an individual
+      application on &os;, and is termed a <quote>port</quote>.</para>
+
+    <para>By default these files are stored under
+      <filename>/usr/ports</filename>.</para>
+
+    <para>Before an
       application can be compiled using a port, the Ports Collection
       must first be installed.  If it was not installed during the
       installation of &os;, use one of the following methods to
@@ -810,11 +819,12 @@
       </step>
     </procedure>
 
-    <para>The Ports Collection installs a series of directories
+    <para>The Ports Collection installs directories
       representing software categories with each category having
-      a subdirectory for each application.  Each subdirectory, also
-      referred to as a ports skeleton, contains a set of files that
-      tell &os; how to compile and install that program.  Each port
+      a subdirectory for each application.  That directory
+      contains a set of files that
+      tell &os; how to compile and install that program,
+      referred to as a ports skeleton.  Each port
       skeleton includes these files and directories:</para>
 
     <itemizedlist>