diff --git a/website/source/docs/providers/fastly/d/ip_ranges.html.markdown b/website/source/docs/providers/fastly/d/ip_ranges.html.markdown
index ae1d83764..adc50a9f9 100644
--- a/website/source/docs/providers/fastly/d/ip_ranges.html.markdown
+++ b/website/source/docs/providers/fastly/d/ip_ranges.html.markdown
@@ -6,13 +6,13 @@ description: |-
   Get information on Fastly IP ranges.
 ---
 
-# fastly\_ip_ranges
+# fastly_ip_ranges
 
 Use this data source to get the [IP ranges][1] of Fastly edge nodes.
 
 ## Example Usage
 
-```
+```hcl
 data "fastly_ip_ranges" "fastly" {}
 
 resource "aws_security_group" "from_fastly" {
diff --git a/website/source/docs/providers/fastly/index.html.markdown b/website/source/docs/providers/fastly/index.html.markdown
index 75ff5eebe..e530dd3a5 100644
--- a/website/source/docs/providers/fastly/index.html.markdown
+++ b/website/source/docs/providers/fastly/index.html.markdown
@@ -18,7 +18,7 @@ Use the navigation to the left to read about the available resources.
 
 ## Example Usage
 
-```
+```hcl
 # Configure the Fastly Provider
 provider "fastly" {
   api_key = "test"
@@ -49,7 +49,7 @@ Fastly provider block:
 
 Usage:
 
-```
+```hcl
 provider "fastly" {
   api_key = "test"
 }
@@ -67,7 +67,7 @@ You can provide your API key via `FASTLY_API_KEY` environment variable,
 representing your Fastly API key. When using this method, you may omit the
 Fastly `provider` block entirely:
 
-```
+```hcl
 resource "fastly_service_v1" "myservice" {
   # ...
 }
diff --git a/website/source/docs/providers/fastly/r/service_v1.html.markdown b/website/source/docs/providers/fastly/r/service_v1.html.markdown
index 3429c86aa..e4c6b2619 100644
--- a/website/source/docs/providers/fastly/r/service_v1.html.markdown
+++ b/website/source/docs/providers/fastly/r/service_v1.html.markdown
@@ -6,7 +6,7 @@ description: |-
   Provides an Fastly Service
 ---
 
-# fastly\_service\_v1
+# fastly_service_v1
 
 Provides a Fastly Service, representing the configuration for a website, app,
 API, or anything else to be served through Fastly. A Service encompasses Domains
@@ -20,7 +20,7 @@ on their documentation site for guidance.
 
 Basic usage:
 
-```
+```hcl
 resource "fastly_service_v1" "demo" {
   name = "demofastly"
 
@@ -41,7 +41,7 @@ resource "fastly_service_v1" "demo" {
 
 Basic usage with an Amazon S3 Website and that removes the `x-amz-request-id` header:
 
-```
+```hcl
 resource "fastly_service_v1" "demo" {
   name = "demofastly"
 
@@ -89,7 +89,7 @@ Basic usage with [custom
 VCL](https://docs.fastly.com/guides/vcl/uploading-custom-vcl) (must be
 enabled on your Fastly account):
 
-```
+```hcl
 resource "fastly_service_v1" "demo" {
   name = "demofastly"
 
@@ -322,7 +322,7 @@ The `sumologic` block supports:
 * `name` - (Required) A unique name to identify this Sumologic endpoint.
 * `url` - (Required) The URL to Sumologic collector endpoint
 * `format` - (Optional) Apache-style string or VCL variables to use for log formatting. Defaults to Apache Common Log format (`%h %l %u %t %r %>s`)
-* `format_version` - (Optional) The version of the custom logging format used for the configured endpoint. Can be either 1 (the default, version 1 log format) or 2 (the version 2 log format). 
+* `format_version` - (Optional) The version of the custom logging format used for the configured endpoint. Can be either 1 (the default, version 1 log format) or 2 (the version 2 log format).
 * `response_condition` - (Optional) Name of already defined `condition` to apply. This `condition` must be of type `RESPONSE`. For detailed information about Conditionals, see [Fastly's Documentation on Conditionals][fastly-conditionals].
 * `message_type` - (Optional) How the message should be formatted. One of: classic, loggly, logplex, blank. See [Fastly's Documentation on Sumologic][fastly-sumologic]