adding more details, screenshots, and URLs

Author: Shannon Anahata

docs/product/test-analytics/index.mdx

@@ -4,20 +4,24 @@ sidebar_order: 135
 description: Learn about how Sentry Prevent's Test Analytics tools can help you improve your code.
 ---
 
-Sentry Prevent Test Analytics provides actionable insights into your CI test runs, helping you identify flaky tests, track failures, and optimize your test suite for faster, more reliable deployments.
+Sentry Prevent Test Analytics provides actionable insights into your CI test runs, helping you identify flaky tests, track failures, and optimize your test suite for faster, more reliable deployments. 
 
 ## Why Use Test Analytics?
 
 - **Spot Flaky Tests:** Quickly identify and address tests that fail intermittently, reducing noise and wasted debugging time.
 - **Track Failures and Trends:** Monitor cumulative failures, slowest tests, and overall test run efficiency to improve CI reliability.
 - **Actionable Insights:** See which lines of code failed within tests, confirm flaky tests, and prioritize fixes.
-- **Integrated with Sentry:** Access test analytics alongside your error and performance data for a unified developer experience. Yay
+- **Integrated with Sentry:** Access test analytics alongside your error and performance data for a unified developer experience.
 
 ## Getting Started
 
-To use Sentry Prevent Test Analytics, you’ll need to install the [Sentry app]() on your GitHub organization or specific repositories. Once installed, choose your JUnit XML Report language and [set your permissions](#permissions-and-repository-tokens) using a repository secret.
+<Alert>
+  Sentry Prevent Test Analytics is currently in <strong>beta</strong>. Beta features are still a work in progress and may have bugs. 
+</Alert>
+
+![Test Analytics Dashboard](./img/TA-dash.png)
 
-*Insert Arcade GIF or screenshot here*
+To use Sentry Prevent Test Analytics, you’ll need to install the [Sentry app]() on your GitHub organization or specific repositories. Once installed, choose your JUnit XML Report language and [set your permissions](#permissions-and-repository-tokens) using a repository secret.
 
 **There are two ways to upload your test results:**
 
@@ -38,14 +42,12 @@ Now that you've configured your CI to upload your test results, you can inspect
 
 After your workflow runs, view failed tests in the [failed tests dashboard](), or in your GitHub pull request comments.
 
-*Insert Arcade GIF or screenshot here*
+![Test Analytics comment](./img/TA-comment.png)
 
 You can see a complete overview of your test analytics in the [test analytics dashboard]().
 
-*insert screenshot here*
-
 ##  Permissions and Repository Tokens
-When configuring Test Analytics, you'll be asked to choose your upload permissions. For GitHub Actions, you can use [OpenID Connect](https://openid.net/developers/how-connect-works/), or generate a repository token. Using the CLI, generate a repository token. 
+When configuring Test Analytics, you'll be asked to choose your upload permissions. For GitHub Actions, you can use [OpenID Connect](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect), or generate a repository token. Using the CLI, generate a repository token. 
 
 You can find a list of repository tokens on the Sentry Prevent [tokens page]().