docs(angular): 📝 add reference to tdd

Author: yjaaidi

apps/cookbook/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) _(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)_.
+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](../../02-glossary.md#tdd) _(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?
 

apps/cookbook/docs/angular/02-glossary.md

@@ -123,7 +123,7 @@ Tests should not change their result if the structure of the code changes.
 
 Tests should be cheap to write relative to the cost of the code being tested.
 
-## Test-Driven Development _(TDD)_
+## Test-Driven Development _(TDD)_ {#tdd}
 
 Test-Driven Development _(TDD)_ is a software development process that relies on the repetition of a very short 3-phase development cycle: first, the developer writes an _(initially failing)_ test that defines a desired behavior, then produces the minimum amount of code that makes that test pass, and finally tidies up the new code to acceptable standards.