docs(angular): 📝 introduce acronym

marmicode · Dec 9, 2024 · 8367bbe · 8367bbe
1 parent 55e4a74
commit 8367bbe
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...ook/docs/angular/01-testing/02-designing-a-pragmatic-testing-strategy/index.mdx b/...ook/docs/angular/01-testing/02-designing-a-pragmatic-testing-strategy/index.mdx
@@ -219,7 +219,7 @@ Testing, and more precisely TDD, **keeps us focused on the task at hand, enablin
 
 ### The Wedding Registry Anecdote
 
-I had the privilege of being "born" into [eXtreme Programming](../../02-glossary.md#extreme-programming). My first job _(back in 2007)_ was with a team deeply committed to XP values and practices. As the least experienced developer on the team, Test-Driven Development _(TDD)_ saved me _(among other practices)_.
+I had the privilege of being "born" into [eXtreme Programming](../../02-glossary.md#extreme-programming) _(XP)_. My first job _(back in 2007)_ was with a team deeply committed to XP values and practices. As the least experienced developer on the team, Test-Driven Development _(TDD)_ saved me _(among other practices)_.
 
 Thirteen years later, having always relied on testing and TDD, **I had to challenge my well-established assumptions**. What if we didn't need as much testing? Could there be situations where testing wasn't necessary at all? We don't need tests for a one-shot simple script or some [Spikes](../../02-glossary.md#spike), but we need tests for ambitious products, right? But where is the line?