diff --git a/website/docs/configure-renovate.md b/website/docs/configure-renovate.md
index 354fcf13a05fab92bdee9fec0eaab0679e65d4d0..6d105f4853ff226433d5781ab74258cb9e78064a 100644
--- a/website/docs/configure-renovate.md
+++ b/website/docs/configure-renovate.md
@@ -11,7 +11,7 @@ Once you have enabled Renovate on a repository, you will receive a "Configure Re
 
 ## No Risk Onboarding
 
-Conveniently, Renovate will not make any changes to your repository or raise any further Pull Requests until after you _merge_ this initial Pull Request. So if there is anything about the Pull Request that you don't like or understand, take your time to read [documentation](/docs/) or ask questions in one of our support forums and merge the PR only once you're satisfied with the result. You can edit your Renovate configuration **within this `renovate/configure` branch** and Renovate will keep updating the description in the PR to match, so you can keep doing that until you're satisfied with the results.
+Conveniently, Renovate will not make any changes to your repository or raise any further Pull Requests until after you _merge_ this initial Pull Request. So if there is anything about the Pull Request that you don't like or understand, take your time to read [documentation](./) or ask questions in one of our support forums and merge the PR only once you're satisfied with the result. You can edit your Renovate configuration **within this `renovate/configure` branch** and Renovate will keep updating the description in the PR to match, so you can keep doing that until you're satisfied with the results.
 
 ## Check for Warnings
 
diff --git a/website/docs/node.md b/website/docs/node.md
index d01def0eaa3ddb5dd667be042b6173ecf3536c82..587958947b560c948a984f2fe9f727963a7d49e8 100644
--- a/website/docs/node.md
+++ b/website/docs/node.md
@@ -28,7 +28,7 @@ When Renovate processes your project's repository it will look for the files lis
 
 ## Configuring Support Policy
 
-Renovate supports a [`supportPolicy`](/docs/configuration-options/#supportpolicy) option that can be passed the following values and associated versions (current as of December 2017):
+Renovate supports a [`supportPolicy`](configuration-options/#supportpolicy) option that can be passed the following values and associated versions (current as of December 2017):
 
 **Default:** `lts`
 
@@ -50,4 +50,4 @@ For example, to instruct Renovate to upgrade your project to the latest [Long-te
 
 It's best to define this support policy inside the `node` configuration object so that it is applied to all Node.js-related files.
 
-For additional language support see the [`supportPolicy` documentation](/docs/configuration-options/#supportpolicy).
+For additional language support see the [`supportPolicy` documentation](configuration-options/#supportpolicy).
diff --git a/website/docs/noise-reduction.md b/website/docs/noise-reduction.md
index 4b8cfa0b1afb2423d5b41fd4d85182cf74192c8a..b997113b441b26583f4dea7ef3d19c12a6dd03ed 100644
--- a/website/docs/noise-reduction.md
+++ b/website/docs/noise-reduction.md
@@ -13,7 +13,7 @@ Of course, please keep in mind that people's definitions of "noise" may differ.
 
 To reduce noise, you can reduce the number of updates in total, and a good way to do that is via intelligent grouping of related packages.
 
-As an example, our default `":app"` and `":library"` [presets](/docs/config-presets/) include the rule `"group:monorepos"`, which means that "sibling" packages from known monorepos will always be grouped into the same branch/PR by renovate. For example, all `@angular/*` packages that are updated at the same time will be raised in a "Renovate angular monorepo packages" PR. And every package in the React monorepo will be grouped together in a React monorepo PR too.
+As an example, our default `":app"` and `":library"` [presets](config-presets/) include the rule `"group:monorepos"`, which means that "sibling" packages from known monorepos will always be grouped into the same branch/PR by renovate. For example, all `@angular/*` packages that are updated at the same time will be raised in a "Renovate angular monorepo packages" PR. And every package in the React monorepo will be grouped together in a React monorepo PR too.
 
 You may wish to take this further, for example you might want to group together all packages related to `eslint`, even if they come from separate repositories/authors. In that case you might add config like this: