use related materials heading

Author: kettanaito

exercises/02.test-setup/01.solution.custom-fixtures/README.mdx

@@ -1 +1,7 @@
 # Custom fixtures
+
+Please wait for the others to finish so we could go through the solution to this exercise together!
+
+## Related materials
+
+- [Fixtures in Playwright](https://playwright.dev/docs/test-fixtures)

exercises/02.test-setup/04.solution.api-mocking/README.mdx

@@ -4,7 +4,7 @@
 1. Create `test-extend.ts` and a `network` fixture there.
 1. Note: `createWorkerFixture()` _automatically_ comes with `auto: true`.
 
-## Materials
+## Related materials
 
 - [`@msw/playwright`](https://github.com/mswjs/playwright)
 - [Mock Service Worker](https://mswjs.io)

exercises/03.guides/01.solution.recording-interactions/README.mdx

@@ -15,6 +15,6 @@ Then, say we've made a mistake while recording our interactions. Not to worry:
 1. Correct the mistake.
 1. Close the window.
 
-## Materials
+## Related materials
 
 - [Playwright Test Generator](https://playwright.dev/docs/codegen)

exercises/03.guides/02.solution.test-annotations/README.mdx

@@ -5,6 +5,6 @@ Goal: Enhance test failures so you are one click away from learning more about t
 - `tag` (let's group user-related tests);
 - `annotation.type` + `annotation.description` (let's provide metadata about the test case).
 
-## Materials
+## Related materials
 
 - [Test annotations](https://playwright.dev/docs/test-annotations)

exercises/04.debugging/03.solution.live-debugging/README.mdx

@@ -3,6 +3,6 @@
 - Use the [Playwright extension for Visual Studio Code](https://playwright.dev/docs/getting-started-vscode) to debug a failing test by opening its browser _inline_, right in the editor.
 - Use breakpoints to stop the code execution and step through the test/code.
 
-## Materials
+## Related materials
 
 - [Debugging tests](https://playwright.dev/docs/debug)