Update references to --create-check

Clarify what we produce after using it
Ensure Traces configuration is explained by default and with overrides with TestCommand
Address Stefan's feedback

Author: MariadeAnton

site/content/docs/cli/command-line-reference.md

@@ -93,14 +93,18 @@ Exclude tests by pattern:
 npx checkly pw-test -- --grep-invert="skip|todo"
 ```
 
-### Creating monitors
+### Creating scheduled checks
+
+Using `pw-test` with the `--create-check` flag will add the check with a default configuration, so that you can tweak the monitoring configuration for your check. If there's no `checkly.config.ts` file it will create it.
+
+Regression tagged tests in multiple locations:
 
-Regression tests in multiple locations:
 ```bash
 npx checkly pw-test --create-check --location=us-east-1 --location=eu-west-1 --frequency=5m -- --grep="@regression"
 ```
 
-Mobile tests every 10 minutes:
+Mobile tests tagged critical every 10 minutes:
+
 ```bash
 npx checkly pw-test --create-check --frequency=10m -- --project="Mobile Chrome" --grep="@critical"
 ```
@@ -117,7 +121,7 @@ npx checkly pw-test --create-check --frequency=10m -- --project="Mobile Chrome"
 - `--test-session-name`: Name your test session
 - `--env`: Pass environment variables
 - `--env-file`: Load variables from file
-- All other `checkly test` flags except `--record`
+- All other [`checkly test` flags](https://www.checklyhq.com/docs/cli/command-line-reference/#npx-checkly-test) except `--record`
 
 ### Playwright flags (after `--`)
 - `--project`: Select Playwright projects

site/content/docs/playwright-checks/_index.md

@@ -48,12 +48,13 @@ What you need:
 
 
 
-### 3. Use `pw-test` for quick testing
+### 3. Use `pw-test` to test in Checkly
 
-Let's start with confirming your tests will work on Checkly, run the ones you want using `pw-test`.
+Run your Playwright test suite using `pw-test`.
 
-`pw-test` accepts both Checkly and Playwright command line arguments using the following syntax: 
-`npx checkly pwtest --checky-flag -- --playwright-flag`. Use `--` to seperate Checkly and Playwright flags. 
+`pw-test` accepts both Checkly and Playwright command line arguments using the following syntax:
+
+`npx checkly pwtest --checky-flag -- --playwright-flag`. Use `--` to seperate Checkly and Playwright flags.
 
 The CLI command will then return a link leading to results, traces and more details:
 
@@ -77,7 +78,7 @@ Detailed session summary at: https://chkly.link/l/linkhere
 
 ### 4. Convert tests to checks with `pw-test`:
 
-Using `pw-test` with the `--create-check` flag will create a `checkly.config.ts` file if it doesn't exist, and add the new check, so that you can tweak the monitoring configuration for your check.
+Using `pw-test` with the `--create-check` flag will create a `checkly.config.ts` file will add the new check and create the Checkly configuration file if it doesn't exist. Afterwards, you can tweak the monitoring configuration for your check.
 
 For example:
 
@@ -90,7 +91,7 @@ For example:
 Creating Checkly check from Playwright test... ✅
 ```
 
-Review the resulting check configuration in your `checkly.config.ts` file and make sure to tweak locations and schedule as needed. 
+Review the resulting check configuration in your `checkly.config.ts` file and make sure to tweak locations and schedule as needed.
 
 ```typescript {title="checkly.config.ts"}
 import { defineConfig } from 'checkly'

site/content/guides/using-pw-test-command.md

@@ -49,7 +49,10 @@ By default, `pw-test` uses N.Virginia (`us-east-1`) to run. Use any [global loca
 
 ### Create monitors
 
-Add `--create-check` to convert suites of tests into scheduled Playwright check suites:
+Using `pw-test` with the `--create-check` flag will create a `checkly.config.ts` file if it doesn't exist, and add the new check, so that you can tweak the monitoring configuration for your check.
+
+Each `--create-check` call will append the check configuration to your configuration file. If you run it twice with the same configuration, it'll create the same check twice.
+
 
 ```bash
 # Run all tests in the "chromium" project every 10 minutes
@@ -64,7 +67,7 @@ npx checkly pw-test --create-check --frequency=15m -- --project="Mobile Chrome"
 
 ## Advanced examples
 
-### Browser and device selection
+### Projects running browsers and emulating devices
 
 ```bash
 # Desktop browsers
@@ -91,7 +94,7 @@ npx checkly pw-test --create-check --frequency=10m -- --grep="@critical"
 
 ### Artifacts
 
-Configure in your `playwright.config.ts`:
+Configure which artifacts are stored in your `playwright.config.ts`:
 
 ```javascript
 use: {
@@ -101,7 +104,38 @@ use: {
 }
 ```
 
-View all artifacts in Checkly's UI after test runs.
+If you'd like different configuration for your checks, make sure to use the `--trace <mode>	` flag in the `testCommand` section of your Playwright Check Suite.
+
+```typescript {title="checkly.config.ts"}
+import { defineConfig } from 'checkly'
+
+const config = defineConfig({
+  logicalId: 'my-repo-name',
+  projectName: 'my-repo-name',
+  checks: {
+    playwrightConfigPath: './playwright.config.ts',
+    playwrightChecks: [
+      {
+        logicalId: 'myrepo', // tweak ID 
+        name: 'myrepo: Chromium Playwright Tests', // tweak name
+        testCommand: 'npx playwright test --project=chromium --trace=on',//
+        locations: [
+          'eu-central-1', 'us-east-1' // add or change locations
+        ],
+        frequency: 10, // a custom per-check frequency
+      },
+    ],
+  },
+  cli: {
+    runLocation: 'us-east-1', // where test and pw-test will run
+  },
+})
+
+export default config
+
+```
+
+View all artifacts in Checkly's UI after test runs in [Test Sessions](https://app.checklyhq.com/test-sessions).
 
 ### Environment variables
 
@@ -113,9 +147,8 @@ npx checkly pw-test --env ENVIRONMENT_URL="https://staging.acme.com" -- --grep="
 npx checkly pw-test --env-file=".env.staging" -- --project=chromium
 ```
 
-## Common patterns
+## Common patterns creating checks
 
-### E-commerce monitoring
 ```bash
 # Checkout flow
 npx checkly pw-test --create-check --frequency=15m --location=us-east-1 -- --project="Desktop Chrome" --grep="checkout"
@@ -149,6 +182,7 @@ npx checkly pw-test --test-session-name="Pre-deployment check" -- --project=chro
 
 **Missing artifacts**
 - Confirm they're set as `on` in `playwright.config.ts`
+- Alternatively, edit your `testCommand` to set the flag `trace=on`
 
 **"Project not found" errors**
 - Match exact names from `playwright.config.ts`