docs: 📝 tidy up

Author: yjaaidi

docs/instructions/101-meal-planner.md

@@ -56,7 +56,7 @@ pnpm test
 
 #### 4. Implement tests.
 
-#### 5. Checkout the implementation if you didn't do it already.
+#### 5. [optional] Checkout the implementation if you've opted for TDD option:
 
 ```sh
 pnpm cook checkout-impl

docs/instructions/102-meal-planner-reactive.md

@@ -73,7 +73,7 @@ pnpm test
 
 #### 3. Implement tests.
 
-#### 3. Checkout the implementation if you didn't do it already.
+#### 3. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl

docs/instructions/201-meal-planner-indirect-output.md

@@ -42,7 +42,7 @@ pnpm test
 
 #### 4. Check that the fake repo contains the added recipe.
 
-#### 5. Checkout the implementation if you didn't do it already.
+#### 5. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl
@@ -62,7 +62,7 @@ pnpm test
 
 #### 4. Check that the spies were called properly.
 
-#### 5. Checkout the implementation if you didn't do it already.
+#### 5. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl

docs/instructions/202-meal-planner-indirect-input.md

@@ -53,7 +53,7 @@ pnpm test
 
 #### 5. Check that the spy was called properly.
 
-#### 6. Checkout the implementation if you didn't do it already.
+#### 6. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl

docs/instructions/303-recipe-search-shallow.md

@@ -54,7 +54,7 @@ TestBed.overrideComponent(RecipeSearch, {
 
 #### 4. Query DOM and check child components properties. (Cf. [query DOM with `fixture.debugElement`](302-recipe-search-integration.md#-tip-query-dom-with-fixturedebugelement)] & [access element properties](#-tip-access-element-properties))
 
-#### 5. Checkout the implementation if you didn't do it already.
+#### 5. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl

docs/instructions/401-recipe-filter.md

@@ -41,7 +41,7 @@ pnpm test
 
 3.  Check that `filterChange` have been triggered.
 
-#### 3. Checkout the implementation if you didn't do it already.
+#### 3. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl

docs/instructions/402-recipe-filter-interaction.md

@@ -41,18 +41,19 @@ pnpm test
 
 #### 5. Query DOM and check child recipe preview components properties. (Cf. [query DOM with `fixture.debugElement`](./302-recipe-search-integration.md#-tip-query-dom-with-fixturedebugelement)] & [access element properties](./303-recipe-search-shallow.md#-tip-access-element-properties))
 
-#### 6. Checkout the implementation if you didn't do it already.
+#### 6. [optional] Checkout the implementation if you've opted for TDD option:.
 
 ```sh
 pnpm cook checkout-impl
 ```
 
 ## 📖 Appendices
 
-### 🎁 Tip: Trigger events using `DebugElement.triggerEventHandler`
+### 🎁 Tip: Trigger events using `DebugElement#triggerEventHandler`
 
-You can trigger both native and custom events using `DebugElement.triggerEventHandler`.
+You can trigger a custom event as an output using `DebugElement#triggerEventHandler` if a component was "shallowed".
 
 ```ts
-fixture.query(...).triggerEventHandler('myEventName', myEvent);
+const debugElement = fixture.query(...);
+debugElement.triggerEventHandler('myOutput', myValue);
 ```

docs/instructions/faq.md

@@ -16,7 +16,7 @@ TestBed.overrideComponent(MyThing, {
 
 ## Not getting the expected result
 
-- [ ] Did you wait for change detection to be triggered and the component to be stable `fixture.whenStable()`?
+- [ ] Did you wait for change detection to be triggered and the component to be stable `fixture.whenStable()`? or did you use a retry-able assertion such as `await expect.element(...)...` or `await expect.poll(() => ...)`?
 - [ ] Did you `await` all functions that return a promise? (e.g. harnesses)
 
 ## How to stub a function that returns an observable?