diff --git a/website/source/docs/internals/internal-plugins.html.md b/website/source/docs/internals/internal-plugins.html.md
index bb99f8094..dc3c96428 100644
--- a/website/source/docs/internals/internal-plugins.html.md
+++ b/website/source/docs/internals/internal-plugins.html.md
@@ -10,7 +10,7 @@ description: |-
 
 Terraform providers and provisioners are provided via plugins. Each plugin provides an implementation for a specific service, such as AWS, or provisioner, such as bash. Plugins are executed as a separate process and communicate with the main Terraform binary over an RPC interface.
 
-# Upgrading From 0.7 and Earlier
+# Upgrading From Versions Earlier Than 0.7
 
 In versions of Terraform prior to 0.7, each plugin shipped as a separate binary. In versions of Terraform >= 0.7, all of the official plugins are shipped as a single binary. This saves a lot of disk space and makes downloads faster for you!
 
@@ -72,4 +72,4 @@ By using the network RPC interface, you can build and distribute a plugin for Te
 
 In theory, because the plugin interface is HTTP, you could even develop a plugin using a completely different programming language! (Disclaimer, you would also have to re-implement the plugin API which is not a trivial amount of work.)
 
-So to conclude, with the RPC interface _and_ internal plugins, we get the best of all of these features: Binaries that _Just Work_, savings from shared code, and extensibility through plugins. We hope you enjoy using these features in Terraform.
\ No newline at end of file
+So to conclude, with the RPC interface _and_ internal plugins, we get the best of all of these features: Binaries that _Just Work_, savings from shared code, and extensibility through plugins. We hope you enjoy using these features in Terraform.