diff --git a/Micro–DC/training.toon b/Micro–DC/training.toon
index e5a5cbf..17682c4 100644
--- a/Micro–DC/training.toon
+++ b/Micro–DC/training.toon
@@ -50,7 +50,7 @@ scenario_prompt:
       description: >
         A structured narrative (like a guided lab + playbook) that walks a
         team from powered-off hardware to a running, GitOps-managed platform
-        in **7–10 stages**, mapping to the deployment_runbook phases. Each
+        in **7-10 stages**, mapping to the deployment_runbook phases. Each
         stage should include learning objectives, inputs, concrete actions
         (as Git commits / pipeline runs), and observable outcomes.
     - id: "D2"
@@ -68,14 +68,14 @@ scenario_prompt:
     - id: "D4"
       name: "Sovereignty & Compliance Labs"
       description: >
-        2–3 hands-on micro-labs embedded in the scenario focusing on data
+        2-3 hands-on micro-labs embedded in the scenario focusing on data
         residency, classification, and admin-access controls (e.g. fixing a
         non-compliant backup policy, tightening access to critical sovereign
         namespaces).
     - id: "D5"
       name: "Observability & SLO Labs"
       description: >
-        1–2 exercises where trainees define SLOs (e.g. control-plane
+        1-2 exercises where trainees define SLOs (e.g. control-plane
         availability, GPU job wait time), wire telemetry into dashboards,
         and respond to a simulated incident or drift event.
     - id: "D6"
@@ -90,7 +90,7 @@ scenario_prompt:
       required_elements:
         - "Short story of the first site going live (choose one: EU-PAR-FR01 or EU-FRA-DE01)."
         - "Constraints: regulatory regime, scale assumptions, target use cases."
-        - "Key learning outcomes for the training cohort (3–7 bullets)."
+        - "Key learning outcomes for the training cohort (3-7 bullets)."
     stages:
       mapping_to_runbook_phases:
         - from_phase: 0
@@ -125,7 +125,7 @@ scenario_prompt:
     - "Bakes in sovereignty, GDPR, and sustainability rather than treating them as afterthoughts."
     - "Provides at least 3 concrete examples of policies preventing bad changes."
     - "Provides at least 2 concrete examples of SLOs and corresponding telemetry signals."
-    - "Addresses limitations and risks (LR1–LR4) with explicit training hooks."
+    - "Addresses limitations and risks (LR1-LR4) with explicit training hooks."
 
 reference_blueprint_template:
   description: >