diff --git a/website-src/src/contributing.html b/website-src/src/contributing.html
index 3413d01..2ec5d00 100644
--- a/website-src/src/contributing.html
+++ b/website-src/src/contributing.html
@@ -3,32 +3,32 @@
 <title>AwesomePiracy</title>
 
 <xmp theme="united" style="display:none;">
-    # Contribution Guidelines
+   # Contribution Guidelines
 
-    Please note that this project is released with a
-    [Contributor Code of Conduct](https://github.com/Igglybuff/awesome-piracy/blob/master/code-of-conduct.md). By participating in this
-    project you agree to abide by its terms.
+   Please note that this project is released with a
+   [Contributor Code of Conduct](https://github.com/Igglybuff/awesome-piracy/blob/master/code-of-conduct.md). By participating in this
+   project you agree to abide by its terms.
 
-    ---
+   ---
 
-    Ensure your pull request adheres to the following guidelines:
+   Ensure your pull request adheres to the following guidelines:
 
-    - Include a description of the link you're adding if possible
-    - If you're changing section headers, ensure you update the contents at the top too
-    - If you're adding a new section, ensure you give it a unique name
+   - Include a description of the link you're adding if possible
+   - If you're changing section headers, ensure you update the contents at the top too
+   - If you're adding a new section, ensure you give it a unique name
 
-    Thank you for your suggestions!
+   Thank you for your suggestions!
 
 
-    ## Updating your PR
+   ## Updating your PR
 
-    A lot of times, making a PR adhere to the standards above can be difficult.
-    If the maintainers notice anything that we'd like changed, we'll ask you to
-    edit your PR before we merge it. There's no need to open a new PR, just edit
-    the existing one. If you're not sure how to do that,
-    [here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
-    on the different ways you can update your PR so that we can merge it.
+   A lot of times, making a PR adhere to the standards above can be difficult.
+   If the maintainers notice anything that we'd like changed, we'll ask you to
+   edit your PR before we merge it. There's no need to open a new PR, just edit
+   the existing one. If you're not sure how to do that,
+   [here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
+   on the different ways you can update your PR so that we can merge it.
 </xmp>
 
 <script src="https://strapdownjs.com/v/0.2/strapdown.js"></script>
-</html>
\ No newline at end of file
+</html>