diff --git a/website/source/docs/guides/index.html.md b/website/source/docs/guides/index.html.md
index b7f27660df..096aa58066 100644
--- a/website/source/docs/guides/index.html.md
+++ b/website/source/docs/guides/index.html.md
@@ -44,4 +44,4 @@ The following guides are available:
 
 * [Sentinel](/docs/guides/sentinel.html) - This guide covers using Sentinel for policy enforcement in Consul.
 
-* [Server Performance](/docs/guides/performance.html) - This guide covers minumum requirements for Consul servers as well as guidelines for running Consul servers in production.
+* [Server Performance](/docs/guides/performance.html) - This guide covers minimum requirements for Consul servers as well as guidelines for running Consul servers in production.
diff --git a/website/source/docs/upgrade-specific.html.md b/website/source/docs/upgrade-specific.html.md
index 35d70fc9da..64934088be 100644
--- a/website/source/docs/upgrade-specific.html.md
+++ b/website/source/docs/upgrade-specific.html.md
@@ -368,7 +368,7 @@ The details of the change are not important, however to function the leader
 node will replicate a new command to its followers. Consul is designed
 defensively, and when a command that is not recognized is received, the
 server will panic. This is a purposeful design decision to avoid the possibility
-of data loss, inconsistensies, or security issues caused by future incompatibility.
+of data loss, inconsistencies, or security issues caused by future incompatibility.
 
 In practice, this means if a Consul 0.5 node is the leader, all of its
 followers must also be running 0.5. There are a number of ways to do this