Doc: edit the building and running topi

Edit for grammar and style.

Change-Id: I61bdbd5dbd4adc8badfe7e5aebe0c43f2a7a875e
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>

1 files changed, 15 insertions, 17 deletions

diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc
index 704600e..7a96856 100644
--- a/src/doc/src/b2qt.qdoc
+++ b/src/doc/src/b2qt.qdoc
@@ -596,19 +596,17 @@
     \previouspage qtee-preparing-hardware.html
     \nextpage qtee-customization.html
 
-    Once the installation and configuration steps for \SDK and the
-    target device(s) are completed, it's time to test the setup.
-
-    First, make sure your device is powered up and connected to the
-    development host via USB.
-
-    Then, follow these steps to create and run a simple \l{Qt Quick}
-    application on the device:
+    After you complete the installation and configuration steps for \SDK and the
+    target devices, you can test the setup by creating a simple \l{Qt Quick}
+    application and running it on the device:
 
     \list 1
-        \li Open \b{File > New File or Project}, select
-            \b{Qt Quick 2 Application (Built-in Types)} and click \b{Choose...}.
-        \li In \b{Kit Selection} dialog, select the kit(s) for your
+        \li Make sure that your device is powered up and connected to the
+            development host.
+        \li In Qt Creator, select \b{File > New File or Project} >
+            \b Applications > \b{Qt Quick 2 Application (Built-in Types)} >
+            \b{Choose}.
+        \li In the \b{Kit Selection} dialog, select the kits for your
             devices. You can also select the emulator kit to test running the
             project in the emulator.
         \li Click \b{Next} and finish the wizard.
@@ -619,23 +617,23 @@
 
     \section1 Setting Up an Already Existing Project for Deployment
 
-    The projects generated by Qt Creator will always have the correct settings
+    The projects generated by Qt Creator always have the correct settings
     for deployment on the device or emulator. However, existing projects may
     need some changes.
 
     As a general rule, application binaries and resources (such as QML files and
-    images) are deployed under \c {/data/user/qt/<APPLICATION_NAME>} directory.
-    Therefore, the \c path variable for \c INSTALLS target(s) need to be adjusted
-    accordingly in .pro files:
+    images) are deployed to the \c {/data/user/qt/<APPLICATION_NAME>} directory.
+    Therefore, the \c path variable for the \c INSTALLS targets needs to be adjusted
+    accordingly in .pro files.
 
-    For example, the following:
+    For example, change the following \c target.path value:
 
     \code
         target.path = ...
         INSTALLS += target
     \endcode
 
-    should be migrated to:
+    to:
 
     \code
         target.path = /data/user/qt/<APPLICATION_NAME>