diff --git a/docs/contributing/contributing.md b/docs/contributing/contributing.md
index 252d9ffe..3c2d9636 100644
--- a/docs/contributing/contributing.md
+++ b/docs/contributing/contributing.md
@@ -6,7 +6,7 @@ Any contribution you make is useful! Even small things like fixing typos make a
 
 ## Code of Conduct
 
-Vapor has adopted Swift's Code of Conduct which can be found at https://www.swift.org/code-of-conduct/. All contributors are expected to follow the code of conduct.
+Vapor has adopted Swift's Code of Conduct which can be found at [https://www.swift.org/code-of-conduct/](https://www.swift.org/code-of-conduct/). All contributors are expected to follow the code of conduct.
 
 ## What to work on
 
@@ -54,4 +54,4 @@ When submitting a pull request there are number of things you should check:
 * New tests added for any new behavior or bugs fixed
 * New public APIs are documented. We use DocC for our API documentation.
 
-Vapor uses automation to reduce the amount of work needed for many tasks. For pull requests, we use the [Vapor Bot](https://github.com/VaporBot) to generate releases when a pull request is merged. The pull request body and title are used to generate the release notes, so make sure that they make sense and cover what you'd expect to see in release notes. We have more details on [Vapor's contributing guidelines](https://github.com/vapor/vapor/blob/main/.github/contributing.md#release-title).
\ No newline at end of file
+Vapor uses automation to reduce the amount of work needed for many tasks. For pull requests, we use the [Vapor Bot](https://github.com/VaporBot) to generate releases when a pull request is merged. The pull request body and title are used to generate the release notes, so make sure that they make sense and cover what you'd expect to see in release notes. We have more details on [Vapor's contributing guidelines](https://github.com/vapor/vapor/blob/main/.github/contributing.md#release-title).