@@ -189,7 +189,7 @@ external source tree.
run your application. If dependent packages (e.g. libraries) do not
exist on the target, your application, when run, will fail to find
those functions. For more information, see the
- ":ref:`ref-manual/devtool-reference:deploying your software on the target machine`"
+ ":ref:`devtool-deploying-your-software-on-the-target-machine`"
section.
By default, ``devtool add`` uses the latest revision (i.e. master) when
@@ -555,7 +555,7 @@ Removing Your Software from the Target Machine
Use the ``devtool undeploy-target`` command to remove deployed build
output from the target machine. For the ``devtool undeploy-target``
command to work, you must have previously used the
-":ref:`devtool deploy-target <ref-manual/devtool-reference:deploying your software on the target machine>`"
+":ref:`devtool deploy-target <devtool-deploying-your-software-on-the-target-machine>`"
command::
$ devtool undeploy-target recipe target
@@ -599,7 +599,7 @@ The ``devtool status`` command has no command-line options::
$ devtool status
Following is sample output after using
-:ref:`devtool add <ref-manual/devtool-reference:adding a new recipe to the workspace layer>`
+:ref:`devtool add <devtool-adding-a-new-recipe-to-the-workspace>`
to create and add the ``mtr_0.86.bb`` recipe to the ``workspace`` directory::
$ devtool status
@@ -15,7 +15,7 @@ Major and Minor Release Cadence
The Yocto Project delivers major releases (e.g. &DISTRO;) using a six
month cadence roughly timed each April and October of the year.
Following are examples of some major YP releases with their codenames
-also shown. See the ":ref:`ref-manual/release-process:major release codenames`"
+also shown. See the "`Major Release Codenames`_"
section for information on codenames used with major releases.
- 2.2 (Morty)