diff --git a/website/source/intro/index.html.markdown b/website/source/intro/index.html.markdown
index 7e4e0b260d..6793944a70 100644
--- a/website/source/intro/index.html.markdown
+++ b/website/source/intro/index.html.markdown
@@ -30,7 +30,7 @@ and coordinating infrastructure. It provides several key features:
* **Key/Value Store**: Applications can make use of Consul's hierarchical key/value
store for any number of purposes including dynamic configuration, feature flagging,
- coordination, leader election, etc. The simple HTTP API makes dead easy to use.
+ coordination, leader election, etc. The simple HTTP API makes it easy to use.
* **Multi Datacenter**: Consul supports multiple datacenters out of the box. This
means users of Consul do not have to worry about building additional layers of
diff --git a/website/source/intro/vs/serf.html.markdown b/website/source/intro/vs/serf.html.markdown
index 52aa566979..1b179bded5 100644
--- a/website/source/intro/vs/serf.html.markdown
+++ b/website/source/intro/vs/serf.html.markdown
@@ -37,9 +37,9 @@ of [multiple gossip pools](/docs/internals/architecture.html), so that
the performance of Serf over a LAN can be retained while still using it over
a WAN for linking together multiple datacenters.
-Consul is also more opinionated in its usage than Serf, enabling Serf
-to be used in a wider variety of cases. Consul also uses a CP architecture,
-favoring consistency over availability. Serf is a AP system, and sacrifices consistency
-for availability. This means Consul cannot operate if the central servers cannot
-form a quorum, while Serf will continue to function under almost all circumstances.
+Consul is opinionated in its usage, while Serf is a more flexible and
+general purpose tool. Consul uses a CP architecture, favoring consistency over
+availability. Serf is a AP system, and sacrifices consistency for availability.
+This means Consul cannot operate if the central servers cannot form a quorum,
+while Serf will continue to function under almost all circumstances.