Remove old messaging (#591)

docs/resources/service_acl_entries.md

@@ -10,8 +10,6 @@ description: |-
 
 Defines a set of Fastly ACL entries that can be used to populate a service ACL.  This resource will populate an ACL with the entries and will track their state.
 
-~> **Warning:** Terraform will take precedence over any changes you make in the UI or API. Such changes are likely to be reversed if you run Terraform again.
-
 ~> **Note:** By default the Terraform provider allows you to externally manage the entries via API or UI.
 If you wish to apply your changes in the HCL, then you should explicitly set the `manage_entries` attribute. An example of this configuration is provided below.
 

docs/resources/service_dictionary_items.md

@@ -3,16 +3,13 @@ layout: "fastly"
 page_title: "Fastly: service_dictionary_items"
 sidebar_current: "docs-fastly-resource-service-dictionary-items"
 description: |-
-  Provides a grouping of Fastly dictionary items that can be applied to a service. 
+  Provides a grouping of Fastly dictionary items that can be applied to a service.
 ---
 
 # fastly_service_dictionary_items
 
 Defines a map of Fastly dictionary items that can be used to populate a service dictionary.  This resource will populate a dictionary with the items and will track their state.
 
-
-~> **Warning:** Terraform will take precedence over any changes you make in the UI or API. Such changes are likely to be reversed if you run Terraform again.  
-
 ~> **Note:** By default the Terraform provider allows you to externally manage the items via API or UI.
 If you wish to apply your changes in the HCL, then you should explicitly set the `manage_items` attribute. An example of this configuration is provided below.
 
@@ -240,7 +237,7 @@ The resource ID is a combined value of the `service_id` and `dictionary_id` sepa
 $ terraform import fastly_service_dictionary_items.items xxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxx
 ```
 
-If Terraform is already managing remote dictionary items against a resource being imported then the user will be asked to remove it from the existing Terraform state.  
+If Terraform is already managing remote dictionary items against a resource being imported then the user will be asked to remove it from the existing Terraform state.
 The following is an example of the Terraform state command to remove the resource named `fastly_service_dictionary_items.items` from the Terraform state file.
 
 ```sh
@@ -259,4 +256,4 @@ $ terraform state rm fastly_service_dictionary_items.items
 
 - **id** (String) The ID of this resource.
 - **items** (Map of String) A map representing an entry in the dictionary, (key/value)
-- **manage_items** (Boolean) Whether to reapply changes if the state of the items drifts, i.e. if items are managed externally
+- **manage_items** (Boolean) Whether to reapply changes if the state of the items drifts, i.e. if items are managed externally

docs/resources/service_dynamic_snippet_content.md

@@ -8,9 +8,7 @@ description: |-
 
 # fastly_service_dynamic_snippet_content
 
-Defines content that represents blocks of VCL logic that is inserted into your service.  This resource will populate the content of a dynamic snippet and allow it to be manged without the creation of a new service verison. 
-
-~> **Warning:** Terraform will take precedence over any changes you make through the API. Such changes are likely to be reversed if you run Terraform again.  
+Defines content that represents blocks of VCL logic that is inserted into your service.  This resource will populate the content of a dynamic snippet and allow it to be manged without the creation of a new service verison.
 
 ~> **Note:** By default the Terraform provider allows you to externally manage the snippets via API or UI.
 If you wish to apply your changes in the HCL, then you should explicitly set the `manage_snippets` attribute. An example of this configuration is provided below.

templates/resources/service_acl_entries.md.tmpl

@@ -10,8 +10,6 @@ description: |-
 
 Defines a set of Fastly ACL entries that can be used to populate a service ACL.  This resource will populate an ACL with the entries and will track their state.
 
-~> **Warning:** Terraform will take precedence over any changes you make in the UI or API. Such changes are likely to be reversed if you run Terraform again.
-
 ~> **Note:** By default the Terraform provider allows you to externally manage the entries via API or UI.
 If you wish to apply your changes in the HCL, then you should explicitly set the `manage_entries` attribute. An example of this configuration is provided below.
 

templates/resources/service_dictionary_items.md.tmpl

@@ -3,16 +3,13 @@ layout: "fastly"
 page_title: "Fastly: service_dictionary_items"
 sidebar_current: "docs-fastly-resource-service-dictionary-items"
 description: |-
-  Provides a grouping of Fastly dictionary items that can be applied to a service. 
+  Provides a grouping of Fastly dictionary items that can be applied to a service.
 ---
 
 # fastly_service_dictionary_items
 
 Defines a map of Fastly dictionary items that can be used to populate a service dictionary.  This resource will populate a dictionary with the items and will track their state.
 
-
-~> **Warning:** Terraform will take precedence over any changes you make in the UI or API. Such changes are likely to be reversed if you run Terraform again.  
-
 ~> **Note:** By default the Terraform provider allows you to externally manage the items via API or UI.
 If you wish to apply your changes in the HCL, then you should explicitly set the `manage_items` attribute. An example of this configuration is provided below.
 
@@ -78,9 +75,9 @@ The resource ID is a combined value of the `service_id` and `dictionary_id` sepa
 
 {{ codefile "sh" "examples/resources/service_dictionary_items_import_with_id.txt" }}
 
-If Terraform is already managing remote dictionary items against a resource being imported then the user will be asked to remove it from the existing Terraform state.  
+If Terraform is already managing remote dictionary items against a resource being imported then the user will be asked to remove it from the existing Terraform state.
 The following is an example of the Terraform state command to remove the resource named `fastly_service_dictionary_items.items` from the Terraform state file.
 
 {{ codefile "sh" "examples/resources/service_dictionary_items_import_from_state.txt" }}
 
-{{ .SchemaMarkdown | trimspace }}
+{{ .SchemaMarkdown | trimspace }}

templates/resources/service_dynamic_snippet_content.md.tmpl

@@ -8,9 +8,7 @@ description: |-
 
 # fastly_service_dynamic_snippet_content
 
-Defines content that represents blocks of VCL logic that is inserted into your service.  This resource will populate the content of a dynamic snippet and allow it to be manged without the creation of a new service verison. 
-
-~> **Warning:** Terraform will take precedence over any changes you make through the API. Such changes are likely to be reversed if you run Terraform again.  
+Defines content that represents blocks of VCL logic that is inserted into your service.  This resource will populate the content of a dynamic snippet and allow it to be manged without the creation of a new service verison.
 
 ~> **Note:** By default the Terraform provider allows you to externally manage the snippets via API or UI.
 If you wish to apply your changes in the HCL, then you should explicitly set the `manage_snippets` attribute. An example of this configuration is provided below.