Fix feedback setup tutorial

Author: ostenbom

tutorial/stage-1-setup/practical-playwright-setup.mdx

@@ -34,8 +34,7 @@ Following the [Playwright documentation](https://playwright.dev/docs/intro#using
 pnpm create playwright
 ```
 
-Follow the wizard. You should now have a `playwright.config.ts` file, a `tests` directory, and also a `tests-examples` directory.
-You can remove the `tests-examples` directory, we won't be using it.
+Follow the wizard. You should now have a `playwright.config.ts` file and a `tests` directory.
 
 ### Modifying `playwright.config.ts` for our needs
 
@@ -76,6 +75,10 @@ Let's check that this works by modifying the `example.spec.ts` test file in the
 - Modify the expectation to check for our page title `/Playwright Tutorial/`
 - Watch your test run `pnpm playwright test --debug`
 
+<Aside type="caution">
+When you run Playwright in debug mode for the first time, the browser will open and appear frozen on `about:blank`. This is expected! You need to click the "step over" button in the Playwright Inspector window to start stepping through your test.
+</Aside>
+
 You can watch your test step by step by using the "step over" button.
 <Image src={StepOverDebug} alt="Step over button in Playwrights inspector" width={600} />
 
@@ -105,9 +108,18 @@ Today we will learn to use both kinds of set up approaches.
 
 First let's make the test files for setup and teardown:
 
+<Tabs>
+<TabItem label="Linux/macOS">
 ```bash
-touch tests/setup.spec.ts && touch tests/teardown.spec.ts
+touch tests/setup.spec.ts tests/teardown.spec.ts
 ```
+</TabItem>
+<TabItem label="Windows (PowerShell)">
+```powershell
+New-Item -ItemType File -Path tests/setup.spec.ts, tests/teardown.spec.ts
+```
+</TabItem>
+</Tabs>
 
 For us to use project dependencies to declare our setup and teardown steps, we need to make more modifications to our `playwright.config.ts` file.
 
@@ -287,9 +299,13 @@ Let's explore the alternative to creating users through the browser, which is to
 Let's make ourselves an internal API endpoint for our tests to use.
 
 ```bash
-git checkout stage-1-setup -- app/api/internal/user/route.ts
+git checkout origin/stage-1-setup -- app/api/internal/user/route.ts
 ```
 
+<Aside type="note">
+This step is only necessary if you're running tests against a local Next.js dev application. If you're testing against the remote Vercel deployment, this API endpoint is already available and you can skip this checkout command.
+</Aside>
+
 This file contains a `POST` and `DELETE` endpoint for creating and deleting users.
 
 ```ts
@@ -329,9 +345,18 @@ export default defineConfig({
 
 Then we need to create the `global-setup.ts` and `global-teardown.ts` files.
 
+<Tabs>
+<TabItem label="Linux/macOS">
 ```bash
 touch global-setup.ts global-teardown.ts
 ```
+</TabItem>
+<TabItem label="Windows (PowerShell)">
+```powershell
+New-Item -ItemType File -Path global-setup.ts, global-teardown.ts
+```
+</TabItem>
+</Tabs>
 
 Can you figure out what these scripts should contain?