Apply suggestions from code review

Author: Karl Heinz Struggl

docs/platforms/android/releases/index.mdx

@@ -16,7 +16,7 @@ We continuously release major/minor/hotfix versions from the `main` branch. Thes
 
 ## `Stable`
 
-Releases are promoted from `Latest` to `Stable` when they've been used in the field for some time and at some scale. The length of time a release has been out, the level of adoption, and other quality and stability metrics are all considered before a release is deemed `Stable`. These types of releases will have a `Stable` label on the <Link to="https://github.com/getsentry/sentry-java/releases/">releases page</Link>. 
+Releases are promoted from `Latest` to `Stable` when they've been used in the field for some time and at some scale. The length of time a release has been out, the level of adoption, and other quality and stability metrics are all considered before a release is deemed `Stable`. These types of releases will have a `Stable` label on the <Link to="https://github.com/getsentry/sentry-java/releases/">releases page</Link>.
 
 ## FAQ
 
@@ -38,4 +38,4 @@ We leave this decision up to you. Stable releases have been tested in the field
 
 ### How does this relate to the stability of a feature?
 
-A `Stable` release status doesn't guarantee the stability of an SDK or product feature. A new feature that's still experimental might be part of a stable SDK release. Any experimental features will be clearly marked and offered as an opt-in.
+A `Stable` release status doesn't guarantee the stability of an SDK feature or product feature. A new feature that's still experimental might be part of a stable SDK release. Any experimental features will be clearly marked and offered as an opt-in.