Implement SEO recs (#12576)

* Implement SEO recs * Update index.mdx --------- Co-authored-by: Alex Krawiec <[email protected]>
getsentry · Feb 6, 2025 · 5a32172 · 5a32172
1 parent 4484f8a
commit 5a32172
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Releases
 sidebar_order: 110
-description: "Learn how to provide information to Sentry about your releases to determine regressions and resolve issues quickly."
+description: "Learn how to provide Sentry with important information about your releases, such as release health and release details,  to determine regressions and resolve issues faster."
 ---
 
 <Alert>
@@ -10,7 +10,7 @@ If you're looking for the latest Sentry SDK release details, head on over to <a
 
 </Alert>
 
-A _release_ is a version of your code deployed to an environment. When you notify Sentry about a <SandboxLink scenario="oneRelease" projectSlug="react">release</SandboxLink>, you can easily identify new issues and regressions, determine whether an issue was resolved, and monitor the health of your newly deployed app. The **Releases** page provides a visualization of your releases. It presents adoption of releases from the past 24 hours and provides a high-level view of:
+A _release_ is a version of your code deployed to an environment. When you notify Sentry about a <SandboxLink scenario="oneRelease" projectSlug="react">release</SandboxLink>, you can easily identify new [issues](/product/issues/) and regressions, determine whether an issue was resolved, and monitor the health of your newly deployed app. The **Releases** page provides a visualization of your releases. It presents adoption of releases from the past 24 hours and provides a high-level view of:
 
 - Each release version (a short version of the release name without the hash)
 - The associated project
@@ -46,7 +46,7 @@ We recommend notifying Sentry about a new release before deploying it. But if yo
 
 You don't need a repository integration for any of these features, though we recommend [installing one as part of an automated release option](/product/releases/setup/release-automation/) for efficiency.
 
-## Associate Commits
+## Associate Commits in Releases
 
 With releases, you can [associate commits](/product/releases/associate-commits/), which keeps track of the commits that were used in a release.
 
@@ -58,11 +58,11 @@ _Release health_ provides insight into the impact of crashes and bugs as it rela
 
 You can view release health data either from the <SandboxLink scenario="oneIssue" projectSlug="react">Issue Details</SandboxLink> page by selecting the commit ID listed under Last Seen", or from the **Releases** page.
 
-## Different Ways to Resolve Issues
+## 3 Different Ways to Resolve Issues
 
 If you'd like to mark an issue as [resolved](/product/issues/states-triage/#resolve) in both a current and a future release, you can do so by resolving it in a release via the dropdown on the issue details page.
 
-There are several options for resolving a release issue. If you'd like to leave the issue unresolved and be notified of it the next time any event is seen in a release, click the main "Resolve" button. But if you'd like to ignore the release issue until it's seen again in your current or next release, you can select "Resolved In The next release" or "Resolved In The current release" from the dropdown.
+There are several options for resolving a release issue. If you'd like to leave the release issue unresolved and be notified of it the next time any event is seen in a release, click the main "Resolve" button. But if you'd like to ignore the release issue until it's seen again in your current or next release, you can select "Resolved In The next release" or "Resolved In The current release" from the dropdown.
 
 ![View of the resolve issue dropdown options on issue details.](./img/resolved_in_options.png)
 
@@ -78,6 +78,6 @@ The "Resolved in the next release" option works like resolving in the current re
 
 The "Resolved in a commit" option allows you to wait for a release with the specified commit to be created. Once the release is created, new events get checked against the release version or release date. If the new events are from a newer release, the issue gets marked as a regression and appears in your [For Review tab](/product/issues/states-triage/) to be triaged.
 
-## Learn More
+## Learn More About Releases
 
 <PageGrid />