manuals: update former references to dev-manual/common-tasks

(From yocto-docs rev: f8bb4c392912f15bb78f6f25910f85897abb4e3d)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>

2 files changed, 4 insertions, 4 deletions

diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst
index c1a12f03ac..a0d513e8e9 100644
--- a/documentation/contributor-guide/recipe-style-guide.rst
+++ b/documentation/contributor-guide/recipe-style-guide.rst
@@ -231,13 +231,13 @@ Recipes need to define both the :term:`LICENSE` and
    differences result in an error with the message containing the
    current checksum. For more explanation and examples of how to set the
    :term:`LIC_FILES_CHKSUM` variable, see the
-   ":ref:`dev-manual/common-tasks:tracking license changes`" section.
+   ":ref:`dev-manual/licenses:tracking license changes`" section.
 
    To determine the correct checksum string, you can list the
    appropriate files in the :term:`LIC_FILES_CHKSUM` variable with incorrect
    md5 strings, attempt to build the software, and then note the
    resulting error messages that will report the correct md5 strings.
-   See the ":ref:`dev-manual/common-tasks:fetching code`" section for
+   See the ":ref:`dev-manual/new-recipe:fetching code`" section for
    additional information.
 
    Here is an example that assumes the software has a ``COPYING`` file::
diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst
index 65d8ea5343..cda2d12d25 100644
--- a/documentation/contributor-guide/submit-changes.rst
+++ b/documentation/contributor-guide/submit-changes.rst
@@ -377,7 +377,7 @@ mailing list, unless specified otherwise in the layer's ``README`` file.
 If you intend to submit a new recipe that neither fits into the core Metadata,
 nor into :oe_git:`meta-openembedded </meta-openembedded/>`, you should
 look for a suitable layer in https://layers.openembedded.org. If similar
-recipes can be expected, you may consider :ref:`dev-manual/common-tasks:creating your own layer`.
+recipes can be expected, you may consider :ref:`dev-manual/layers:creating your own layer`.
 
 If in doubt, please ask on the :yocto_lists:`yocto </g/yocto/>` general mailing list
 or on the :oe_lists:`openembedded-devel </g/openembedded-devel>` mailing list.
@@ -625,7 +625,7 @@ follows:
 #. *Identify the bug or CVE to be fixed:* This information should be
    collected so that it can be included in your submission.
 
-   See :ref:`dev-manual/common-tasks:checking for vulnerabilities`
+   See :ref:`dev-manual/vulnerabilities:checking for vulnerabilities`
    for details about CVE tracking.
 
 #. *Check if the fix is already present in the master branch:* This will