dev-manual, kernel-dev, profile-manual: Fixed title and link issues.

Following fixes:

 dev-manual - Discovered a <ulink> tag that was not a single
              line.  These types of links need to not have hard
              returns.  If they do, mega-manual.sed will not
              process the link.  Changed the reference to a
              single line.

 kernel-dev - Discovered that I had the old poky.ent variable
              (i.e. YOCTO_DOCS_KERNEL_URL) as part of the link
              in the opening note on the title page.  I changed
              it to the proper variable, which is
              YOCTO_DOCS_KERNEL_DEV_URL.  The old link was not
              being processed by mega-manual.sed.

 profile-manual - First problem was the wrong manual title in
              a <ulink> tag, which caused the mega-manual.sed
              file to skip processing the link into a non-link.

              Second problem was on the title page. Incredulously,
              I had the title of the manual reversed for Chapter
              1.  Fixed it.

(From yocto-docs rev: 71dedd610dce9fdc6472a5cf2b18ec8729d77e55)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

4 files changed, 48 insertions, 49 deletions

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index a59a447ce8..d2f6e938ed 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -18,8 +18,7 @@
              "<ulink url='&YOCTO_DOCS_BSP_URL;#creating-a-new-bsp-layer-using-the-yocto-bsp-script'>Creating a New BSP Layer Using the yocto-bsp Script</ulink>"
              section in the Yocto Project Board Support Package (BSP) Developer's Guide.
              For more complete information on how to work with the kernel, see the
-             <ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;'>Yocto Project Linux Kernel
-             Development Manual</ulink>.
+             <ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;'>Yocto Project Linux Kernel Development Manual</ulink>.
              </para></listitem>
          <listitem><para><emphasis>User Application Development:</emphasis>
              User Application Development covers development of applications that you intend
@@ -131,7 +130,7 @@
                     <ulink url='&YOCTO_DOCS_BSP_URL;#creating-a-new-bsp-layer-using-the-yocto-bsp-script'><filename>yocto-bsp</filename></ulink> script</emphasis>:
                     Layers are ideal for
                     isolating and storing work for a given piece of hardware.
-                    A layer is really just a location or area in which you place 
+                    A layer is really just a location or area in which you place
                     the recipes and configurations for your BSP.
                     In fact, a BSP is, in itself, a special type of layer.
                     The simplest way to create a new BSP layer that is compliant with the
@@ -165,7 +164,7 @@
                     Romley, sys940x, Sugar Bay, and tlk exist in their own separate layers
                     within the larger <filename>meta-intel</filename> layer.</note>
                     <para>When you set up a layer for a new BSP, you should follow a standard layout.
-                    This layout is described in the 
+                    This layout is described in the
                     "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout'>Example Filesystem Layout</ulink>"
                     section of the Board Support Package (BSP) Development Guide.
                     In the standard layout, you will notice a suggested structure for recipes and
@@ -343,10 +342,10 @@
                 If you are working in the kernel all the time, you probably would want
                 to set up your own local Git repository of the kernel tree.
                 If you just need to make some patches to the kernel, you can access
-                temporary kernel source files that were extracted and used 
+                temporary kernel source files that were extracted and used
                 during a build.
                 We will just talk about working with the temporary source code.
-                For more information on how to get kernel source code onto your 
+                For more information on how to get kernel source code onto your
                 host system, see the
                 "<link linkend='local-kernel-files'>Yocto Project Kernel</link>"
                 bulleted item earlier in the manual.
@@ -411,7 +410,7 @@
                         "<link linkend='local-yp-release'>Yocto Project Release</link>" earlier in this manual.
                         </para></listitem>
                     <listitem><para><emphasis>Establish the temporary kernel source files</emphasis>:
-                        Temporary kernel source files are kept in the 
+                        Temporary kernel source files are kept in the
                         <link linkend='build-directory'>Build Directory</link>
                         created by the
                         OpenEmbedded build system when you run BitBake.
@@ -474,7 +473,7 @@
         Application development involves creating an application that you want
         to run on your target hardware, which is running a kernel image created using the
         OpenEmbedded build system.
-        The Yocto Project provides an 
+        The Yocto Project provides an
         <ulink url='&YOCTO_DOCS_ADT_URL;#adt-intro-section'>Application Development Toolkit (ADT)</ulink>
         and stand-alone
         <ulink url='&YOCTO_DOCS_ADT_URL;#the-cross-development-toolchain'>cross-development toolchains</ulink>
@@ -950,7 +949,7 @@
                                 and then click "Next".</para></listitem>
                             <listitem><para>Select the root directory and browse to
                                 <filename>~/yocto-eclipse/plugins</filename>.</para></listitem>
-                            <listitem><para>Three plug-ins exist: 
+                            <listitem><para>Three plug-ins exist:
                                 <filename>org.yocto.bc.ui</filename>,
                                 <filename>org.yocto.sdk.ide</filename>, and
                                 <filename>org.yocto.sdk.remotetools</filename>.
@@ -980,7 +979,7 @@
                 <para>
                     To start, you need to do the following from within the Eclipse IDE:
                     <itemizedlist>
-                        <listitem><para>Choose "Preferences" from the 
+                        <listitem><para>Choose "Preferences" from the
                             "Windows" menu to display
                             the Preferences Dialog</para></listitem>
                         <listitem><para>Click "Yocto Project ADT"</para></listitem>
@@ -1010,7 +1009,7 @@
                                        <listitem><para><emphasis>
                                             <filename>Build System Derived Toolchain:</filename></emphasis>
                                             Select this mode if the cross-toolchain has been installed and built
-                                            as part of the 
+                                            as part of the
                                             <link linkend='build-directory'>Build Directory</link>.
                                             When you select <filename>Build system derived toolchain</filename>,
                                             you are using the toolchain bundled
@@ -1022,7 +1021,7 @@
                                 If you are using a stand-alone pre-built toolchain, you should be pointing to the
                                 where it is installed.
                                 If you used the ADT Installer script and accepted the default
-                                installation directory, the toolchain will be installed in 
+                                installation directory, the toolchain will be installed in
                                 the <filename>&YOCTO_ADTPATH_DIR;</filename> directory.
                                 Sections "<ulink url='&YOCTO_DOCS_ADT_URL;#configuring-and-running-the-adt-installer-script'>Configuring
                                 and Running the ADT Installer Script</ulink>" and
@@ -1034,17 +1033,17 @@
                                 field is the <link linkend='build-directory'>Build Directory</link>.
                                 See the "<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-toolchain-from-within-the-build-tree'>Using
                                 BitBake and the Build Directory</ulink>" section in the Yocto Project Application
-                                Developer's Guide for information on how to install 
+                                Developer's Guide for information on how to install
                                 the toolchain into the Build Directory.</para></listitem>
                             <listitem><para><emphasis>Specify the Sysroot Location:</emphasis>
                                 This location is where the root filesystem for the target hardware resides.
-                                If you used the ADT Installer script and accepted the 
+                                If you used the ADT Installer script and accepted the
                                 default installation directory, then the location is
                                 <filename>/opt/poky/&lt;release&gt;</filename>.
                                 Additionally, when you use the ADT Installer script,
                                 the same location is used for
                                 the QEMU user-space tools and the NFS boot process.</para>
-                                <para>If you used either of the other two methods to 
+                                <para>If you used either of the other two methods to
                                 install the toolchain or did not accept the ADT Installer
                                 script's default installation directory, then the
                                 location of the sysroot filesystem depends on where you separately
@@ -1160,7 +1159,7 @@
                 configurations.
                 You can override these settings for a given project by following these steps:
                 <orderedlist>
-                    <listitem><para>Select "Change Yocto Project Settings" from the 
+                    <listitem><para>Select "Change Yocto Project Settings" from the
                         "Project" menu.
                         This selection brings up the Yocto Project Settings Dialog
                         and allows you to make changes specific to an individual project.
@@ -1170,14 +1169,14 @@
                         Dialog as described earlier
                         in the "<link linkend='configuring-the-eclipse-yocto-plug-in'>Configuring the Eclipse
                         Yocto Plug-in</link>" section.
-                        The Yocto Project Settings Dialog allows you to override 
+                        The Yocto Project Settings Dialog allows you to override
                         those default settings for a given project.</para></listitem>
                     <listitem><para>Make your configurations for the project and click "OK".
                         If you are running the Juno version of Eclipse, you can skip down to the next
                         section where you build the project.
                         If you are not working with Juno, you need to reconfigure the project as
                         described in the next step.</para></listitem>
-                    <listitem><para>Select "Reconfigure Project" from the 
+                    <listitem><para>Select "Reconfigure Project" from the
                         "Project" menu.
                         This selection reconfigures the project by running
                        <filename>autogen.sh</filename> in the workspace for your project.
@@ -1197,7 +1196,7 @@
             <para>
                 To build the project in Juno, right click on the project in the navigator pane and select
                 "Build Project".
-                If you are not running Juno, select "Build Project" from the 
+                If you are not running Juno, select "Build Project" from the
                 "Project" menu.
                 The console should update and you can note the cross-compiler you are using.
             </para>
@@ -1209,7 +1208,7 @@
             <para>
                 To start the QEMU emulator from within Eclipse, follow these steps:
                 <orderedlist>
-                    <listitem><para>Expose and select "External Tools" from 
+                    <listitem><para>Expose and select "External Tools" from
                         the "Run" menu.
                         Your image should appear as a selectable menu item.
                         </para></listitem>
@@ -1232,12 +1231,12 @@
             <title>Deploying and Debugging the Application</title>
 
             <para>
-                Once the QEMU emulator is running the image, you can deploy 
-                your application using the Eclipse IDE and use then use 
+                Once the QEMU emulator is running the image, you can deploy
+                your application using the Eclipse IDE and use then use
                 the emulator to perform debugging.
                 Follow these steps to deploy the application.
                 <orderedlist>
-                    <listitem><para>Select "Debug Configurations..." from the 
+                    <listitem><para>Select "Debug Configurations..." from the
                     "Run" menu.</para></listitem>
                     <listitem><para>In the left area, expand <filename>C/C++Remote Application</filename>.</para></listitem>
                     <listitem><para>Locate your project and select it to bring up a new
@@ -1258,7 +1257,7 @@
                         determined earlier.</para></listitem>
                     <listitem><para>Click "Finish" to close the
                         New Connections Dialog.</para></listitem>
-                    <listitem><para>Use the drop-down menu now in the 
+                    <listitem><para>Use the drop-down menu now in the
                         "Connection" field and pick the IP Address you entered.
                          </para></listitem>
                     <listitem><para>Click "Run" to bring up a login screen
@@ -1315,8 +1314,8 @@
                         display the output.
                         For information on how to use Lttng to trace an application,
                         see <ulink url='http://lttng.org/documentation'></ulink>
-                        and the 
-                        "<ulink url='&YOCTO_DOCS_PROF_URL;#lttng-linux-trace-toolkit-next-generation'>LTTng (Linux Trace Toolkit, next generation)</ulink>" 
+                        and the
+                        "<ulink url='&YOCTO_DOCS_PROF_URL;#lttng-linux-trace-toolkit-next-generation'>LTTng (Linux Trace Toolkit, next generation)</ulink>"
                         section, which is in the Yocto Project Profiling and Tracing Manual.
                         <note>Do not use <filename>Lttng-user space (legacy)</filename> tool.
                             This tool no longer has any upstream support.</note>
@@ -1326,18 +1325,18 @@
                         Tracing project.
                         Do the following:
                         <orderedlist>
-                            <listitem><para>Select "Open Perspective" from the 
+                            <listitem><para>Select "Open Perspective" from the
                                 "Window" menu and then select "Tracing".</para></listitem>
                             <listitem><para>Click "OK" to change the Eclipse perspective
                                 into the Tracing perspective.</para></listitem>
                             <listitem><para>Create a new Tracing project by selecting
                                 "Project" from the "File -> New" menu.</para></listitem>
-                            <listitem><para>Choose "Tracing Project" from the 
+                            <listitem><para>Choose "Tracing Project" from the
                                 "Tracing" menu.
                                 </para></listitem>
                             <listitem><para>Generate your tracing data on the remote target.
                                 </para></listitem>
-                            <listitem><para>Select "Lttng2.0 ust trace import" from 
+                            <listitem><para>Select "Lttng2.0 ust trace import" from
                                 the "Yocto Project Tools" menu to
                                 start the data import process.</para></listitem>
                             <listitem><para>Specify your remote connection name.</para></listitem>
@@ -1348,8 +1347,8 @@
                             <listitem><para>Click "OK" to complete the import process.
                                 The data is now in the local tracing project you created.</para></listitem>
                             <listitem><para>Right click on the data and then use the menu to
-                                Select "Generic CTF Trace" from the 
-                                "Trace Type... -> Common Trace Format" menu to map 
+                                Select "Generic CTF Trace" from the
+                                "Trace Type... -> Common Trace Format" menu to map
                                 the tracing type.</para></listitem>
                             <listitem><para>Right click the mouse and select "Open"
                                 to bring up the Eclipse Lttng Trace Viewer so you
@@ -1386,7 +1385,7 @@
 
             <para>
                 Within the Eclipse IDE, you can create a Yocto BitBake Commander project,
-                edit the <link linkend='metadata'>Metadata</link>, and then use 
+                edit the <link linkend='metadata'>Metadata</link>, and then use
                 <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink> to build a customized
                 image all within one IDE.
             </para>
@@ -1397,16 +1396,16 @@
                 <para>
                     To create a Yocto BitBake Commander project, follow these steps:
                     <orderedlist>
-                        <listitem><para>Select "Other" from the 
-                            "Window -> Open Perspective" menu 
+                        <listitem><para>Select "Other" from the
+                            "Window -> Open Perspective" menu
                             and then choose "Bitbake Commander".</para></listitem>
                         <listitem><para>Click "OK" to change the perspective to
                             Bitbake Commander.</para></listitem>
                         <listitem><para>Select "Project" from the "File -> New"
                             menu to create a new Yocto
                             Bitbake Commander project.</para></listitem>
-                        <listitem><para>Choose "New Yocto Project" from the 
-                            "Yocto Project Bitbake Commander" menu and click 
+                        <listitem><para>Choose "New Yocto Project" from the
+                            "Yocto Project Bitbake Commander" menu and click
                             "Next".</para></listitem>
                         <listitem><para>Enter the Project Name and choose the Project Location.
                             The Yocto project's Metadata files will be put under the directory
@@ -1424,7 +1423,7 @@
                 <title>Editing the Metadata</title>
 
                 <para>
-                    After you create the Yocto Bitbake Commander project, you can modify the 
+                    After you create the Yocto Bitbake Commander project, you can modify the
                     <link linkend='metadata'>Metadata</link> files
                     by opening them in the project.
                     When editing recipe files (<filename>.bb</filename> files), you can view BitBake
@@ -1436,8 +1435,8 @@
                     To edit the Metadata, follow these steps:
                     <orderedlist>
                         <listitem><para>Select your Yocto Bitbake Commander project.</para></listitem>
-                        <listitem><para>Select "BitBake Recipe" from the 
-                        "File -> New -> Yocto BitBake Commander" menu 
+                        <listitem><para>Select "BitBake Recipe" from the
+                        "File -> New -> Yocto BitBake Commander" menu
                             to open a new recipe wizard.</para></listitem>
                         <listitem><para>Point to your source by filling in the "SRC_URL" field.
                             For example, you can add a recipe to your
@@ -1459,13 +1458,13 @@
                 <title>Building and Customizing the Image Using Hob</title>
 
                 <para>
-                    To build and customize the image using Hob from within the 
+                    To build and customize the image using Hob from within the
                     Eclipse IDE, follow these steps:
                     <orderedlist>
                         <listitem><para>Select your Yocto Bitbake Commander project.</para></listitem>
                         <listitem><para>Select "Launch Hob" from the "Project"
                             menu.</para></listitem>
-                        <listitem><para>Enter the 
+                        <listitem><para>Enter the
                             <link linkend='build-directory'>Build Directory</link>
                             where you want to put your final images.</para></listitem>
                         <listitem><para>Click "OK" to launch Hob.</para></listitem>
@@ -1508,7 +1507,7 @@
                     support development using actual hardware.
                     For example, the area might contain
                     <filename>.hddimg</filename> files that combine the
-                    kernel image with the filesystem, boot loaders, and 
+                    kernel image with the filesystem, boot loaders, and
                     so forth.
                     Be sure to get the files you need for your particular
                     development process.</para>
@@ -1879,9 +1878,9 @@
 
     <para>
         For a better understanding of Hob, see the project page at
-        <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'></ulink> 
+        <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'></ulink>
         on the Yocto Project website.
-        If you follow the "Documentation" link from the Hob page, you will 
+        If you follow the "Documentation" link from the Hob page, you will
         find a short introductory training video on Hob.
         The following lists some features of Hob:
         <itemizedlist>
@@ -1893,9 +1892,9 @@
             <listitem><para>You can set the
                 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
                 for which you are building the image.</para></listitem>
-            <listitem><para>You can modify various policy settings such as the 
+            <listitem><para>You can modify various policy settings such as the
                 package format with which to build,
-                the parallelism BitBake uses, whether or not to build an 
+                the parallelism BitBake uses, whether or not to build an
                 external toolchain, and which host to build against.
                 </para></listitem>
             <listitem><para>You can manage
diff --git a/documentation/kernel-dev/kernel-dev.xml b/documentation/kernel-dev/kernel-dev.xml
index c1c4660e07..702dda937d 100644
--- a/documentation/kernel-dev/kernel-dev.xml
+++ b/documentation/kernel-dev/kernel-dev.xml
@@ -71,7 +71,7 @@
       <note>
           Due to production processes, there could be differences between the Yocto Project
           documentation bundled in the release tarball and the
-          <ulink url='&YOCTO_DOCS_KERNEL_URL;'>Yocto Project Linux Kernel Development Manual</ulink> on
+          <ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;'>Yocto Project Linux Kernel Development Manual</ulink> on
           the <ulink url='&YOCTO_HOME_URL;'>Yocto Project</ulink> website.
           For the latest version of this manual, see the manual on the website.
       </note>
diff --git a/documentation/profile-manual/profile-manual-intro.xml b/documentation/profile-manual/profile-manual-intro.xml
index 9ed807f356..e8e0908733 100644
--- a/documentation/profile-manual/profile-manual-intro.xml
+++ b/documentation/profile-manual/profile-manual-intro.xml
@@ -4,7 +4,7 @@
 
 <chapter id='profile-manual-intro'>
 
-<title>Yocto Project Tracing and Profiling Manual</title>
+<title>Yocto Project Profiling and Tracing Manual</title>
     <section id='intro'>
         <title>Introduction</title>
 
diff --git a/documentation/profile-manual/profile-manual.xml b/documentation/profile-manual/profile-manual.xml
index 4c7a4f453b..ca00d84484 100644
--- a/documentation/profile-manual/profile-manual.xml
+++ b/documentation/profile-manual/profile-manual.xml
@@ -74,7 +74,7 @@
       <note>
           Due to production processes, there could be differences between the Yocto Project
           documentation bundled in the release tarball and the
-          <ulink url='&YOCTO_DOCS_PROF_URL;'>Yocto Project Tracing and Profiling Manual</ulink> on
+          <ulink url='&YOCTO_DOCS_PROF_URL;'>Yocto Project Profiling and Tracing Manual</ulink> on
           the <ulink url='&YOCTO_HOME_URL;'>Yocto Project</ulink> website.
           For the latest version of this manual, see the manual on the website.
       </note>