diff --git a/website/source/intro/examples/consul.html.markdown b/website/source/intro/examples/consul.html.markdown
index 0f00f1b251..56e7086037 100644
--- a/website/source/intro/examples/consul.html.markdown
+++ b/website/source/intro/examples/consul.html.markdown
@@ -51,7 +51,7 @@ infrastructure to be decoupled from its overall architecture. This enables
 details to be changed without updating the Terraform configuration.
 
 Outputs from Terraform can also be easily stored in Consul. One powerful
-features this enables is using Consul for inventory management. If an
+feature this enables is using Consul for inventory management. If an
 application relies on ELB for routing, Terraform can update the application's
 configuration directly by setting the ELB address into Consul. Any resource
 attribute can be stored in Consul, allowing an operator to capture anything
diff --git a/website/source/intro/getting-started/variables.html.md b/website/source/intro/getting-started/variables.html.md
index e0c3855097..e1f779c8bc 100644
--- a/website/source/intro/getting-started/variables.html.md
+++ b/website/source/intro/getting-started/variables.html.md
@@ -56,7 +56,7 @@ the AWS provider with the given variables.
 There are three ways to assign variables.
 
 First, if you execute `terraform plan` or apply without doing
-anythiing, Terraform will ask you to input the variables interactively.
+anything, Terraform will ask you to input the variables interactively.
 These variables are not saved, but provides a nice user experience for
 getting started with Terraform.