Greg Ward avatar Greg Ward committed 58a44e5 Draft

Fix several typos and grammatical errors in the user guide.

Comments (0)

Files changed (10)

doc/user/add-method.in

 
   <para>
 
-  As mentioned, a psuedo-builder also provides more flexibility
+  As mentioned, a pseudo-builder also provides more flexibility
   in parsing arguments than you can get with a &Builder;.
   The next example shows a pseudo-builder with a
   named argument that modifies the filename, and a separate argument

doc/user/add-method.xml

 
   <para>
 
-  As mentioned, a psuedo-builder also provides more flexibility
+  As mentioned, a pseudo-builder also provides more flexibility
   in parsing arguments than you can get with a &Builder;.
   The next example shows a pseudo-builder with a
   named argument that modifies the filename, and a separate argument

doc/user/builders-writing.in

   <para>
 
   Although &SCons; provides many useful methods
-  for building common software products:
-  programs, libraries, documents.
+  for building common software products
+  (programs, libraries, documents, etc.),
   you frequently want to be
   able to build some other type of file
   not supported directly by &SCons;.
   (In fact, the &SCons; interfaces for creating
   &Builder; objects are flexible enough and easy enough to use
   that all of the the &SCons; built-in &Builder; objects
-  are created the mechanisms described in this section.)
+  are created using the mechanisms described in this section.)
 
   </para>
 

doc/user/builders-writing.xml

   <para>
 
   Although &SCons; provides many useful methods
-  for building common software products:
-  programs, libraries, documents.
+  for building common software products
+  (programs, libraries, documents, etc.),
   you frequently want to be
   able to build some other type of file
   not supported directly by &SCons;.
   (In fact, the &SCons; interfaces for creating
   &Builder; objects are flexible enough and easy enough to use
   that all of the the &SCons; built-in &Builder; objects
-  are created the mechanisms described in this section.)
+  are created using the mechanisms described in this section.)
 
   </para>
 

doc/user/command-line.in

 
     Any command-line argument containing an <literal>=</literal>
     (equal sign) is considered a variable setting with the form
-    <varname>variable</varname>=<varname>value</varname>
+    <varname>variable</varname>=<varname>value</varname>.
     &SCons; provides direct access to
     all of the command-line variable settings,
     the ability to apply command-line variable settings

doc/user/command-line.xml

 
     Any command-line argument containing an <literal>=</literal>
     (equal sign) is considered a variable setting with the form
-    <varname>variable</varname>=<varname>value</varname>
+    <varname>variable</varname>=<varname>value</varname>.
     &SCons; provides direct access to
     all of the command-line variable settings,
     the ability to apply command-line variable settings
       by the ones specified on the command line.
 
       </para>
-
+      
     </section>
 
     <section>

doc/user/depends.in

 
       <para>
 
-      Another thing to look out for, is the fact that the three
+      Another thing to look out for is the fact that the three
       attributes above may not be present at the time of the first run.
-      Without any prior build, no targets got created and no
+      Without any prior build, no targets have been created and no
       <filename>.sconsign</filename> DB file exists yet.
-      So, it is recommended to always check whether the
+      So, you should always check whether the
       <varname>prev_ni</varname> attribute in question is available.
 
       </para>

doc/user/depends.xml

 
       <para>
 
-      Another thing to look out for, is the fact that the three
+      Another thing to look out for is the fact that the three
       attributes above may not be present at the time of the first run.
-      Without any prior build, no targets got created and no
+      Without any prior build, no targets have been created and no
       <filename>.sconsign</filename> DB file exists yet.
-      So, it is recommended to always check whether the
+      So, you should always check whether the
       <varname>prev_ni</varname> attribute in question is available.
 
       </para>

doc/user/environments.in

       <para>
 
       Another way to get information from
-      a construction environment.
+      a construction environment
       is to use the &subst; method
       on a string containing <literal>$</literal> expansions
       of construction variable names.
       <para>
 
       You can, however, control the settings
-      in the default contstruction environment
+      in the default construction environment
       by using the &DefaultEnvironment; function
       to initialize various settings:
 

doc/user/environments.xml

       <para>
 
       Another way to get information from
-      a construction environment.
+      a construction environment
       is to use the &subst; method
       on a string containing <literal>$</literal> expansions
       of construction variable names.
       <para>
 
       You can, however, control the settings
-      in the default contstruction environment
+      in the default construction environment
       by using the &DefaultEnvironment; function
       to initialize various settings:
 
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.