diff --git a/doc/qa/test-guidelines.md b/doc/qa/test-guidelines.md
index 47afc27de..c5b142452 100644
--- a/doc/qa/test-guidelines.md
+++ b/doc/qa/test-guidelines.md
@@ -11,7 +11,7 @@ This document describes recommended testing strategies for the Elsa engine. It i
 2. **Fast feedback** — unit and integration tests should run quickly to support local development workflows and CI.
 3. **Minimal reliance on real delays** — avoid `Task.Delay`, `Thread.Sleep` or real clocks except where unavoidable; prefer event-driven assertions.
 4. **Environment portability** — tests should run in local dev, Docker or any other container CI environment with minimal changes.
-5. **Version alignment** — workflow definition versions and test artifacts must be explicitly linked so tests refer to a specific workflow blueprint version.
+5. **Version alignment** — workflow definition versions and test artifacts must be explicitly linked so tests refer to a specific workflow definition version.
 6. **Bulk provisioning & isolation** — tests should support bulk import of workflow definitions for large-suite runs and ensure clean, isolated state per test.
 7. **Clear assertion points** — provide a consistent and resilient set of places to assert behavior (journal, activity execution endpoints, DB queries, events) and guidelines for choosing between them.
 8. **Failure simulation** — deterministic ways to simulate activity or host failures and assert correct recovery/compensation.