usermanual: Grammer and consistency edits.

1 files changed, 20 insertions, 19 deletions

diff --git a/usermanual/reference/class_autotools.xml b/usermanual/reference/class_autotools.xml
index 2614209045..36b377a14a 100644
--- a/usermanual/reference/class_autotools.xml
+++ b/usermanual/reference/class_autotools.xml
@@ -10,9 +10,9 @@
   options to specify search paths for headers and libraries.</para>
 
   <para>The autotools class takes care of all of the details for you. It
-  defines appropriate tasks for <command>do_configure</command>,
-  <command>do_compile</command>, <command>do_stage</command> and
-  <command>do_install</command>. At it's simplest adding an inherit for the
+  defines appropriate tasks for <emphasis>configure</emphasis>,
+  <emphasis>compile</emphasis>, <emphasis>stage</emphasis> and
+  <emphasis>install</emphasis>. At it's simplest adding an inherit for the
   autotools class is all that is required. The netcat recipe for example
   is:<screen>DESCRIPTION = "GNU Netcat"
 HOMEPAGE = "http://netcat.sourceforge.net"
@@ -24,17 +24,18 @@ PR = "r1"
 SRC_URI = "${SOURCEFORGE_MIRROR}/netcat/netcat-${PV}.tar.bz2"
 
 inherit autotools</screen>The header is defined, the location of the source
-  code and then inherit. For the simplest cases that is all that is required.
-  If you need to pass addition parameters to the configure script, such as for
-  enabling and/or disabling options, then they can be specified via the
-  <command>EXTRA_OECONF</command> variable. This example from the lftp recipe
-  shows several extra options being passed to the configure script:<screen>EXTRA_OECONF = "--disable-largefile --disable-rpath --with-included-readline=no"</screen>If
-  you define your own tasks for <command>do_configure</command>,
-  <command>do_compile</command>, <command>do_stage</command> or
-  <command>do_install</command> then they will override the methods generated
-  by the autotools class. If you need to perform additional operations (rather
-  than replacing the generated operations) you can use the
-  <command>do_&lt;task&gt;_append</command> or
+  code and then the inherit. For the simplest cases this is all that is
+  required. If you need to pass additionol parameters to the configure script,
+  such as for enabling and/or disabling options, then they can be specified
+  via the <command>EXTRA_OECONF</command> variable. This example from the lftp
+  recipe shows several extra options being passed to the configure
+  script:<screen>EXTRA_OECONF = "--disable-largefile --disable-rpath --with-included-readline=no"</screen>If
+  you define your own tasks for <emphasis>configure</emphasis>,
+  <emphasis>compile</emphasis>, <emphasis>stage</emphasis> or
+  <emphasis>install</emphasis> (via <command>do_&lt;taskname&gt;</command>)
+  then they will override the methods generated by the autotools class. If you
+  need to perform additional operations (rather than replacing the generated
+  operations) you can use the <command>do_&lt;task&gt;_append</command> or
   <command>do_&lt;task&gt;_prepend</command> methods. The following example
   from the conserver recipe shows some additional items being
   installed:<screen># Include the init script and default settings in the package
@@ -51,9 +52,9 @@ do_install_append () {
     <command>oe_runconf</command> which runs the actual configure script, and
     a method called <command>autotools_do_configure</command> which generates
     the configure file (runs automake and autoconf) and then calls
-    <command>oe_runconf</command>. The generated
-    <command>do_configure</command> task just calls
-    autotools_do_configure.</para>
+    <command>oe_runconf</command>. The generated method for the
+    <emphasis>configure</emphasis> task, <command>do_configure</command>, just
+    calls the <command>autotools_do_configure</command> method.</para>
 
     <para>It is sometimes desirable to implement your own
     <command>do_configure</command> method, where additional configuration is
@@ -65,8 +66,8 @@ do_install_append () {
     oe_runconf
 }</screen>Sometimes manual manipulations of the autotools files is required
     prior to calling autoconf/automake. In this case you can defined your own
-    do_configure which performs the required actions and then calls
-    <command>autotools_do_configure</command>.</para>
+    <command>do_configure</command> method which performs the required actions
+    and then calls <command>autotools_do_configure</command>.</para>
   </section>
 
   <section>