docs: Fix broken page links

6 files changed, 6 insertions, 6 deletions

diff --git a/docs/markdown/Adding-arguments.md b/docs/markdown/Adding-arguments.md
index e049e82..0bf5944 100644
--- a/docs/markdown/Adding-arguments.md
+++ b/docs/markdown/Adding-arguments.md
@@ -15,7 +15,7 @@ Global compiler arguments are set with the following command. As an example you
 add_global_arguments('-DFOO=bar', language : 'c')
 ```
 
-This makes Meson add the define to all C compilations. Usually you would use this setting for flags for global settings. Note that for setting the C/C++ language standard (the `-std=c99` argument in GCC), you would probably want to use a default option of the `project()` function. For details see the [reference manual](Reference manual).
+This makes Meson add the define to all C compilations. Usually you would use this setting for flags for global settings. Note that for setting the C/C++ language standard (the `-std=c99` argument in GCC), you would probably want to use a default option of the `project()` function. For details see the [reference manual](Reference-manual.md).
 
 Global arguments have certain limitations. They all have to be defined before any build targets are specified. This ensures that the global flags are the same for every single source file built in the entire project with one exception. Compilation tests that are run as part of your project configuration do not use these flags. The reason for that is that you may need to run a test compile with and without a given flag to determine your build setup. For this reason tests do not use these global arguments.
 
diff --git a/docs/markdown/Comparisons.md b/docs/markdown/Comparisons.md
index 4ceb930..eb0e4dd 100644
--- a/docs/markdown/Comparisons.md
+++ b/docs/markdown/Comparisons.md
@@ -50,7 +50,7 @@ Implemented in Java. Poor Windows support. Heavily focused on Google's way of do
 
 ### Pros ###
 
-The fastest build system [see measurements](Performance comparison), user friendly, designed to be as invisible to the developer as possible, native support for modern tools (precompiled headers, coverage, Valgrind etc). Not Turing complete so build definition files are easy to read and understand.
+The fastest build system [see measurements](Performance-comparison.md), user friendly, designed to be as invisible to the developer as possible, native support for modern tools (precompiled headers, coverage, Valgrind etc). Not Turing complete so build definition files are easy to read and understand.
 
 ### Cons ###
 
diff --git a/docs/markdown/Compiler-properties.md b/docs/markdown/Compiler-properties.md
index c33d917..83fc0d9 100644
--- a/docs/markdown/Compiler-properties.md
+++ b/docs/markdown/Compiler-properties.md
@@ -10,7 +10,7 @@ Here we extract the C compiler. We could also have given the argument `cpp` to g
 
 ## System information
 
-This is a bit complex and more thoroughly explained on the page on [cross compilation](Cross compilation). But if you just want to know the operating system your code will run on, issue this command:
+This is a bit complex and more thoroughly explained on the page on [cross compilation](Cross-compilation.md). But if you just want to know the operating system your code will run on, issue this command:
 
 ```meson
 host_machine.system()
diff --git a/docs/markdown/Creating-Linux-binaries.md b/docs/markdown/Creating-Linux-binaries.md
index 13940b5..3c48122 100644
--- a/docs/markdown/Creating-Linux-binaries.md
+++ b/docs/markdown/Creating-Linux-binaries.md
@@ -50,7 +50,7 @@ Old distros might have too old versions of some tools. For Meson this could incl
 
 ## Adding dependencies
 
-You want to embed and statically link every dependency you can (especially C++ dependencies). Meson's [Wrap package manager might be of use here](Wrap dependency system manual). This is equivalent to what you would do on Windows, OSX, Android etc. Sometimes static linking is not possible. In these cases you need to copy the .so files inside your package. Let's use SDL2 as an example. First we download and install it as usual giving it our custom install prefix (that is, `./configure --prefix=${HOME}/devroot`). This makes Meson's dependency detector pick it up automatically.
+You want to embed and statically link every dependency you can (especially C++ dependencies). Meson's [Wrap package manager](Wrap-dependency-system-manual.md) might be of use here. This is equivalent to what you would do on Windows, OSX, Android etc. Sometimes static linking is not possible. In these cases you need to copy the .so files inside your package. Let's use SDL2 as an example. First we download and install it as usual giving it our custom install prefix (that is, `./configure --prefix=${HOME}/devroot`). This makes Meson's dependency detector pick it up automatically.
 
 ## Building and installing
 
diff --git a/docs/markdown/Reference-manual.md b/docs/markdown/Reference-manual.md
index c835f6f..fab317d 100644
--- a/docs/markdown/Reference-manual.md
+++ b/docs/markdown/Reference-manual.md
@@ -345,7 +345,7 @@ If you want to generate files for general purposes such as for generating header
     value get_option(option_name)
 ```
 
-Obtains the value of the [project build option](Build options) specified in the positional argument.
+Obtains the value of the [project build option](Build-options.md) specified in the positional argument.
 
 ### get_variable()
 
diff --git a/docs/markdown/Subprojects.md b/docs/markdown/Subprojects.md
index b91366d..2dd012e 100644
--- a/docs/markdown/Subprojects.md
+++ b/docs/markdown/Subprojects.md
@@ -69,4 +69,4 @@ This uses the system dependency when available and the self built version if not
 
 # Obtaining subprojects
 
-Meson ships with a dependency system to automatically obtain dependency subprojects. It is documented in the [Wrap dependency system manual](Wrap dependency system manual).
+Meson ships with a dependency system to automatically obtain dependency subprojects. It is documented in the [Wrap dependency system manual](Wrap-dependency-system-manual.md).