diff --git a/website/source/intro/getting-started/dependencies.html.md b/website/source/intro/getting-started/dependencies.html.md
index 550546d29d26..fe3397afed83 100644
--- a/website/source/intro/getting-started/dependencies.html.md
+++ b/website/source/intro/getting-started/dependencies.html.md
@@ -112,7 +112,7 @@ to infer dependencies based on usage of attributes of other
 resources.
 
 Using this information, Terraform builds a graph of resources.
-This tells Terraform not only what order to create resources,
+This tells Terraform not only in what order to create resources,
 but also what resources can be created in parallel. In our example,
 since the IP address depended on the EC2 instance, they could
 not be created in parallel.
diff --git a/website/source/intro/getting-started/modules.html.md b/website/source/intro/getting-started/modules.html.md
index 138ab6098546..c11c73ef0d69 100644
--- a/website/source/intro/getting-started/modules.html.md
+++ b/website/source/intro/getting-started/modules.html.md
@@ -83,7 +83,9 @@ With the modules downloaded, we can now plan and apply it. If you run
 
 ```
 $ terraform plan
-TODO
+...
++ module.consul
+    4 resource(s)
 ```
 
 As you can see, the module is treated like a black box. In the plan, Terraform
@@ -97,7 +99,8 @@ will have some cost associated with it.
 
 ```
 $ terraform apply
-TODO
+...
+Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
 ```
 
 After a few minutes, you'll have a three server Consul cluster up and