Typo fixes plus some additional docs about authentication options.

third_party/terraform/website/docs/guides/getting_started.html.markdown

@@ -23,7 +23,10 @@ provider.
 First, authenticate with GCP.  The easiest way to do this is to run
 `gcloud auth application-default login`, if you already have gcloud
 installed.  If you don't already have it, gcloud can be installed with
-`apt-get install google-cloud-sdk` on Debian-based machines.
+`apt-get install google-cloud-sdk` on Debian-based machines.  For a
+production use-case, you will want to use service account authentication,
+which you can learn about further down in this doc, but for experimenting,
+gcloud authentication will work fine.
 
 Next, create a Terraform config file named `"main.tf"`. Inside, you'll
 want to include the following configuration:
@@ -173,6 +176,11 @@ You supply the key to Terraform using the environment variable
 export GOOGLE_APPLICATION_CREDENTIALS={{path}}
 ```
 
+If you choose to use `gcloud`-generated credentials, and you encounter
+quota or billing issues which don't seem to apply to you, you may want to set
+`user_project_override` to `true` in the provider block - see the
+[provider reference](/docs/providers/google/guides/provider_reference.html) for more information.
+
 -> Remember to add this line to a startup file such as `bash_profile` or
 `bashrc` to store your credentials across sessions!
 

third_party/terraform/website/docs/guides/provider_reference.html.markdown

@@ -76,7 +76,7 @@ same configuration.
 [service account key file] in JSON format. You can
 [manage key files using the Cloud Console].  If not provided, the
 application default credentials will be used.  You can configure
-use Application Default Credentials on your personal machine by
+Application Default Credentials on your personal machine by
 running `gcloud auth application-default login`. If
 terraform is running on a GCP machine, and this value is unset,
 it will automatically use that machine's configured service account.