From a80240463c8795d99bfc37c0a379cf0150425079 Mon Sep 17 00:00:00 2001
From: Anton Babenko <393243+antonbabenko@users.noreply.github.com>
Date: Wed, 3 Jun 2026 18:05:13 +0200
Subject: [PATCH] fix: use ASCII hyphens in Safe Destroy Protocol guidance
 (#45)

---
 skills/terraform-skill/references/state-management.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/skills/terraform-skill/references/state-management.md b/skills/terraform-skill/references/state-management.md
index 5704884..8dbe495 100644
--- a/skills/terraform-skill/references/state-management.md
+++ b/skills/terraform-skill/references/state-management.md
@@ -1797,9 +1797,9 @@ rm .terraform/terraform.tfstate.lock.info  # ❌ Dangerous
 
 A targeted destroy can cascade far beyond its targets via implicit dependencies. Always follow this sequence:
 
-1. Run `terraform plan -destroy [-target=...]` — never skip straight to destroy
+1. Run `terraform plan -destroy [-target=...]` - never skip straight to destroy
 2. Read **every** resource under "will be destroyed", not just the targeted ones
-3. ⚠️ Watch for `for_each` resources fed by a local that references a targeted resource — all instances become implicit dependents (e.g. targeting an `aws_eip` that is referenced in a `locals {}` block used by a `for_each` record resource will destroy **all** those records)
+3. ⚠️ Watch for `for_each` resources fed by a local that references a targeted resource - all instances become implicit dependents (e.g. targeting an `aws_eip` that is referenced in a `locals {}` block used by a `for_each` record resource will destroy **all** those records)
 4. Get explicit user confirmation of the full list before proceeding
 5. ❌ Never use `-auto-approve` on destroy in production
 
@@ -1815,7 +1815,7 @@ Common model mistakes to correct before returning state-related recommendations:
 - mixes prod and non-prod in the same backend key
 - recommends workspace-only isolation as a substitute for backend-level IAM separation
 - writes DynamoDB-lock configuration on Terraform 1.10+ instead of using `use_lockfile = true` on the S3 backend
-- runs `terraform destroy -auto-approve` or skips `plan -destroy` before a targeted destroy — missing implicit dependents pulled in via shared locals
+- runs `terraform destroy -auto-approve` or skips `plan -destroy` before a targeted destroy - missing implicit dependents pulled in via shared locals
 - reads via `terraform_remote_state` within a single team's stack instead of using module outputs (see [module-patterns.md](module-patterns.md#3-use-terraform_remote_state-sparingly--only-at-true-ownership-boundaries))
 - omits the rollback/recovery note for destructive state operations