documentation: Purged overview manual references

When I converted the Yocto Project Overview Manual to the Getting
Started With Yocto Project Manual, I updated the strings for
references from "&YOCTO_DOCS_OVERVIEW_URL" TO
"&YOCTO_DOCS_GS_URL".  Unfortunately, I did it with a global command
that did not take into account the text the might follow the link
by saying "see such-and-such section in the Yocto Project Overview
Manual."  So, I had to hand fix these.

Additionally, since I have moved a deeper concepts chapter that
was in the getting-started manual to a new Yocto Project Concepts
chapter, many of those links changed had to really go to the new
manual instead.  Those were fixed.

(From yocto-docs rev: fca1c56b0764802fb6a687ea81ab0fb95186cf0a)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 18 insertions, 18 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index f420a14f5a..3ac223159b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1508,7 +1508,7 @@
                 <note>
                     For information on recipe syntax, see the
                     "<ulink url='&YOCTO_DOCS_GS_URL;#recipe-syntax'>Recipe Syntax</ulink>"
-                    section in the Yocto Project Overview Manual.
+                    section in the Getting Started With Yocto Project Manual.
                 </note>
             </para>
 
@@ -1799,7 +1799,7 @@
             <para>
                 You can find more information about the build process in
                 "<ulink url='&YOCTO_DOCS_GS_URL;#overview-development-environment'>The Yocto Project Development Environment</ulink>"
-                chapter of the Yocto Project Overview Manual.
+                chapter of the Getting Started With Yocto Project Manual.
             </para>
         </section>
 
@@ -1816,7 +1816,7 @@
                 that points to where the source is located.
                 For a graphical representation of source locations, see the
                 "<ulink url='&YOCTO_DOCS_GS_URL;#sources-dev-environment'>Sources</ulink>"
-                section in the Yocto Project Overview Manual.
+                section in the Getting Started With Yocto Project Manual.
             </para>
 
             <para>
@@ -2128,8 +2128,8 @@
                         containing the current checksum.
                         For more explanation and examples of how to set the
                         <filename>LIC_FILES_CHKSUM</filename> variable, see the
-                        "<ulink url='&YOCTO_DOCS_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
-                        section in the Yocto Project Overview Manual.</para>
+                        "<ulink url='&YOCTO_DOCS_CM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
+                        section in the Yocto Project Concepts Manual.</para>
                         <para>To determine the correct checksum string, you
                         can list the appropriate files in the
                         <filename>LIC_FILES_CHKSUM</filename> variable with
@@ -2275,8 +2275,8 @@
                 automatically add a runtime dependency to "mypackage" on
                 "example").
                 See the
-                "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
-                in the Yocto Project Overview Manual for further details.
+                "<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
+                in the Yocto Project Concepts Manual for further details.
             </para>
         </section>
 
@@ -3211,8 +3211,8 @@
                     The variable
                     <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</ulink></filename>
                     is used to track source license changes as described in the
-                    "<ulink url='&YOCTO_DOCS_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
-                    section in the Yocto Project Overview Manual.
+                    "<ulink url='&YOCTO_DOCS_CM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
+                    section in the Yocto Project Concepts Manual.
                     You can quickly create Autotool-based recipes in a manner similar to the previous example.
                 </para>
             </section>
@@ -3418,8 +3418,8 @@
                                 allows runtime dependencies between packages
                                 to be added automatically.
                                 See the
-                                "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
-                                section in the Yocto Project Overview Manual
+                                "<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
+                                section in the Yocto Project Concepts Manual
                                 for more information.
                                 </para></listitem>
                         </itemizedlist>
@@ -4543,8 +4543,8 @@
             architectures.
             <note>
                 For more information on x32 psABI, see the
-                "<ulink url='&YOCTO_DOCS_GS_URL;#x32'>x32 psABI</ulink>"
-                section in the Yocto Project Overview Manual.
+                "<ulink url='&YOCTO_DOCS_CM_URL;#x32'>x32 psABI</ulink>"
+                section in the Yocto Project Concepts Manual.
             </note>
             To use the x32 psABI, you need to edit your
             <filename>conf/local.conf</filename> configuration file as
@@ -7347,7 +7347,7 @@ Some notes from Cal:
 
                 <para>
                     Because the OpenEmbedded build system uses
-                    "<ulink url='&YOCTO_DOCS_GS_URL;#overview-checksums'>signatures</ulink>",
+                    "<ulink url='&YOCTO_DOCS_CM_URL;#overview-checksums'>signatures</ulink>",
                     which are unique to a given build, the build system
                     knows when to rebuild packages.
                     All the inputs into a given task are represented by a
@@ -7451,8 +7451,8 @@ Some notes from Cal:
 
                     <para>
                         For more information on shared state, see the
-                        "<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>Shared State Cache</ulink>"
-                        section in the Yocto Project Overview Manual.
+                        "<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>Shared State Cache</ulink>"
+                        section in the Yocto Project Concepts Manual.
                     </para>
                 </note>
             </section>
@@ -11134,8 +11134,8 @@ Some notes from Cal:
                 considers it "out of date".
                 See the
                 "<ulink url='&YOCTO_DOCS_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
-                section in the Yocto Project Overview Manual for how BitBake
-                determines whether a task is "out of date".
+                section in the Getting Started With Yocto Project Manual for
+                how BitBake determines whether a task is "out of date".
             </para>
 
             <para>