Added notes above each additional terraform example

Author: dcpena

src/content/docs/terraform/additional-configurations/ddos-managed-rulesets.mdx

@@ -79,6 +79,8 @@ This example configures the [Network-layer DDoS Attack Protection](/ddos-protect
 
 :::
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_level_network_ddos_config" {
   account_id  = "<ACCOUNT_ID>"
@@ -128,6 +130,8 @@ The order of the rules is important: the rule with the highest sensitivity level
 
 :::
 
+<Render file="v4-code-snippets" />
+
 ```tf
 variable "zone_id" {
   default = "<ZONE_ID>"

src/content/docs/terraform/additional-configurations/rate-limiting-rules.mdx

@@ -73,6 +73,8 @@ resource "cloudflare_ruleset" "zone_rl" {
 
 This example defines a [custom ruleset](/ruleset-engine/custom-rulesets/) with a single rate limiting rule in account with ID `<ACCOUNT_ID>` that blocks traffic for the `/api/` path exceeding the configured rate. The second `cloudflare_ruleset` resource defines an `execute` rule that deploys the custom ruleset for traffic addressed at `example.com`.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_rl" {
   account_id  = <ACCOUNT_ID>
@@ -127,6 +129,8 @@ This example creates a rate limiting rule in zone with ID `<ZONE_ID>` with:
 - A custom counting expression that includes a response field (`http.response.code`).
 - A custom JSON response for rate limited requests.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "zone_rl_custom_response" {
   zone_id     = "<ZONE_ID>"

src/content/docs/terraform/additional-configurations/transform-rules.mdx

@@ -71,6 +71,8 @@ The following configuration example performs the following adjustments to HTTP r
 - Adds a `my-header-2` header to the request with a dynamic value defined by an expression.
 - Deletes the `existing-header` header from the request, if it exists.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "transform_modify_request_headers" {
   zone_id     = "<ZONE_ID>"
@@ -119,6 +121,8 @@ The following configuration example performs the following adjustments to HTTP r
 - Adds a `my-header-2` header to the response with a dynamic value defined by an expression.
 - Deletes the `existing-header` header from the response, if it exists.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "transform_modify_response_headers" {
   zone_id     = "<ZONE_ID>"

src/content/docs/terraform/additional-configurations/waf-custom-rules.mdx

@@ -69,6 +69,8 @@ For more information on enabling leaked credentials detection using Terraform, r
 
 This example adds a custom rule that challenges requests with leaked credentials by using one of the [leaked credentials fields](/waf/detections/leaked-credentials/#leaked-credentials-fields) in the rule expression.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "zone_custom_firewall_leaked_creds" {
   zone_id     = "<ZONE_ID>"
@@ -96,6 +98,8 @@ For more information on enabling malicious uploads detection using Terraform, re
 
 This example adds a custom rule that blocks requests with one or more <GlossaryTooltip term="content object">content objects</GlossaryTooltip> considered malicious by using one of the [content scanning fields](/waf/detections/malicious-uploads/#content-scanning-fields) in the rule expression.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "zone_custom_firewall_malicious_uploads" {
   zone_id     = "<ZONE_ID>"
@@ -127,6 +131,8 @@ You can only create and deploy custom rulesets at the account level.
 
 The following configuration creates the custom ruleset with a single rule:
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_firewall_custom_ruleset" {
   account_id  = "<ACCOUNT_ID>"
@@ -151,6 +157,8 @@ resource "cloudflare_ruleset" "account_firewall_custom_ruleset" {
 
 The following configuration deploys the custom ruleset at the account level. It defines a dependency on the `account_firewall_custom_ruleset` resource and uses the ID of the created custom ruleset in `action_parameters`:
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_firewall_custom_entrypoint" {
   account_id  = "<ACCOUNT_ID>"
@@ -183,6 +191,8 @@ The following configuration creates a custom ruleset with a single rule that [ch
 
 You can only add exposed credential checks to rules in a custom ruleset (that is, a ruleset with `kind = "custom"`).
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_firewall_custom_ruleset_exposed_creds" {
   account_id  = "<ACCOUNT_ID>"
@@ -215,6 +225,8 @@ resource "cloudflare_ruleset" "account_firewall_custom_ruleset_exposed_creds" {
 
 The following configuration deploys the custom ruleset. It defines a dependency on the `account_firewall_custom_ruleset_exposed_creds` resource and obtains the ID of the created custom ruleset:
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_firewall_custom_entrypoint" {
   account_id  = "<ACCOUNT_ID>"

src/content/docs/terraform/additional-configurations/waf-managed-rulesets.mdx

@@ -82,6 +82,8 @@ resource "cloudflare_ruleset" "zone_level_managed_waf" {
 
 The following example deploys two managed rulesets to the account with ID `<ACCOUNT_ID>` using Terraform, using a `cloudflare_ruleset` resource with two rules that execute the managed rulesets for two hostnames belonging to Enterprise zones.
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_ruleset" "account_level_managed_waf" {
   account_id  = "<ACCOUNT_ID>"
@@ -125,6 +127,8 @@ The following example adds two [skip rules](/waf/managed-rules/waf-exceptions/)
 
 Add the two skip rules to the `cloudflare_ruleset` resource before the rule that deploys the Cloudflare Managed Ruleset:
 
+<Render file="v4-code-snippets" />
+
 ```tf null {4-13,15-27}
 resource "cloudflare_ruleset" "zone_level_managed_waf" {
   # (...)
@@ -186,6 +190,8 @@ The following example adds three [overrides](/ruleset-engine/managed-rulesets/ov
 
 The following configuration includes the three overrides in the rule that executes the Cloudflare Managed Ruleset:
 
+<Render file="v4-code-snippets" />
+
 ```tf null {9-24}
   # (...)
 
@@ -225,6 +231,8 @@ This example enables [payload logging](/waf/managed-rules/payload-logging/) for
 
 Building upon the rule that deploys the Cloudflare Managed Ruleset, the following rule configuration adds the `matched_data` object with the public key used to encrypt the payload:
 
+<Render file="v4-code-snippets" />
+
 ```tf null {9-11}
   # (...)
 
@@ -264,6 +272,8 @@ The following example rule of a `cloudflare_ruleset` Terraform resource performs
 - Sets the score threshold to `60` (_Low_).
 - Sets the ruleset action to `log`.
 
+<Render file="v4-code-snippets" />
+
 ```tf null {8-25}
   # (...)
 

src/content/docs/terraform/advanced-topics/import-cloudflare-resources.mdx

@@ -73,6 +73,8 @@ cf-terraforming generate --email $CLOUDFLARE_EMAIL --token $CLOUDFLARE_API_TOKEN
 
 If you had not redirected the output to the `importing-example.tf` file, the result displayed in the standard output (your terminal window) would look like the following:
 
+<Render file="v4-code-snippets" />
+
 ```tf
 resource "cloudflare_record" "terraform_managed_resource_3c0b456bc2aa443089c5f40f45f51b31" {
     name    = "@"