include TR content in body copy

docs/guides/cloud/debugging/recorded-runs.mdx

@@ -119,9 +119,8 @@ 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 easy access to run
-artifacts, and a badge clearly indicating the reason the result was considered
-notable.
+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) or [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
 [test detail sidebar](#Test-detail-sidebar).
@@ -228,7 +227,7 @@ to raise tickets on integrated project management systems or view artifacts.
 ### Attempts and errors
 
 Stack traces, error message, and point-of-failure code frames for each attempt
-of a test.
+of a test. View or debug artifacts of each particular attempt.
 
 <DocsImage
   src="/img/guides/cloud/runs/sidebar-errors.png"
@@ -247,6 +246,9 @@ successes on the current branch.
 
 ### Artifacts
 
+[Test Replay](/guides/cloud/debugging/test-replay) to view the
+test as it executed in CI with full debug capability.
+
 [Screenshots](/guides/guides/screenshots-and-videos#Screenshots),
 [videos](/guides/guides/screenshots-and-videos#Videos) and CI logs generated by
 this test. Both screenshots taken during failures and screenshots taken using

docs/guides/cloud/introduction.mdx

@@ -25,8 +25,11 @@ read on for more benefits of Cypress Cloud.
 ### View 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. View
-each test's
+current state of your app on the [Latest Runs](/guides/cloud/debugging/recorded-runs) page.
+
+Replay the test as it executed during the recorded run with full debug capability using [Test Replay](/guides/cloud/debugging/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).
 Quickly identifying a test failure in CI is just a click away.
 

docs/guides/continuous-integration/aws-codebuild.mdx

@@ -437,7 +437,7 @@ are leveraging three useful features of
 
    - In-depth and shareable
      [test reports](/guides/cloud/debugging/recorded-runs#Latest-Runs).
-   - Visibility into test failures via quick access to error messages, stack
+   - Visibility into test failures via quick access to [Test Replay](/guides/cloud/debugging/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/bitbucket-pipelines.mdx

@@ -274,7 +274,7 @@ section, we are leveraging three useful features of
 
    - In-depth and shareable
      [test reports](/guides/cloud/debugging/recorded-runs#Latest-Runs).
-   - Visibility into test failures via quick access to error messages, stack
+   - Visibility into test failures via quick access to [Test Replay](/guides/cloud/debugging/test-replay), error messages, stack
      traces, screenshots, videos, and contextual details.
    - [Integrating testing with the pull-request process](/guides/cloud/integrations/source-control/bitbucket)
      via

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

@@ -426,7 +426,7 @@ are leveraging three useful features of
 
    - In-depth and shareable
      [test reports](/guides/cloud/debugging/recorded-runs#Latest-Runs).
-   - Visibility into test failures via quick access to error messages, stack
+   - Visibility into test failures via quick access to [Test Replay](/guides/cloud/debugging/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/gitlab-ci.mdx

@@ -248,7 +248,7 @@ leveraging three useful features of
 
    - In-depth and shareable
      [test reports](/guides/cloud/debugging/recorded-runs#Latest-Runs).
-   - Visibility into test failures via quick access to error messages, stack
+   - Visibility into test failures via quick access to [Test Replay](/guides/cloud/debugging/test-replay), error messages, stack
      traces, screenshots, videos, and contextual details.
    - [Integrating testing with the merge-request process](/guides/cloud/integrations/source-control/gitlab)
      via

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

@@ -827,7 +827,7 @@ it could be a user hitting this bug!
   alt="Cypress with a single failed test"
 />
 
-After a test fails, the screenshots and videos can help find the problem so it
+After a test fails, the screenshots and videos or [Test Replay](/guides/cloud/debugging/test-replay) with Cypress Cloud can help find the problem so it
 can be fixed.
 
 ### Pending

docs/guides/end-to-end-testing/migration/protractor-to-cypress.mdx

@@ -65,11 +65,15 @@ describe('Authorization Tests', () => {
 })
 ```
 
+:::info
+
 To see how this conversion would work with some of your own test code, you can
 paste it into the interactive
 [Cypress Migrator tool](https://migrator.cypress.io/), which will generate the
 equivalent Cypress code.
 
+:::
+
 ## Benefits of Using Cypress
 
 As many developers can attest to, end-to-end testing is one of those things that
@@ -155,10 +159,13 @@ too indirect. To understand the reason behind test failures it also helps to see
 the state of the app UI at the point of failure or see the events that led up to
 the failure.
 
-Cypress assists with debugging in headless mode, by automatically taking a
-screenshot of the app UI and command log at the exact point of test failure. To
-see everything that happened prior to test failure, enable the `video`
-configuration option to record (as an MP4 file) the full test spec run.
+Cypress assists with debugging in headless mode, in numerous ways:
+
+- By automatically taking a
+  screenshot of the app UI and command log at the exact point of test failure.
+- To see everything that happened prior to test failure, enable the [`video`](/guides/references/configuration#Videos).
+  configuration option to record (as an MP4 file) the full test spec run.
+- Replay the test as it executed during the recorded run with full debug capability using [Test Replay](/guides/cloud/debugging/test-replay) in Cypress Cloud.
 
 ### Test Retries
 
@@ -1115,6 +1122,8 @@ For more information, check out our
 
 :::
 
+<TestReplayInfo />
+
 ## Angular Schematic Configuration
 
 The

docs/guides/overview/why-cypress.mdx

@@ -116,10 +116,10 @@ do that no other testing framework can:
   involving your server. You can stub network traffic however you like.
 - **Consistent Results:** Our architecture doesn't use Selenium or WebDriver.
   Say hello to fast, consistent and reliable tests that are flake-free.
-- **Screenshots and Videos:** View screenshots taken automatically on failure,
+- **Screenshots, Videos, and Test Replay:** View screenshots taken automatically on failure,
   or videos, if enabled, of your entire test suite when run from the CLI. Record
   to [Cypress Cloud](/guides/cloud/introduction) to store them with your test
-  results.
+  results. Replay the test as it executed during the recorded run with full debug capability using [Test Replay](/guides/cloud/debugging/test-replay) in Cypress Cloud.
 - **Cross Browser Testing:** Run tests within Firefox and Chrome-family browsers
   (including Edge and Electron) locally and
   [optimally in a Continuous Integration pipeline](/guides/guides/cross-browser-testing).