fix finished exercise texts

Author: kettanaito

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

@@ -1,29 +1,30 @@
 # Test annotations
 
-Goal: Enhance test failures so you are one click away from learning more about the tested behavior. Put a link to the specification document your manager has written, or a GitHub/Linear/JIRA ticket if it's a test for regression. Help your future self and your teammates to navigate test failures easier.
+Good job! 👏
 
-- `tag` (let's group user-related tests);
-- `annotation.type` + `annotation.description` (let's provide metadata about the test case).
+Please wait for the others to finish so we could go through the solution to this exercise together.
+
+---
 
 Things you can do with tags:
 
 1. Run a subset of tests:
 
-````sh
+```sh
 npm run test:e2e -- --grep=@user
 npm run test:e2e -- --grep=@user|@profile
-``
+```
 
 2. You can also filter and run subset of tests from the UI mode (the "Filter" input at the top left).
-2. You can filter the test results in the test report (`show-report`) by tags.
+3. You can filter the test results in the test report (`show-report`) by tags.
 
 Things you can do with annotations:
 
 ```sh
 npx playwright show-report
 # And then click on the failing test.
 # Custom annotataions will list extra info to help you debug.
-````
+```
 
 ## Related materials
 

exercises/03.guides/03.problem.blocking-unneeded-requests/README.mdx

@@ -1,5 +1,9 @@
 # Blocking unneeded requests
 
+Our application now has [One Dollar Stats](https://onedollarstats.com/) for very simple analytics. That's useful in production but we don't need this analytics script running in our tests. It only creates unnecessary requests and takes time.
+
+Let's block this kind of requests in Playwright!
+
 ## Your task
 
 👨‍💼 In this one, your task is to block a certain HTTP request fired by the app. I'm talking about this analytics script:

exercises/03.guides/03.solution.blocking-unneeded-requests/README.mdx

@@ -1,19 +1,5 @@
 # Blocking unneeded requests
 
-Our application now has [One Dollar Stats](https://onedollarstats.com/) for very simple analytics. That's useful in production but we don't need this in our tests. It only creates unnecessary requests and takes time.
+Good job! 👏
 
-Let's block this kind of requests in Playwright!
-
-```ts
-// test-extend.ts
-test.beforeAll(({ network }) => {
-	network.use(
-		http.get('https://assets.onedollarstats.com/*', () => {
-			return Response.error()
-		}),
-	)
-})
-```
-
-- Belongs to the test setup, not fixtures? If a test doesn't use the custom `test()` function from `fixtures.ts`, it won't have those requests blocked.
-- Consider responding with an _empty response_. Responding with a network error will print an error to the browser console, creating noise. Mocking 3rd-party side-effect requests with empty responses should have no effect on the app (cause we want to exclude them, in the first place).
+Please wait for the others to finish so we could go through the solution to this exercise together.