update content urls

docs/faq/questions/cloud-faq.mdx

@@ -46,7 +46,7 @@ before being sent to the Cloud so those are not captured.
 
 When [Test Replay](#Test-Replay) capturing is enabled, the additional data outlined
 below will be sent to the Cloud. You can
-[disable capturing](/guides/cloud/debugging/test-replay#Opt-out-of-Test-Replay) this data.
+[disable capturing](/guides/cloud/test-replay#Opt-out-of-Test-Replay) this data.
 
 - The rendered DOM and CSS styles for the application under test
 - Cypress commands and events represented in the Command Log
@@ -87,7 +87,7 @@ the number of tests you record each month in your organization.
 
 Tests are recorded when [cypress run](/guides/guides/command-line#cypress-run)
 is called with the `--record` flag while supplying the record `--key`. This
-means your [test run data](/guides/cloud/debugging/recorded-runs#Latest-Runs) is being
+means your [test run data](/guides/cloud/recorded-runs#Latest-Runs) is being
 "recorded" to Cypress Cloud.
 
 We consider each time the `it()` function is called to be a single test. So you
@@ -164,7 +164,7 @@ any test results.
 ### <Icon name="angle-right" /> What is the projectId for?
 
 The `projectId` is a 6-character string that helps identify your project once
-you've [set up your tests to record](/guides/cloud/debugging/recorded-runs#Latest-Runs).
+you've [set up your tests to record](/guides/cloud/recorded-runs#Latest-Runs).
 It's generated by Cypress and typically is found in your
 [Cypress configuration](/guides/references/configuration).
 
@@ -185,7 +185,7 @@ section of the [Cypress Cloud](/guides/cloud/introduction) docs.
 ### <Icon name="angle-right" /> What is a Record Key?
 
 A _Record Key_ is a GUID that's generated automatically by Cypress once you've
-[set up your tests to record](/guides/cloud/debugging/recorded-runs#Latest-Runs). It helps
+[set up your tests to record](/guides/cloud/recorded-runs#Latest-Runs). It helps
 identify your project and authenticate that your project is even _allowed_ to
 record tests.
 
@@ -204,14 +204,14 @@ section of the [Cypress Cloud](/guides/cloud/introduction) docs.
 ### <Icon name="angle-right" /> How do I record my tests?
 
 1. First [set up the project to record](/guides/cloud/getting-started#Setup).
-2. Then [record your runs](/guides/cloud/debugging/recorded-runs#Latest-Runs).
+2. Then [record your runs](/guides/cloud/recorded-runs#Latest-Runs).
 
 After recording your tests, you will see them in
 [Cypress Cloud](https://on.cypress.io/cloud) and in the Cypress App [Runs](/guides/core-concepts/cypress-app#Runs) tab.
 
 ### <Icon name="angle-right" /> Can I delete a run from Cypress Cloud?
 
-You can [archive a run](/guides/cloud/debugging/recorded-runs#Archive-run) so that it does
+You can [archive a run](/guides/cloud/recorded-runs#Archive-run) so that it does
 not display in the runs list or in analytics.
 
 **Note:** Archiving the recorded runs has no effect on the amount of tests
@@ -330,7 +330,7 @@ in your account will be permanently deleted.
 
 ### <Icon name="angle-right" /> What is Test Replay?
 
-[Test Replay](/guides/cloud/debugging/test-replay) enables you and your team to troubleshoot and debug failed tests faster. After updating to Cypress `v13`, the new feature will automatically record all browser events and allow you to “replay” what your application under test looked like.
+[Test Replay](/guides/cloud/test-replay) enables you and your team to troubleshoot and debug failed tests faster. After updating to Cypress `v13`, the new feature will automatically record all browser events and allow you to “replay” what your application under test looked like.
 
 Wind back the clock to any point in an application's test execution and directly interact with tests as they happened in CI. Debug complex problems as if you were there when they first happened. You can:
 
@@ -381,15 +381,15 @@ Our aim is to create an impactful debugging experience that covers the most grou
 
 Test Replay leverages [Chrome DevTools Protocol(CDP)](https://chromedevtools.github.io/devtools-protocol/), so currently supports Chromium-based browsers (Chrome, Edge, and Electron) only.
 
-Test Replay would be disabled, with a message that it's only available on Chromium, for tests run in Firefox or WebKit (Safari). You can still record and capture test [artifacts](/guides/cloud/debugging/recorded-runs#Artifacts) (screenshots, videos and CI logs) via other browsers in separate [run groups](/guides/cloud/smart-orchestration/parallelization#Grouping-test-runs).
+Test Replay would be disabled, with a message that it's only available on Chromium, for tests run in Firefox or WebKit (Safari). You can still record and capture test [artifacts](/guides/cloud/recorded-runs#Artifacts) (screenshots, videos and CI logs) via other browsers in separate [run groups](/guides/cloud/smart-orchestration/parallelization#Grouping-test-runs).
 
 ### <Icon name="angle-right" /> Can I replay tests from historical Cypress Cloud runs?
 
 Test Replay is available for tests recorded using Cypress `v13` and up. Tests recorded prior to this will not have Test Replay enabled in Cypress Cloud. You will still have any artifacts collected during the pre `v13` test runs.
 
 ### <Icon name="angle-right" /> Can I enable or disable Test Replay for specific, individual tests, or is it a global setting? Can I configure my settings so that Test Replay is only enabled for failing test retries?
 
-At this time, users can only opt-out of Test Replay via [project-level settings](/guides/cloud/debugging/test-replay#Opt-out-of-Test-Replay) in Cypress Cloud. There is no local option for opting out at this time.
+At this time, users can only opt-out of Test Replay via [project-level settings](/guides/cloud/test-replay#Opt-out-of-Test-Replay) in Cypress Cloud. There is no local option for opting out at this time.
 
 ### <Icon name="angle-right" /> Can I share my test replays?
 

docs/guides/cloud/branch-review.mdx

@@ -98,7 +98,7 @@ The header includes the Git commit message, PR selector, PR status, and base and
 
 If there are multiple pull requests open for the same branch, you can select the pull request you want to review from the dropdown to the right of the commit message.
 
-Clicking the branch label will link you directly to the appropriate [run overview](/guides/cloud/debugging/recorded-runs#Overview-tab) and hovering on these elements exposes additional run meta data.
+Clicking the branch label will link you directly to the appropriate [run overview](/guides/cloud/recorded-runs#Overview-tab) and hovering on these elements exposes additional run meta data.
 
 <DocsImage
   src="/img/guides/cloud/branch-review/branch-review-header.jpg"

docs/guides/cloud/data-storage-and-masking.mdx

@@ -30,7 +30,7 @@ When you run Cypress via `cypress run` and pass the `--record` flag, the followi
 - Videos
 - OS environment variables related to CI and git information
 
-When [Test Replay](/guides/cloud/debugging/test-replay) capturing is enabled, the additional data outlined below will be sent to Cypress Cloud. [See our guide on disabling Test Replay.](/guides/cloud/debugging/test-replay#Opt-out-of-Test-Replay)
+When [Test Replay](/guides/cloud/test-replay) capturing is enabled, the additional data outlined below will be sent to Cypress Cloud. [See our guide on disabling Test Replay.](/guides/cloud/test-replay#Opt-out-of-Test-Replay)
 
 - The rendered DOM and CSS styles for the application under test
 - Cypress commands and events represented in the Command Log
@@ -57,7 +57,7 @@ Setting a project to private means that only the users explicitly invited to the
 
 #### Disable Test Replay
 
-You can disable capturing data in Test Replay per project by following [this guide](/guides/cloud/debugging/test-replay#Opt-out-of-Test-Replay). This means Test Replay will not be available for viewing or debugging in the project. This will prevent Cypress Cloud from capturing the following data:
+You can disable capturing data in Test Replay per project by following [this guide](/guides/cloud/test-replay#Opt-out-of-Test-Replay). This means Test Replay will not be available for viewing or debugging in the project. This will prevent Cypress Cloud from capturing the following data:
 
 - The rendered DOM and CSS styles for the application under test
 - Cypress commands and events represented in the Command Log
@@ -129,7 +129,7 @@ You can delete videos that are recorded when you are passing `video: true` by fo
 
 You can disable showing the entirety of the Cypress Command Log as well as the Application under Test (AUT) controls in your tests to prevent all test content from being shown and recorded in any screenshot or video by passing `--no-runner-ui` via the CLI while running Cypress tests. See [Cypress Command Line options](/guides/guides/command-line#Options). This means that the AUT will be the only thing that is rendered while running tests, so the only thing that is captured in screenshots and videos.
 
-Note that when `--no-runner-ui` is set, data from the Cypress Command Log will still be sent to Cypress Cloud to be generated and displayed in Test Replay if it is enabled. See [Disable Test Replay](/guides/cloud/debugging/test-replay#Opt-out-of-Test-Replay) for more information.
+Note that when `--no-runner-ui` is set, data from the Cypress Command Log will still be sent to Cypress Cloud to be generated and displayed in Test Replay if it is enabled. See [Disable Test Replay](/guides/cloud/test-replay#Opt-out-of-Test-Replay) for more information.
 
 #### Mask data in the Cypress Command Log
 

docs/guides/cloud/introduction.mdx

@@ -25,19 +25,19 @@ read on for more benefits of Cypress Cloud.
 ### View and debug past test results
 
 Each test run is stored in Cypress Cloud, where you can see past results and the
-current state of your app on the [Latest Runs](/guides/cloud/debugging/recorded-runs) page.
+current state of your app on the [Latest Runs](/guides/cloud/recorded-runs) page.
 
-Replay the test as it executed during the recorded run with full debug capability using [<Logo src="/img/guides/cloud/test-replay/replay-icon.svg" /> Test Replay](/guides/cloud/debugging/test-replay).
+Replay the test as it executed during the recorded run with full debug capability using [<Logo src="/img/guides/cloud/test-replay/replay-icon.svg" /> Test Replay](/guides/cloud/test-replay).
 
 Or view each test's
-[command logs, screenshots, video replays, stack traces, and CI logs](/guides/cloud/debugging/recorded-runs#Test-detail-sidebar).
+[command logs, screenshots, video replays, stack traces, and CI logs](/guides/cloud/recorded-runs#Test-detail-sidebar).
 Quickly identifying a test failure in CI is just a click away.
 
 <DocsVideo src="https://vimeo.com/806005654" />
 
 ### Analyze and diagnose test health
 
-View each [run's overview](/guides/cloud/debugging/recorded-runs#Overview-tab) to see and compare
+View each [run's overview](/guides/cloud/recorded-runs#Overview-tab) to see and compare
 past runs and analyze trends over time. You can quickly analyze changes in your
 setup that might introduce problematic trends as well as identify unreliable
 tests with [Flaky Test Management](/guides/cloud/flaky-test-management).
@@ -64,7 +64,7 @@ no setup required! You can prioritize recently failed specs with
 surface problems earlier, and cancel whole test runs on failure with
 [Auto Cancellation](/guides/cloud/smart-orchestration/run-cancellation) to save
 on resource usage. You can also
-[cancel in-progress runs](/guides/cloud/debugging/recorded-runs#Run-cancellation) manually
+[cancel in-progress runs](/guides/cloud/recorded-runs#Run-cancellation) manually
 from Cypress Cloud if you need to.
 
 <DocsImage
@@ -77,7 +77,7 @@ Cypress Cloud's
 lets you prioritize recently failed specs so they run faster on their next run.
 The [Auto Cancellation](/guides/cloud/smart-orchestration/run-cancellation)
 feature will cancel a whole test run on failure, saving time and resource usage.
-You can also [cancel in-progress runs](/guides/cloud/debugging/recorded-runs#Run-cancellation)
+You can also [cancel in-progress runs](/guides/cloud/recorded-runs#Run-cancellation)
 manually from Cypress Cloud if you need to.
 
 ### Integrate with your favorite tools
@@ -125,7 +125,7 @@ directly from specific test failures.
 
 ### Cypress app integration
 
-The [Cypress app](/guides/cloud/debugging/recorded-runs#Cypress-App) integrates directly with
+The [Cypress app](/guides/cloud/recorded-runs#Cypress-App) integrates directly with
 Cypress Cloud to provide developers with the latest test results without having
 to switch tools.
 

docs/guides/cloud/recorded-runs.mdx

@@ -119,7 +119,7 @@ It orders results by:
 - **Flaky** - when a test failed one or more attempts before finally passing
 - **Modified** - when the test body has changed from a previously recorded tests
 
-The panel shows these tests broken down by spec, with a badge clearly indicating the reason the result was considered notable. Access run artifacts with a mouse hover to quickly expose the [Test Replay](/guides/cloud/debugging/test-replay), [screenshots](/guides/guides/screenshots-and-videos#Screenshots),
+The panel shows these tests broken down by spec, with a badge clearly indicating the reason the result was considered notable. Access run artifacts with a mouse hover to quickly expose the [Test Replay](/guides/cloud/test-replay), [screenshots](/guides/guides/screenshots-and-videos#Screenshots),
 [videos](/guides/guides/screenshots-and-videos#Videos), and CI logs generated by this test.
 
 Clicking on a specific test opens the

docs/guides/cloud/smart-orchestration/run-cancellation.mdx

@@ -38,7 +38,7 @@ failure will:
 **Auto Cancellation** is a _Smart Orchestration_ feature available to users with
 a [Business or Enterprise tier Cypress Cloud plan](https://cypress.io/pricing).
 Wondering if upgrading your Team tier subscription is worth it? Check out the
-[recommendations](/guides/cloud/debugging/recorded-runs#Recommendations) on the run
+[recommendations](/guides/cloud/recorded-runs#Recommendations) on the run
 overview page to see how much time we predict these features would save you.
 
 :::

docs/guides/cloud/smart-orchestration/spec-prioritization.mdx

@@ -39,7 +39,7 @@ time.**
 with a
 [Business or Enterprise tier Cypress Cloud plan](https://cypress.io/pricing).
 Wondering if upgrading your Team tier subscription is worth it? Check out the
-[recommendations](/guides/cloud/debugging/recorded-runs#Recommendations) on the run
+[recommendations](/guides/cloud/recorded-runs#Recommendations) on the run
 overview page to see how much time we predict these features would save you.
 
 :::

docs/guides/cloud/test-replay.mdx

@@ -57,14 +57,14 @@ All you need to do after [recording test runs](/guides/cloud/getting-started) is
 
 Accessing the replay of your test is as simple as reviewing any other test artifact in Cypress Cloud.
 
-1. Hover on a [test for review](/guides/cloud/debugging/recorded-runs#Tests-for-Review) under the Latest Runs Overview.
+1. Hover on a [test for review](/guides/cloud/recorded-runs#Tests-for-Review) under the Latest Runs Overview.
 
    <DocsImage
      src="/img/guides/cloud/test-replay/replay_row_magnified.jpg"
      alt="Run overview row"
    />
 
-2. Or navigate to the [test detail sidebar](/guides/cloud/debugging/recorded-runs#Test-detail-sidebar) header or above each attempt in the errors panel. The header option will replay the first failing test while the option above each attempt will replay the affiliated test.
+2. Or navigate to the [test detail sidebar](/guides/cloud/recorded-runs#Test-detail-sidebar) header or above each attempt in the errors panel. The header option will replay the first failing test while the option above each attempt will replay the affiliated test.
 
    <DocsImage
      src="/img/guides/cloud/test-replay/replay_sidebar_magnified.jpg"

docs/guides/continuous-integration/github-actions.mdx

@@ -433,8 +433,8 @@ are leveraging three useful features of
    to [Cypress Cloud](https://on.cypress.io/cloud):
 
    - In-depth and shareable
-     [test reports](/guides/cloud/debugging/recorded-runs#Latest-Runs).
-   - Visibility into test failures via quick access to [Test Replay](/guides/cloud/debugging/test-replay), error messages, stack
+     [test reports](/guides/cloud/recorded-runs#Latest-Runs).
+   - Visibility into test failures via quick access to [Test Replay](/guides/cloud/test-replay), error messages, stack
      traces, screenshots, videos, and contextual details.
    - [Integrating testing with the pull-request (PR) process](/guides/cloud/integrations/source-control/github)
      via

docs/guides/continuous-integration/introduction.mdx

@@ -660,7 +660,7 @@ CI providers. Find the workshop at
   viewport sizes.
 - [cypress-example-kitchensink](https://github.com/cypress-io/cypress-example-kitchensink#ci-status)
   is set up to run on multiple CI providers.
-- [Test Replay](/guides/cloud/debugging/test-replay)
+- [Test Replay](/guides/cloud/test-replay)
 - [Cross Browser Testing Guide](/guides/guides/cross-browser-testing)
 - [Blog: Setting up Bitbucket Pipelines with proper caching of npm and Cypress](https://www.cypress.io/blog/2018/08/30/setting-up-bitbucket-pipelines-with-proper-caching-of-npm-and-cypress/)
 - [Blog: Record Test Artifacts from any Docker CI](https://www.cypress.io/blog/2018/08/28/record-test-artifacts-from-any-ci/)

docs/guides/core-concepts/cypress-app.mdx

@@ -163,7 +163,7 @@ Running a large number of specs sequentially can consume more resources.
 />
 
 This screen shows detailed information about the most recently recorded
-[test runs](/guides/cloud/debugging/recorded-runs#Latest-Runs) to Cypress Cloud, showing
+[test runs](/guides/cloud/recorded-runs#Latest-Runs) to Cypress Cloud, showing
 the latest first.
 
 Cypress uses Git to show runs for your branch. Ensure that version control is
@@ -192,11 +192,11 @@ This feature eliminates the tedious process of switching between Cypress, your
 local editor, and CI output, in order to fix failed tests. It does this by
 enabling you to use the [Test Runner](#Test-Runner) to run only the tests that
 failed in your last recorded test run, as well as review the
-[Test Replay](/guides/cloud/debugging/test-replay) and other artifacts like screenshots,
+[Test Replay](/guides/cloud/test-replay) and other artifacts like screenshots,
 videos, and logs from your tests.
 
 The Debug page shows the latest completed
-[test run](/guides/cloud/debugging/recorded-runs#Latest-Runs) that matches the `HEAD` commit
+[test run](/guides/cloud/recorded-runs#Latest-Runs) that matches the `HEAD` commit
 (the commit currently checked out in the working directory) of your local
 project. Users can see and switch to relevant runs within the Debug page. If no
 run is found for your current commit, then Cypress shows the most recent run in
@@ -217,7 +217,7 @@ information using
 />
 
 You can receive notifications in the Cypress app for recorded runs directly from
-Cypress Cloud. Learn more about [Cloud Run Notifications](/guides/cloud/debugging/recorded-runs#Notifications).
+Cypress Cloud. Learn more about [Cloud Run Notifications](/guides/cloud/recorded-runs#Notifications).
 
 ## Test Runner
 

docs/guides/core-concepts/writing-and-organizing-tests.mdx

@@ -247,9 +247,9 @@ module API option, if specified)
 />
 
 Instead of administering assets yourself, you can
-[save them to the cloud with Cypress Cloud](/guides/cloud/debugging/recorded-runs#Run-Details).
+[save them to the cloud with Cypress Cloud](/guides/cloud/recorded-runs#Run-Details).
 
-Replay the test as it executed during the recorded run with full debug capability using [<Logo src="/img/guides/cloud/test-replay/replay-icon.svg" /> Test Replay](/guides/cloud/debugging/test-replay).
+Replay the test as it executed during the recorded run with full debug capability using [<Logo src="/img/guides/cloud/test-replay/replay-icon.svg" /> Test Replay](/guides/cloud/test-replay).
 
 Screenshots and videos are stored permanently, attached to their respective test
 results, and easily shared or browsed through our web interface. To learn more about videos and settings available, see
@@ -826,7 +826,7 @@ it could be a user hitting this bug!
   alt="Cypress with a single failed test"
 />
 
-After a test fails, the [Test Replay](/guides/cloud/debugging/test-replay) or screenshots and videos with Cypress Cloud can help find the problem so it
+After a test fails, the [Test Replay](/guides/cloud/test-replay) or screenshots and videos with Cypress Cloud can help find the problem so it
 can be fixed.
 
 ### Pending