Clean up beta notes and add link

detect/synthetic-monitoring/browser-checks/playwright-support.mdx

@@ -158,18 +158,16 @@ To see one way this can look like, see our [example repository](https://github.c
 
 ## Global configuration
 
-We are gradually rolling out support for global configuration options for the Playwright Test Runner. This allows you to 
+We are gradually rolling out support for global configuration options for the Playwright Test Runner. This allows you to
 configure your Playwright tests in a single place, instead of having to repeat the same configuration for each test file.
 
-<Warning> This feature is in **beta** and is only available when using the Checkly CLI to manage your checks and associated `.spec.ts|js` files.</Warning>
-
 There are three things you should be aware of:
 1. You can only use a subset of the Playwright config options. See the [supported configuration options](#supported-configuration-options) section for more information.
 2. You need to add the `playwrightConfig` section to your `checkly.config.ts` file, nested under the `browserChecks` section.
 3. We explicitly do not read from the existing `playwright.config.ts` or `playwright.config.js` file in your project. This is to avoid any confusion about which config file is used to run your tests and to prevent any unexpected behaviour.
 
 
-If you have an existing `playwright.config.ts` or `playwright.config.js` file in your project that you want to import, 
+If you have an existing `playwright.config.ts` or `playwright.config.js` file in your project that you want to import,
 you can simply run the [sync-playwright](/cli/checkly-sync-playwright)
 
 ```bash
@@ -389,7 +387,7 @@ await expect(page).toHaveScreenshot('homepage.png')
 test('Mobile checkout workflow', async ({ page }) => {
   // Simulate iPhone 12
   await page.setViewportSize({ width: 390, height: 844 })
-  
+
   // Test mobile-specific interactions
   await page.goto('https://shop.example.com')
   await page.click('[data-testid="mobile-menu-toggle"]')
@@ -417,7 +415,7 @@ test('Setup authentication', async ({ page }) => {
   await page.fill('[name="email"]', process.env.TEST_EMAIL)
   await page.fill('[name="password"]', process.env.TEST_PASSWORD)
   await page.click('[type="submit"]')
-  
+
   // Save authentication state
   await page.context().storageState({ path: 'auth-state.json' })
 })
@@ -429,4 +427,4 @@ test('Authenticated user workflow', async ({ page }) => {
   await page.goto('https://app.example.com/dashboard')
   await expect(page.locator('.welcome-message')).toBeVisible()
 })
-```
+```

detect/synthetic-monitoring/browser-checks/snippets.mdx

@@ -11,10 +11,9 @@ Snippets can be useful for:
 - a common navigation flow
 - a common setup or teardown procedure
 
-
-> [!CLI]
-> If you are using the CLI, you don't need to use snippets. You can just use `import` or `require` to add any local dependencies from your repo.
-> Check the docs on using local dependencies [right here](/cli/npm-packages/).
+<Note>
+If you are using [the Checkly CLI](/cli/overview), you don't need to use snippets. Use `import` or `require` to add any local dependencies from your repo. Check the docs on [using local dependencies](/platform/runtimes/dependencies#local-dependencies) to learn more.
+</Note>
 
 ## How to use snippets
 

detect/synthetic-monitoring/playwright-checks/overview.mdx

@@ -52,10 +52,6 @@ Receive notifications when tests fail or performance degrades, keeping your team
 </Step>
 </Steps>
 
-<Info>
-**Runtime Limits**: During Beta, Playwright Checks can run up to 20 minutes per execution. This limit can be adjusted based on feedback.
-</Info>
-
 ## Test Selection
 
 Your Playwright end-to-end test suite consists of projects, `spec.ts` files and individual tests. Use Playwright Check Suites to select and regroup the tests you want to run as synthetic monitors.

detect/synthetic-monitoring/playwright-checks/test-organization.mdx

@@ -35,7 +35,7 @@ Playwright tests are run to validate a pre-production environment and prepare a
 
 Split your Playwright tests into focus areas or groups of urgency to ensure the best monitoring frequency and alerting mechanisms.
 
-The acceptable test duration depends on your application and how quickly you want to be alerted in case of an issue. **If your service level agreements (SLAs) require a fast reaction time, we recommend keeping your Playwright Check Suite execution times as short as possible**.
+The acceptable test duration depends on your application and how quickly you want to be alerted in case of an issue. **If [your service level agreements (SLAs)](/learn/incidents/slo-sla-sli) require a fast reaction time, we recommend keeping your Playwright Check Suite execution times as short as possible**.
 
 <Tip>
 Remember: 99.9% uptime means about 1 minute and 26 seconds of downtime each day. To ensure high uptime, your Playwright Check Suites should run much faster than the maximum downtime per day. To guarantee a high level of uptime, your Playwright Check Suites should run significantly faster than 1 minute and 26 seconds.

docs.json

@@ -303,7 +303,6 @@
                       "resolve/traces/import/overview",
                       "resolve/traces/import/open-telemetry",
                       "resolve/traces/import/missing-spans",
-
                       "resolve/traces/import/https-grpc"
                     ]
                   },

resolve/traces/import/open-telemetry.mdx

@@ -1,4 +1,4 @@
---- 
+---
 title: 'Setting Up The OpenTelemetry Collector'
 description: 'Learn how to import traces from OpenTelemetry'
 sidebarTitle: 'From OpenTelemetry'
@@ -53,7 +53,7 @@ service:
 ```
 ## Step 2: Restart your collector
 
-Grab your **OTel API key** in the *Send traces* section of the [Open Telemetry Integration page in the Checkly app](https://app.checklyhq.com/settings/account/open-telemetry).  
+Grab your **OTel API key** in the *Send traces* section of the [Open Telemetry Integration page in the Checkly app](https://app.checklyhq.com/settings/account/open-telemetry).
 Now, export your API key in your shell by setting the `CHECKLY_OTEL_API_KEY` environment variable.
 
 ```bash Terminal