diff --git a/src/contributing/direct_contributions/creating_proper_bug_reports.md b/src/contributing/direct_contributions/creating_proper_bug_reports.md
index 4fb3367f8fb7184b59ce20f15f403c49486e2d02..30ae867175b67f02f48a017be4d7202a67a9d739 100644
--- a/src/contributing/direct_contributions/creating_proper_bug_reports.md
+++ b/src/contributing/direct_contributions/creating_proper_bug_reports.md
@@ -11,7 +11,7 @@
     * `qemu-system-x86_64 -version` or your actual hardware specs, if applicable
   * The operating system you used to build Redox
     * `uname -a` or an alternative format
-4. Make sure that your bug doesn't already have an issue on GitLab. If you submit a duplicate, you should accept that you may be ridiculed for it, though you'll still be helped. Feel free to ask in the Redox [chat](./contributing/communication/chat.html) if you're uncertain as to whether your issue is new
+4. Make sure that your bug doesn't already have an issue on GitLab. If you submit a duplicate, you should accept that you may be ridiculed for it, though you'll still be helped. Feel free to ask in the Redox [chat](../communication/chat.html) if you're uncertain as to whether your issue is new
 5. Create a GitLab issue following the template
     * Non-bug report issues may ignore this template
 6. Watch the issue and be available for questions
diff --git a/src/contributing/direct_contributions/creating_proper_pull_requests.md b/src/contributing/direct_contributions/creating_proper_pull_requests.md
index 0f92bc20571ca16e844c6dd9fcc282807eae1daa..e811fd01f2e2fa397bf26872a0e1e6c9990c5eb0 100644
--- a/src/contributing/direct_contributions/creating_proper_pull_requests.md
+++ b/src/contributing/direct_contributions/creating_proper_pull_requests.md
@@ -21,7 +21,7 @@ The steps given below are for the main Redox project - submodules and other proj
 8. Commit (`git add . --all; git commit -m "my commit"`)
 9. Optionally run [rustfmt](https://gitlab.redox-os.org/rust-lang-nursery/rustfmt) on the files you changed and commit again if it did anything (check with `git diff` first)
 10. Test your changes with `make qemu` or `make virtualbox` (you might have to use `make qemu kvm=no`, formerly `make qemu_no_kvm`)
-(see [Best Practices and Guidelines](./contributing/best_practices/overview.html))
+(see [Best Practices and Guidelines](../best_practices/overview.html))
 11. Pull from upstream (`git fetch upstream; git rebase upstream/master`) (Note: try not to use `git pull`, it is equivalent to doing `git fetch upstream; git merge master upstream/master`, which is not usually preferred for local/fork repositories, although it is fine in some cases.)
 12. Repeat step 9 to make sure the rebase still builds and starts
 13. Push to your fork (`git push origin my-branch`)
diff --git a/src/contributing/direct_contributions/pull_requests.md b/src/contributing/direct_contributions/pull_requests.md
index fc1cdfee93b8b8bc4738ad82b6100be5a51a6161..79f6aef9bc1487bbee7a81840a510284b40cc034 100644
--- a/src/contributing/direct_contributions/pull_requests.md
+++ b/src/contributing/direct_contributions/pull_requests.md
@@ -1,3 +1,3 @@
 # Pull Requests
 
-It's completely fine to just submit a small pull request without first making an issue, but if it's a big change that will require a lot of planning and reviewing, it's best you start with writing an issue first. Also see the [git guidelines](./contributing/best_practices/git.html).
+It's completely fine to just submit a small pull request without first making an issue, but if it's a big change that will require a lot of planning and reviewing, it's best you start with writing an issue first. Also see the [git guidelines](../best_practices/git.html).
diff --git a/src/design/url/how_it_works.md b/src/design/url/how_it_works.md
index aaea9ad293b7c480ea068376de0619d004865cd4..ce506ae124ecf0b904eab165db7e6fbbd389f7d9 100644
--- a/src/design/url/how_it_works.md
+++ b/src/design/url/how_it_works.md
@@ -29,4 +29,4 @@ The path argument of `OPEN` does not have to be a URL. For compatibility reasons
 
 > TODO
 
-[The root scheme]: design/scheme/the_root_scheme.html
+[The root scheme]: ../scheme/the_root_scheme.html
diff --git a/src/explore/boot_process.md b/src/explore/boot_process.md
index bb67e04d3c9ce8b8881f2ad14210abf55920889b..3cf37319c3eaeddd5013ffa22e811788dee1e7b6 100644
--- a/src/explore/boot_process.md
+++ b/src/explore/boot_process.md
@@ -84,7 +84,7 @@ The login program accepts a username, currently any username may be used, prints
 ############################
 ```
 
-At this point, the user will now be able to access the [Shell](./explore/shell.html)
+At this point, the user will now be able to access the [Shell](./shell.html)
 
 ## Graphical overview
 
diff --git a/src/explore/explore.md b/src/explore/explore.md
index 0764161ef3b9ac83d4569ed827291d963aac133c..b0786de7be44fabe63931f930b804894520067c1 100644
--- a/src/explore/explore.md
+++ b/src/explore/explore.md
@@ -6,7 +6,7 @@ We will start with the boot system, continuing to the shell and command-line uti
 
 Redox is meant to be an *insanely* customizable system, allowing a user to tear it down to a very small command-line distro, or build it up to a full desktop environment with ease.
 
-- [Boot Process](./explore/boot_process.html)
-- [Shell](./explore/shell.html)
+- [Boot Process](./boot_process.html)
+- [Shell](./shell.html)
 - [Utilities](./explore/utilities.html)
-- [GUI](./explore/gui.html)
+- [GUI](./gui.html)
diff --git a/src/introduction/how_redox_compares_to_other_operating_systems.md b/src/introduction/how_redox_compares_to_other_operating_systems.md
index 8f8a94983db87daaa97d9852b4ff1d53b12afc17..4b9a31bcfe19fb2851fa20a1ac11c1487679271b 100644
--- a/src/introduction/how_redox_compares_to_other_operating_systems.md
+++ b/src/introduction/how_redox_compares_to_other_operating_systems.md
@@ -40,4 +40,4 @@ The main idea is to have components and drivers that would be inside a monolithi
 All of this increases the reliability of the system significantly. This would be useful for mission-critical applications and for users that want minimal issues with their computer systems.
 
 
-[URLs, schemes, and resources]: ./design/urls_schemes_resources.html
+[URLs, schemes, and resources]: ../design/urls_schemes_resources.html
diff --git a/src/introduction/what_is_redox.md b/src/introduction/what_is_redox.md
index d6059b7146d7df75a1ba6e9a265f69621be1dd6f..9f05bc380991d6c6360fcef2745342ebbc1f126c 100644
--- a/src/introduction/what_is_redox.md
+++ b/src/introduction/what_is_redox.md
@@ -23,5 +23,5 @@ This means that a large number of standard programs and libraries will be compat
 
 The key here is the trade off between correctness and compatibility. Ideally, you should be able achieve both, but unfortunately, you can't always do so.
 
-[Why Free Software]: ./introduction/why_free_software.html
-[Why Rust]: ./introduction/why_rust.html
+[Why Free Software]: ./why_free_software.html
+[Why Rust]: ./why_rust.html
diff --git a/src/introduction/why_redox.md b/src/introduction/why_redox.md
index 92a4d7718e760dcea8eca5efe1cf49a71c021f57..5ad4ab52817a71f13ef9cc93d9526e11492804d2 100644
--- a/src/introduction/why_redox.md
+++ b/src/introduction/why_redox.md
@@ -48,7 +48,7 @@ We have to admit, that we do like the idea of writing something that is our own
 - User space written mostly in Rust
 - Orbital, a new GUI
 
-[Why Free Software]: ./introduction/why_free_software.html
+[Why Free Software]: ./why_free_software.html
 [jails]: https://www.freebsd.org/doc/handbook/jails.html
 [ZFS]: https://www.freebsd.org/doc/handbook/zfs.html
 [reliability]: http://wiki.minix3.org/doku.php?id=www:documentation:reliability
diff --git a/src/overview/community.md b/src/overview/community.md
index ddb0937cd4b63f4eca05300591169c6daf06ee08..ccd73205e06db6dc386377955f7286c76e7e101e 100644
--- a/src/overview/community.md
+++ b/src/overview/community.md
@@ -58,7 +58,7 @@ But [don't]. [forget]. [all]. [the]. [other]. [awesome]. [contributors].
 [stratact]: https://gitlab.redox-os.org/stratact
 [ticki]: https://github.com/ticki
 
-[this list]: ./overview/maintainers.html
+[this list]: ./maintainers.html
 
 [don't]: https://gitlab.redox-os.org/redox-os/redox/graphs/master
 [forget]: https://gitlab.redox-os.org/redox-os/coreutils/graphs/master
diff --git a/src/overview/side_projects.md b/src/overview/side_projects.md
index 5364caa776dab886adbbc8a6bc4c90f335c60cca..7a343419a66def1b8952b6a118a683c217e30c8d 100644
--- a/src/overview/side_projects.md
+++ b/src/overview/side_projects.md
@@ -59,4 +59,4 @@ It is important to note we seek to avoid non-Rust tools, for safety and consiste
 [uutils/coreutils]: https://github.com/uutils/coreutils
 [m-labs/smoltcp]: https://github.com/m-labs/smoltcp
 
-[Why Rust]: ./introduction/why_rust.html
+[Why Rust]: ../introduction/why_rust.html
diff --git a/src/overview/welcome.md b/src/overview/welcome.md
index 4e54de2bb1849042e1a9de5d941101c071f0e7d6..94125883073d1dd86c9414080f9c4fee0112e3d0 100644
--- a/src/overview/welcome.md
+++ b/src/overview/welcome.md
@@ -7,4 +7,4 @@ Please notice that this book is currently being written.
 
 This book was written by Ticki with the help of LazyOxen, Steve Klabnik, ElijahCaine, and Jackpot51.
 
-If you want to skip straight to trying out Redox, see [getting started](getting_started/getting_started.html).
+If you want to skip straight to trying out Redox, see [getting started](../getting_started/getting_started.html).
diff --git a/src/overview/what_redox_is.md b/src/overview/what_redox_is.md
index e946cd09f1d0efe313ed640e13cc832852d16dfe..6049acdad23c19cf870920970138d30306acc6e3 100644
--- a/src/overview/what_redox_is.md
+++ b/src/overview/what_redox_is.md
@@ -37,9 +37,9 @@ It is written such that you do not need any prior knowledge in Rust and/or OS de
 [Linux]: https://en.wikipedia.org/wiki/Linux
 [BSD]: http://www.bsd.org/
 
-[Design]: ./design/design.html
-[Overview]: ./overview/welcome.html
-[Introduction]: ./introduction/why_redox.html
-[Getting started]: ./getting_started/preparing_the_build.html
-[The design]: ./design/design.html
-[Contributing]: ./contributing/chat.html
+[Design]: ../design/design.html
+[Overview]: ./welcome.html
+[Introduction]: ../introduction/why_redox.html
+[Getting started]: ../getting_started/preparing_the_build.html
+[The design]: ../design/design.html
+[Contributing]: ../contributing/chat.html