Apply suggestions from code review

Co-authored-by: Alex Krawiec <[email protected]>

Author: adinauer

docs/platforms/android/troubleshooting/mixed-versions/index.mdx

@@ -4,11 +4,11 @@ description: "Troubleshoot and resolve mixed Android SDK dependency versions."
 sidebar_order: 1000
 ---
 
-Using multiple Android SDK dependencies with mixed versions is not supported as it is very likely this leads to a crash later on. For this reason we chose to crash the application on SDK init instead.
+Using multiple Android SDK dependencies with mixed versions is not supported as it is very likely to lead to a crash later on. For this reason we chose to crash the application on SDK init instead.
 
 ## Multiple Dependencies With Mixed Versions
 
-The following snippet shows a mix of version caused by using `sentry` with version `8.6.0` and `sentry-android` with version `8.7.0`. To fix the issue please set the same version for all dependencies or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>. This may also happen if you are using an internal library which has a different version defined.
+The following snippet shows a mixed version conflict caused by using `sentry` with version `8.6.0` and `sentry-android` with version `8.7.0`. To fix the issue, set the same version for all dependencies or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>. This may also happen if you are using an internal library which has a different version defined.
 
 ```groovy {tabTitle:Gradle}{filename:build.gradle}
 implementation('io.sentry:sentry:8.6.0')
@@ -33,7 +33,7 @@ implementation('io.sentry:sentry-android:8.7.0')
 
 ## Build Plugin And Explicit Dependency
 
-When using our Gradle or Maven plugin and manually defining additional Sentry Android SDK dependencies it is also possible to end up with mixed versions. The following snippet shows the plugin being configured to use version `8.0.0` but there is also an additional dependency that has been set to version `8.1.0`. To fix the issue please set the same version or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>.
+When using our Gradle or Maven plugin and manually defining additional Sentry Android SDK dependencies, it is also possible to end up with mixed versions. The following snippet shows the plugin being configured to use version `8.0.0` but there is an additional dependency that has been set to version `8.1.0`. To fix the issue,  set the same version or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>.
 
 ```groovy {tabTitle:Gradle}{filename:build.gradle}
 plugins { id "io.sentry.android.gradle" version "5.3.0" }

docs/platforms/java/common/troubleshooting/mixed-versions/index.mdx

@@ -4,11 +4,11 @@ description: "Troubleshoot and resolve mixed Java SDK dependency versions."
 sidebar_order: 1000
 ---
 
-Using multiple Java SDK dependencies with mixed versions is not supported as it is very likely this leads to a crash later on. For this reason we chose to crash the application on SDK init instead.
+Using multiple Java SDK dependencies with mixed versions is not supported as it is very likely to lead to a crash later on. For this reason we chose to crash the application on SDK init instead.
 
 ## Multiple Dependencies With Mixed Versions
 
-The following snippet shows a mix of version caused by using `sentry` with version `8.6.0` and `sentry-logback` with version `8.7.0`. To fix the issue please set the same version for all dependencies or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>. This may also happen if you are using an internal library which has a different version defined.
+The following snippet shows a mixed version conflict caused by using `sentry` with version `8.6.0` and `sentry-logback` with version `8.7.0`. To fix the issue please set the same version for all dependencies or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>. This may also happen if you are using an internal library which has a different version defined.
 
 ```groovy {tabTitle:Gradle}{filename:build.gradle}
 implementation('io.sentry:sentry:8.6.0')
@@ -33,7 +33,7 @@ implementation('io.sentry:sentry-logback:8.7.0')
 
 ## Build Plugin And Explicit Dependency
 
-When using our Gradle or Maven plugin and manually defining additional Sentry Java SDK dependencies it is also possible to end up with mixed versions. The following snippet shows the plugin being configured to use version `8.0.0` but there is also an additional dependency that has been set to version `8.1.0`. To fix the issue please set the same version or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>.
+When using our Gradle or Maven plugin and manually defining additional Sentry Java SDK dependencies, it is also possible to end up with mixed versions. The following snippet shows the plugin being configured to use version `8.0.0`, but there is an additional dependency that has been set to version `8.1.0`. To fix the issue, set the same version or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>.
 
 ```groovy {tabTitle:Gradle}{filename:build.gradle}
 plugins { id "io.sentry.android.gradle" version "5.3.0" }
@@ -51,4 +51,4 @@ sentry {
 
 ## Agent Version And Build Time Version
 
-When using `sentry-opentelemetry-agent` you may end up using a version of the Agent that differs from other Sentry Java SDK dependencies you are using as dependencies. This is also not supported. Please use the same version for `sentry-opentelemetry-agent` and all other Java SDK dependencies.
+When using `sentry-opentelemetry-agent` you may end up using a version of the Agent that differs from other Sentry Java SDK dependencies you are using. This is also not supported. Use the same version for `sentry-opentelemetry-agent` and all other Java SDK dependencies.