sphinx: manual updates for some links

Some links were not found by the regexp, especially because of they
are spanning across multiple lines. This patch is a manual fixup for
these patterns.

(From yocto-docs rev: 7a5cf8b372903d959d4a1f0882e6198f31f3cba5)

Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

5 files changed, 15 insertions, 18 deletions

diff --git a/documentation/sdk-manual/sdk-appendix-customizing.rst b/documentation/sdk-manual/sdk-appendix-customizing.rst
index 8169f2bed8..3bb6ef3a19 100644
--- a/documentation/sdk-manual/sdk-appendix-customizing.rst
+++ b/documentation/sdk-manual/sdk-appendix-customizing.rst
@@ -150,7 +150,7 @@ set. If the ``DISTRO_NAME`` variable is not set, the title is derived
 from the :term:`DISTRO` variable.
 
 The
-```populate_sdk_base`` <&YOCTO_DOCS_REF_URL;#ref-classes-populate-sdk-*>`__
+:ref:`populate_sdk_base <ref-classes-populate-sdk-*>`
 class defines the default value of the ``SDK_TITLE`` variable as
 follows: SDK_TITLE ??= "${@d.getVar('DISTRO_NAME') or
 d.getVar('DISTRO')} SDK"
@@ -212,7 +212,7 @@ installation directory for the SDK is based on the
 :term:`DISTRO` and
 :term:`SDKEXTPATH` variables from
 within the
-```populate_sdk_base`` <&YOCTO_DOCS_REF_URL;#ref-classes-populate-sdk-*>`__
+:ref:`populate_sdk_base <ref-classes-populate-sdk-*>`
 class as follows: SDKEXTPATH ??= "~/${@d.getVar('DISTRO')}_sdk" You can
 change this default installation directory by specifically setting the
 ``SDKEXTPATH`` variable.
@@ -276,8 +276,8 @@ source, you need to do a number of things:
 
    -  Alternatively, if you just want to set the ``SSTATE_MIRRORS``
       variable's value for the SDK alone, create a
-      ``conf/sdk-extra.conf`` file either in your `Build
-      Directory <&YOCTO_DOCS_REF_URL;#build-directory>`__ or within any
+      ``conf/sdk-extra.conf`` file either in your
+      :term:`Build Directory` or within any
       layer and put your ``SSTATE_MIRRORS`` setting within that file.
 
       .. note::
diff --git a/documentation/sdk-manual/sdk-appendix-obtain.rst b/documentation/sdk-manual/sdk-appendix-obtain.rst
index c6efdf674c..015506de01 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.rst
+++ b/documentation/sdk-manual/sdk-appendix-obtain.rst
@@ -70,8 +70,8 @@ build the SDK installer. Follow these steps:
    machine that uses CROPS.
 
 2. *Clone the ``poky`` Repository:* You need to have a local copy of the
-   Yocto Project `Source
-   Directory <&YOCTO_DOCS_REF_URL;#source-directory>`__ (i.e. a local
+   Yocto Project :term:`Source Directory`
+   (i.e. a local
    ``poky`` repository). See the "`Cloning the ``poky``
    Repository <&YOCTO_DOCS_DEV_URL;#cloning-the-poky-repository>`__" and
    possibly the "`Checking Out by Branch in
@@ -87,8 +87,8 @@ build the SDK installer. Follow these steps:
    ````` <&YOCTO_DOCS_REF_URL;#structure-core-script>`__ environment
    setup script to define the OpenEmbedded build environment on your
    build host. $ source OE_INIT_FILE Among other things, the script
-   creates the `Build
-   Directory <&YOCTO_DOCS_REF_URL;#build-directory>`__, which is
+   creates the :term:`Build Directory`,
+   which is
    ``build`` in this case and is located in the Source Directory. After
    the script runs, your current working directory is set to the
    ``build`` directory.
diff --git a/documentation/sdk-manual/sdk-extensible.rst b/documentation/sdk-manual/sdk-extensible.rst
index 17cd08a25c..3df2174fd9 100644
--- a/documentation/sdk-manual/sdk-extensible.rst
+++ b/documentation/sdk-manual/sdk-extensible.rst
@@ -9,8 +9,8 @@ Information covers the pieces of the SDK, how to install it, and
 presents a look at using the ``devtool`` functionality. The extensible
 SDK makes it easy to add new applications and libraries to an image,
 modify the source for an existing component, test changes on the target
-hardware, and ease integration into the rest of the `OpenEmbedded build
-system <&YOCTO_DOCS_REF_URL;#build-system-term>`__.
+hardware, and ease integration into the rest of the
+:term:`OpenEmbedded Build System`.
 
 .. note::
 
diff --git a/documentation/sdk-manual/sdk-intro.rst b/documentation/sdk-manual/sdk-intro.rst
index fcb15a8592..88238d7dd4 100644
--- a/documentation/sdk-manual/sdk-intro.rst
+++ b/documentation/sdk-manual/sdk-intro.rst
@@ -39,8 +39,7 @@ All SDKs consist of the following:
 Additionally, an extensible SDK has tools that allow you to easily add
 new applications and libraries to an image, modify the source of an
 existing component, test changes on the target hardware, and easily
-integrate an application into the `OpenEmbedded build
-system <&YOCTO_DOCS_REF_URL;#build-system-term>`__.
+integrate an application into the :term:`OpenEmbedded Build System`.
 
 You can use an SDK to independently develop and test code that is
 destined to run on some target machine. SDKs are completely
@@ -126,8 +125,7 @@ of a cross-compiler, cross-linker, and cross-debugger that are used to
 develop user-space applications for targeted hardware. Additionally, for
 an extensible SDK, the toolchain also has built-in ``devtool``
 functionality. This toolchain is created by running a SDK installer
-script or through a `Build
-Directory <&YOCTO_DOCS_REF_URL;#build-directory>`__ that is based on
+script or through a :term:`Build Directory` that is based on
 your metadata configuration or extension for your targeted device. The
 cross-toolchain works with a matching target sysroot.
 
@@ -149,8 +147,8 @@ The QEMU emulator allows you to simulate your hardware while running
 your application or image. QEMU is not part of the SDK but is made
 available a number of different ways:
 
--  If you have cloned the ``poky`` Git repository to create a `Source
-   Directory <&YOCTO_DOCS_REF_URL;#source-directory>`__ and you have
+-  If you have cloned the ``poky`` Git repository to create a
+   :term:`Source Directory` and you have
    sourced the environment setup script, QEMU is installed and
    automatically available.
 
diff --git a/documentation/sdk-manual/sdk-working-projects.rst b/documentation/sdk-manual/sdk-working-projects.rst
index 63f61de66d..d18568d60a 100644
--- a/documentation/sdk-manual/sdk-working-projects.rst
+++ b/documentation/sdk-manual/sdk-working-projects.rst
@@ -14,8 +14,7 @@ Once you have a suitable `cross-development
 toolchain <&YOCTO_DOCS_REF_URL;#cross-development-toolchain>`__
 installed, it is very easy to develop a project using the `GNU
 Autotools-based <https://en.wikipedia.org/wiki/GNU_Build_System>`__
-workflow, which is outside of the `OpenEmbedded build
-system <&YOCTO_DOCS_REF_URL;#build-system-term>`__.
+workflow, which is outside of the :term:`OpenEmbedded Build System`.
 
 The following figure presents a simple Autotools workflow.