Fix typo

docs/faq.md

@@ -52,7 +52,7 @@ We strive for clear inline documentation across our codebase, but have gaps. Con
 
 If you are considering changing a core component (aka, one that is not in a plugin), you are entering the realm of a core developer. We strongly ask that you reach out the coral team before forking and changing core code. We are glad to help talk through your product need and come up with a strategy for implementing as a plugin, or working with you to extend the plugin API for your use case.
 
-### How do I contribue to these docs?
+### How do I contribute to these docs?
 
 Contributions to the docs are much appreciated and a great way to get involved in the project.
 

docs/install.md

@@ -19,4 +19,4 @@ While Talk can be installed in many ways, we support two install paths:
 * [Install from Source](install-source.html) (development)
 * [Install via Docker](install-docker.html) (deployment)
 
-If you have success installing Talk in another way, please consider [contributing to this documentation](faq.html#how-do-i-contribue-to-these-docs)!
+If you have success installing Talk in another way, please consider [contributing to this documentation](faq.html#how-do-i-contribute-to-these-docs)!

docs/plugins-quickstart.md

@@ -6,7 +6,7 @@ permalink: plugins-quickstart.html
 summary:
 ---
 
-This tutorial walks through the mechanics of creating and publishing a Talk plugin. Along the way I call out some particular habits and techniques that I employ. If you have other practices that you find valuable, please don't hesitate to [contribute!](faq.html#how-do-i-contribue-to-these-docs)
+This tutorial walks through the mechanics of creating and publishing a Talk plugin. Along the way I call out some particular habits and techniques that I employ. If you have other practices that you find valuable, please don't hesitate to [contribute!](faq.html#how-do-i-contribute-to-these-docs)
 
 We will create a plugin that exposes a route that allows assets to be created or updated.