Apply suggestions from code review

mtopo27 · coolguyzone · web-flow · commit 5b84ef2c055f · 2025-11-04T15:06:38.000-05:00
Co-authored-by: Alex Krawiec &lt;alex.krawiec@sentry.io&gt;
diff --git a/docs/platforms/android/size-analysis/index.mdx b/docs/platforms/android/size-analysis/index.mdx
@@ -15,11 +15,11 @@ description: Upload Android builds to Sentry for Size Analysis.
 
 **Upload Mechanisms**: [Gradle](#uploading-with-gradle) | [Sentry CLI](#uploading-with-the-sentry-cli)
 
-### Uploading with Gradle
+### Uploading With Gradle
 
 <Include name="size-analysis/upload-gradle" />
 
-### Uploading with the Sentry CLI
+### Uploading With the Sentry CLI
 
 <Include name="size-analysis/upload-cli-android" />
 
@@ -31,7 +31,7 @@ description: Upload Android builds to Sentry for Size Analysis.
 
 <Include name="size-analysis/build-configuration-android" />
 
-## What's next?
+## What's Next?
 
 We strongly recommend integrating Size Analysis into your CI pipeline. Follow our guide on [getting set up in CI](/product/size-analysis/integrating-into-ci/).
 
diff --git a/docs/platforms/android/size-analysis/insights.mdx b/docs/platforms/android/size-analysis/insights.mdx
@@ -4,7 +4,7 @@ sidebar_order: 5250
 description: Preview how Size Analysis reports highlight Android build trends.
 ---
 
-Size Analysis Insights point out how opportunities to reduce your Android app's size. They spot patterns like duplicate files, oversized media, or unneeded assets, and list exactly what to fix along with the estimated size savings.
+Size Analysis Insights point out opportunities to reduce your Android app's size. They spot patterns like duplicate files, oversized media, or unneeded assets, and list exactly what to fix along with the estimated size savings.
 
 ## Android Insights
 
@@ -31,7 +31,6 @@ Below are a list of available insights for Android builds, followed by more deta
 
 **How to fix**: Compress images with lossless WebP or resize them before bundling.
 
-**Options**:
 
 **Options:**
 
diff --git a/docs/platforms/apple/guides/ios/size-analysis/index.mdx b/docs/platforms/apple/guides/ios/size-analysis/index.mdx
@@ -14,7 +14,7 @@ description: Upload iOS builds to Sentry for size analysis.
 
 **Upload Mechanisms**: [Fastlane Plugin](#uploading-with-fastlane) (version 1.34.0 or higher) *or* [Sentry CLI](#uploading-with-the-sentry-cli)
 
-### Uploading with Fastlane
+### Uploading With Fastlane
 
 <Include name="size-analysis/upload-fastlane" />
 
@@ -38,7 +38,7 @@ description: Upload iOS builds to Sentry for size analysis.
 
 <Include name="size-analysis/app-store-connect-file-sizes" />
 
-## What's next?
+## What's Next?
 
 We strongly recommend integrating Size Analysis into your CI pipeline. Follow our guide on [getting set up in CI](/product/size-analysis/integrating-into-ci/).
 
diff --git a/docs/platforms/apple/guides/ios/size-analysis/insights.mdx b/docs/platforms/apple/guides/ios/size-analysis/insights.mdx
@@ -4,7 +4,7 @@ sidebar_order: 5250
 description: See how Size Analysis surfaces trends for your iOS builds.
 ---
 
-Size Analysis Insights point out how opportunities to reduce your iOS app's size. They spot patterns like duplicate files, oversized media, or unneeded assets, and list exactly what to fix along with the estimated size savings.
+Size Analysis Insights point out opportunities to reduce your iOS app's size. They spot patterns like duplicate files, oversized media, or unneeded assets, and list exactly what to fix along with the estimated size savings.
 
 ## iOS Insights
 
diff --git a/includes/size-analysis/build-configuration-ios.mdx b/includes/size-analysis/build-configuration-ios.mdx
@@ -1,3 +1,3 @@
 Features such as automatically comparing the head build against the base build **will only compare builds of the same build configuration**. This is important to consider when setting up Size Analysis in your CI. For example, `Release` and `Debug` builds can be drastically different depending on the compiler and linker settings used during the build process. Trying to compare the two would give unexpected results.
 
-Sometimes this is expected though, say if you want to test the impact of converting your project to use Bazel (e.g. `Release` vs `Release-Bazel`). In this case, it's still possible to perform a manual comparison of builds with different build configurations.
+Sometimes this is expected though, say you want to test the impact of converting your project to use Bazel (e.g. `Release` vs `Release-Bazel`). In this case, it's still possible to perform a manual comparison of builds with different build configurations.
diff --git a/includes/size-analysis/upload-cli-android.mdx b/includes/size-analysis/upload-cli-android.mdx
@@ -1,6 +1,6 @@
 1. Install the [sentry-cli](/cli/)
 
-2. Authenticate the sentry-cli by [following these steps](https://docs.sentry.io/cli/configuration/#to-authenticate-manually)
+2. Authenticate the Sentry CLI by [following these steps](https://docs.sentry.io/cli/configuration/#to-authenticate-manually)
 
 3. Build your app to create an AAB (preferred) or APK
 
diff --git a/includes/size-analysis/upload-cli-ios.mdx b/includes/size-analysis/upload-cli-ios.mdx
@@ -1,6 +1,6 @@
 1. Install the [sentry-cli](/cli/)
 
-2. Authenticate the sentry-cli by [following these steps](https://docs.sentry.io/cli/configuration/#to-authenticate-manually)
+2. Authenticate the Sentry CLI by [following these steps](https://docs.sentry.io/cli/configuration/#to-authenticate-manually)
 
 3. Build your app to create an XCArchive (preferred) or IPA
 
diff --git a/includes/size-analysis/upload-gradle.mdx b/includes/size-analysis/upload-gradle.mdx
@@ -46,7 +46,7 @@ export SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
 
 The Gradle plugin automatically detects build metadata from your git repository. On GitHub Actions, all metadata is automatically detected. On other CI systems, you may need to manually set some values using the (`vcsInfo`)[https://developer.android.com/reference/tools/gradle-api/8.8/com/android/build/api/dsl/VcsInfo] extension.
 
-Configure overrides in your Gradle build configuration
+Configure overrides in your Gradle build configuration:
 
 ```kotlin {filename:build.gradle.kts}
 sentry {

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`	`1`	Features such as automatically comparing the head build against the base build will only compare builds of the same build configuration. This is important to consider when setting up Size Analysis in your CI. For example, `Release` and `Debug` builds can be drastically different depending on the compiler and linker settings used during the build process. Trying to compare the two would give unexpected results.
`2`	`2`
`3`		-Sometimes this is expected though, say if you want to test the impact of converting your project to use Bazel (e.g. `Release` vs `Release-Bazel`). In this case, it's still possible to perform a manual comparison of builds with different build configurations.
	`3`	+Sometimes this is expected though, say you want to test the impact of converting your project to use Bazel (e.g. `Release` vs `Release-Bazel`). In this case, it's still possible to perform a manual comparison of builds with different build configurations.