Small updates

Author: pedrosousa

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

@@ -95,7 +95,6 @@ For more information on configuring custom detection locations, refer to the [Te
 The following example creates a [custom ruleset](/ruleset-engine/custom-rulesets/) in the account with ID `<ACCOUNT_ID>` containing a single custom rule. This custom ruleset is then deployed using a separate `cloudflare_ruleset` Terraform resource. If you do not deploy a custom ruleset, it will not execute.
 
 :::caution
-
 You can only create and deploy custom rulesets at the account level.
 :::
 
@@ -153,9 +152,7 @@ For more information on configuring and deploying custom rulesets, refer to [Wor
 
 <Render file="leaked-credentials-recommend-detection" product="waf" />
 
-The following configuration creates a custom ruleset with a single rule that
-[checks for exposed
-credentials](/waf/managed-rules/check-for-exposed-credentials/configure-api/#create-a-custom-rule-checking-for-exposed-credentials).
+The following configuration creates a custom ruleset with a single rule that [checks for exposed credentials](/waf/managed-rules/check-for-exposed-credentials/configure-api/#create-a-custom-rule-checking-for-exposed-credentials).
 
 You can only add exposed credential checks to rules in a custom ruleset (that is, a ruleset with `kind = "custom"`).
 

src/content/partials/waf/leaked-credentials-detection-enable-terraform.mdx

@@ -4,9 +4,9 @@
 
 ```terraform
 resource "cloudflare_leaked_credential_check" "zone_lcc_example" {
-    zone_id = "<ZONE_ID>"
-    enabled = true
+	zone_id = "<ZONE_ID>"
+	enabled = true
 }
 ```
 
-For more information, refer to the [Terraform Cloudflare provider](https://registry.terraform.io/providers/cloudflare/cloudflare/4.48.0/docs/resources/leaked_credential_check) documentation.
+For more information, refer to the [Terraform Cloudflare provider documentation](https://registry.terraform.io/providers/cloudflare/cloudflare/4.48.0/docs/resources/leaked_credential_check).