svn: /pear/peardoc/trunk/en/guide/users/ dependencytracking.xml

ashnazg                                  Thu, 10 Sep 2009 13:23:36 +0000

Revision: http://svn.php.net/viewvc?view=revision&revision=288239

Log:
minor clarity updates

Changed paths:
    U   pear/peardoc/trunk/en/guide/users/dependencytracking.xml

Modified: pear/peardoc/trunk/en/guide/users/dependencytracking.xml
===================================================================
--- pear/peardoc/trunk/en/guide/users/dependencytracking.xml	2009-09-10 13:23:24 UTC (rev 288238)
+++ pear/peardoc/trunk/en/guide/users/dependencytracking.xml	2009-09-10 13:23:36 UTC (rev 288239)
@@ -15,18 +15,17 @@
  </para>

  <para>
-  This can be done, for example, to ensure that a specified set of PEAR packages
-  are installed on both a development environment, into a test environment and
-  finally into a production environment with minimum fuss.
+  For example, this can be done to ensure that a specified set of PEAR packages
+  are installed on a development environment, into a test environment, and
+  finally into a production environment, all with minimum fuss.
  </para>

  <para>
-  Another reason for using pear to track dependencies is to reduce the amount of
-  work required when trying to do this work manually: checking to see if a new
-  release that may add required functionality, close security issues or
-  include bug fixes can take time. Add a
-  few more packages and interdependencies in to the mix and the
-  amount of work grows exponentially.
+  Another reason for using PEAR to track dependencies is to reduce the amount of
+  work required when trying to do this work manually... checking to see if a new
+  release that may add required functionality, close security issues, or
+  include bug fixes can take time. Add a few more packages and interdependencies
+  to the mix, and the amount of work grows exponentially.
  </para>

  <para>
@@ -45,14 +44,14 @@
     <para>
      List what you need -
      Include in this details such as what channels the packages are to be
-     installed from and whether you only very specific versions of those packages
+     installed from and whether you only want very specific versions of those packages
      to be installed, or if you want to specify what the minimum versions of the
      packages should be.
     </para>
    </listitem>
    <listitem>
     <para>
-     Create a package.xml including these packages as it's manifest.
+     Create a package.xml including these packages as its manifest.
     </para>
    </listitem>
    <listitem>
@@ -67,7 +66,7 @@
  <section xml:id="guide.users.dependencytracking.generatingalist">
   <title>Generating a list of what's needed</title>
   <para>
-   Assuming you want to replicate a subset of [pear] packages that are on one
+   Assuming you want to replicate a subset of PEAR-installable packages that are on one
    machine and you wish to install that same set on another machine, this is one
    suggested way to get the required details:
    Use the output of "$ pear info -a" to determine the names of the packages,