@@ -173,7 +173,7 @@ Here is a list of resources you might find helpful:
- :yocto_wiki:`FAQ </FAQ>`: A list of commonly asked
questions and their answers.
-- :yocto_docs:`Release Information </migration-guides/>`:
+- :doc:`Release Information </migration-guides/index>`:
Migration guides, release notes, new features, updates and known issues
for the current and past releases of the Yocto Project.
@@ -8481,7 +8481,7 @@ system and gives an overview of their function and contents.
responsibility to ensure that the toolchain is compatible with the
default toolchain. Using older or newer versions of these
components might cause build problems. See
- :yocto_docs:`Release Information </migration-guides/>` for your
+ :doc:`Release Information </migration-guides/index>` for your
version of the Yocto Project, to find the specific components with
which the toolchain must be compatible.
@@ -24,8 +24,8 @@ reproducibility matters. The primary focus of the project is the ability to
detect security issues being introduced. However, from a Yocto Project
perspective, it is also hugely important that our builds are deterministic. When
you build a given input set of metadata, we expect you to get consistent output.
-This has always been a key focus but, :yocto_docs:`since release 3.1 ("dunfell")
-</ref-manual/migration-3.1.html#reproducible-builds-now-enabled-by-default>`,
+This has always been a key focus but, :ref:`since release 3.1 ("dunfell")
+<migration-guides/migration-3.1:reproducible builds now enabled by default>`,
it is now true down to the binary level including timestamps.
For example, at some point in the future life of a product, you find that you