diff --git a/README.md b/README.md
index bd6270c..44c45ee 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
 loot.github.io
 ==============
 
-This repository acts as the main LOOT team repository, and holds all the issues and wiki pages that aren't specific to the code or any one game. In addition to that, it also holds LOOT's static website.
+This repository acts as the main LOOT team repository, and holds all the issues that aren't specific to the code or any one game. In addition to that, it also holds LOOT's static website.
 
 The static website is a [Jekyll](http://jekyllrb.com/) site that uses [Material Design Lite](http://www.getmdl.io/) components and the [js-yaml](https://github.com/nodeca/js-yaml) library, which are provided by Google and Cloudflare CDNs respectively.
 
diff --git a/docs/contributing/How-To-Contribute.html b/docs/contributing/How-To-Contribute.html
index 2a3923c..8781a91 100644
--- a/docs/contributing/How-To-Contribute.html
+++ b/docs/contributing/How-To-Contribute.html
@@ -35,7 +35,7 @@ title: How To Contribute
 
 <h3 id="joining-the-team">Joining the Team</h3>
 
-<p>Contributors can ask or be asked to join the LOOT team, which grants write access to the LOOT repositories, their issue trackers and wikis. Addition of new team members is done by the team admins, who base their decision on the quality of past contributions. If you would like to join the team, and feel comfortable with the workflow, contact a <a href="https://github.com/orgs/loot/people">team member</a>.</p>
+<p>Contributors can ask or be asked to join the LOOT team, which grants write access to the LOOT repositories and their issue trackers. Addition of new team members is done by the team admins, who base their decision on the quality of past contributions. If you would like to join the team, and feel comfortable with the workflow, contact a <a href="https://github.com/orgs/loot/people">team member</a>.</p>
 
 <h3 id="contributing-as-a-team-member">Contributing as a Team Member</h3>
 
diff --git a/docs/team/Team-Member-Responsibilities.html b/docs/team/Team-Member-Responsibilities.html
index caf5203..cba5ebc 100644
--- a/docs/team/Team-Member-Responsibilities.html
+++ b/docs/team/Team-Member-Responsibilities.html
@@ -26,7 +26,7 @@ title: Team Member Responsibilities
 <p>Team members who are admins on GitHub are responsible for adding new members. GitHub's excellent Forking feature allows people to contribute to repositories that they don't have write access to, and you should take full advantage of that:</p>
 
 <ul>
-  <li>If someone who hasn't contributed on GitHub asks for addition to the team, politely refer them to the <a href="/docs/contributing/How-To-Contribute.html">How To Contribute</a> wiki page, saying that they can contribute without being a team member.</li>
+  <li>If someone who hasn't contributed on GitHub asks for addition to the team, politely refer them to the <a href="/docs/contributing/How-To-Contribute.html">How To Contribute</a> page, saying that they can contribute without being a team member.</li>
   <li>If someone who has contributed on GitHub asks for addition to the team, take a look at their contributions (on their user page, in the "Repositories contributed to" list) and see if their contributions have been accepted or not to decide whether or not to grant them access. If their most recent pull requests have been rejected, it may be better to reply with a polite "not until we're happy with your contributions" message.</li>
 </ul>
 
diff --git a/docs/team/Thread-Management.html b/docs/team/Thread-Management.html
index cc5c8fd..48b920b 100644
--- a/docs/team/Thread-Management.html
+++ b/docs/team/Thread-Management.html
@@ -5,7 +5,7 @@ title: Thread Management
 
 <h3>Introduction</h3>
 
-<p>This wiki page is aimed at anyone who finds themselves in the position of being the only person active when a thread reaches its 200 post limit.</p>
+<p>This page is aimed at anyone who finds themselves in the position of being the only person active when a thread reaches its 200 post limit.</p>
 
 <p>When a thread nears 200 posts, a new thread should be opened with the title <code>[REL] LOOT - Thread #&lt;num&gt;</code>, where <code>&lt;num&gt;</code> is the number of the current thread + 1. The content of the opening post is given below.</p>
 
diff --git a/index.html b/index.html
index 7e7bb03..2ff15cb 100644
--- a/index.html
+++ b/index.html
@@ -11,4 +11,4 @@ title: The Load Order Optimisation Tool
     <button class="mdl-button mdl-js-button mdl-button--raised mdl-button--accent mdl-js-ripple-effect">Download LOOT</button>
 </a></p>
 
-<p>While we welcome user feedback, please check the <a href="/docs/help/LOOT-FAQs.html">FAQs</a> in case you have a question that has already been answered. If you wish to report an issue, please read the <a href="/docs/help/How-To-Report-Issues-Helpfully.html">How To Report Issues Helpfully</a> wiki page for instructions.</p>
+<p>While we welcome user feedback, please check the <a href="/docs/help/LOOT-FAQs.html">FAQs</a> in case you have a question that has already been answered. If you wish to report an issue, please read the <a href="/docs/help/How-To-Report-Issues-Helpfully.html">How To Report Issues Helpfully</a> page for instructions.</p>
diff --git a/masterlist.schema.yaml b/masterlist.schema.yaml
index 211b4d6..ded231f 100644
--- a/masterlist.schema.yaml
+++ b/masterlist.schema.yaml
@@ -12,7 +12,7 @@ type: map
 mapping:
   'common':
     # This is not strictly part of the spec., see:
-    # https://github.com/loot/loot.github.io/wiki/Masterlist-Editing#common-metadata
+    # https://loot.github.io/docs/contributing/Masterlist-Editing.html
     type: seq
     sequence:
       - type: any