From 6cdb356826d8aec19b9180433d4452feb46d48d7 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <srifenbark@gmail.com>
Date: Tue, 15 Mar 2016 10:31:34 -0700
Subject: toaster-manual: Edits to a previous patch.

I applied some grammar and writing edits to a large patch of new
text.

(From yocto-docs rev: 67cd700131e7cbca5769f25328772406f860d519)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../toaster-manual-setup-and-use.xml               | 40 ++++++++++++----------
 1 file changed, 22 insertions(+), 18 deletions(-)

(limited to 'documentation/toaster-manual')

diff --git a/documentation/toaster-manual/toaster-manual-setup-and-use.xml b/documentation/toaster-manual/toaster-manual-setup-and-use.xml
index 2e465f432b..12fe5839bd 100644
--- a/documentation/toaster-manual/toaster-manual-setup-and-use.xml
+++ b/documentation/toaster-manual/toaster-manual-setup-and-use.xml
@@ -119,7 +119,7 @@
                   If you used <filename>virtualenv</filename>, which is
                   recommended, to set up the Toaster system dependencies,
                   you need be sure the virtual environment is activated.
-                  To activate this environment, use the following:
+                  To activate this environment, use the following command:
                   <literallayout class='monospaced'>
    $ source venv/bin/activate
                   </literallayout>
@@ -179,7 +179,7 @@
       <para>
           You can use a production instance of Toaster to share the
           Toaster instance with remote users, multiple users, or both.
-          The production instance is also the setup that can cope with
+          The production instance is also the setup that can handle
           heavier loads on the web service.
           Use the instructions in the following sections to set up
           Toaster to run builds through the Toaster web interface.
@@ -559,44 +559,48 @@
       </section>
 
       <section id='a-note-on-the-local-yocto-project-release'>
-          <title>A Note on the Local Yocto Project Release</title>
+          <title>Additional Information About the Local Yocto Project Release</title>
 
           <para>
-              This note only applies if you have set up Toaster
-              for local development, as explained in
-              <link linkend='starting-toaster-for-local-development'>
-                section 3.1.</link>
+              This section only applies if you have set up Toaster
+              for local development, as explained in the
+              "<link linkend='starting-toaster-for-local-development'>Starting Toaster for Local Development</link>"
+              section.
           </para>
+
           <para>
               When you create a project in Toaster, you will be asked to
-              provide a name and to select a Yocto Project release. One
-              of the release options you will find is called
-              <emphasis>Local Yocto Project</emphasis>.
+              provide a name and to select a Yocto Project release.
+              One of the release options you will find is called
+              "Local Yocto Project".
               <imagedata fileref="figures/new-project.png" align="center" width="9in" />
           </para>
 
           <para>
-              When you select the <emphasis>Local Yocto Project</emphasis>
-              release, Toaster will run your builds using the local Yocto
+              When you select the "Local Yocto Project" release, Toaster
+              will run your builds using the local Yocto
               Project clone you have in your computer: the same clone
-              you are using to run Toaster. Unless you manually update
+              you are using to run Toaster.
+              Unless you manually update
               this clone, your builds will always use the same Git revision.
           </para>
 
           <para>
               If you select any of the other release options, Toaster
               will fetch the tip of your selected release from the upstream
-              <ulink url='https://git.yoctoproject.org'>Yocto Project
-              repository</ulink> every time you run a build. This effectively
+              <ulink url='https://git.yoctoproject.org'>Yocto Project repository</ulink>
+              every time you run a build.
+              Fetching this tip effectively
               means that if your selected release is updated upstream, the
               Git revision you are using for your builds will change.
               If you are doing development locally, you might not want this
-              to happen. In that case, the <emphasis>Local Yocto Project</emphasis>
+              change to happen.
+              In that case, the "Local Yocto Project"
               release might be the right choice.
           </para>
 
           <para>
-              However, the <emphasis>Local Yocto Project</emphasis> release
+              However, the "Local Yocto Project" release
               will not provide you with any compatible layers, other than the
               three core layers that come with the Yocto Project:
               <itemizedlist>
@@ -616,7 +620,7 @@
           <para>
               If you want to build any other layers, you will need to
               manually import them into your Toaster project, using the
-              <emphasis>Import layer</emphasis> page.
+              "Import layer" page.
               <imagedata fileref="figures/import-layer.png" align="center" width="9in" />
           </para>
 
-- 
cgit v1.2.3-54-g00ecf