Fix links to Test Replay and content limitations (#6060)

Author: MikeMcC399

docs/accessibility/core-concepts/how-it-works.mdx

@@ -43,4 +43,4 @@ In rare cases - such as if an Axe Core® update contains a critical security pat
 
 ## Powered by Test Replay
 
-Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject [Test Replay limitations](https://docs.cypress.io/faq/questions/cloud-faq#Is-everything-captured-and-replayed-in-Test-Replay).
+Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject to Test Replay limitations. Read [How Test Replay Works](/cloud/features/test-replay#How-Test-Replay-Works) to discover which data is captured and which browsers are supported.

docs/ui-coverage/get-started/introduction.mdx

@@ -54,4 +54,4 @@ UI Coverage captures "snapshots" of every page visited by your Cypress tests (an
 
 As a result, a UI Coverage score is generated. This score quantifies coverage across your application by measuring the ratio of the unique elements that have been tested to the total unique elements that are found across your application.
 
-Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject to any [limitations of Test Replay](https://docs.cypress.io/faq/questions/cloud-faq#Is-everything-captured-and-replayed-in-Test-Replay) data captured and browser support.
+Because Cypress UI Coverage uses data captured through Cypress Test Replay, it is subject to Test Replay limitations. Read [How Test Replay Works](/cloud/features/test-replay#How-Test-Replay-Works) to discover which data is captured and which browsers are supported.