Apply suggestions from code review

Alex suggestions

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

Author: mtopo27

docs/platforms/android/size-analysis/insights.mdx

@@ -35,7 +35,9 @@ Below are a list of available insights for Android builds, followed by more deta
 
 **Options**:
 
-- Use Android Studio: right-click an image → **Convert to WebP** → choose **Lossless**.
+**Options:**
+
+- Use Android Studio: right-click an image → **Convert to WebP** → select **Lossless**.
 - Use the command line:
 
   ```bash

docs/platforms/apple/guides/ios/size-analysis/index.mdx

@@ -12,7 +12,7 @@ description: Upload iOS builds to Sentry for size analysis.
 
 **Accepted Formats**: XCArchive (preferred) | IPA
 
-**Upload Mechanisms**: [Fastlane Plugin](#uploading-with-fastlane) | [Sentry CLI](#uploading-with-the-sentry-cli)
+**Upload Mechanisms**: [Fastlane Plugin](#uploading-with-fastlane) (version 1.34.0 or higher) *or* [Sentry CLI](#uploading-with-the-sentry-cli)
 
 ### Uploading with Fastlane
 

docs/platforms/apple/guides/ios/size-analysis/insights.mdx

@@ -40,7 +40,7 @@ Below are a list of available insights for iOS builds, followed by more details
   has them) before stripping.
 </Alert>
 
-In Xcode ensure your release configuration sets the `Debug Information Format` build setting to `DWARF with dSYM`.
+In Xcode, ensure your release configuration sets the `Debug Information Format` build setting to `DWARF with dSYM`.
 
 The `strip` command can then remove the extra information:
 
@@ -192,7 +192,7 @@ optimize_icon() {
 
 ### Loose Images
 
-**What it is**: Finds scaled @1x/@2x/@3x images stored outside of asset catalogs. This prevents app thinning from removing variants not needed for the user's device.
+**What it is**: Finds scaled @1x/@2x/@3x images stored outside of asset catalogs. App thinning will not remove these images, even when they are not needed for the user's device.
 
 **How to fix**: Move each image set into an asset catalog in Xcode.
 
@@ -226,11 +226,11 @@ optimize_icon() {
 
 **How to fix**: Start with low-effort cleanup, then automate comment stripping if you still ship large payloads.
 
-#### Option 1: Keep the format lean
+#### Option 1: Keep the Format Lean
 
 - Encode localized strings as plain text (`"key" = "value";`), not binary plists. Set **Strings File Output Encoding** (`STRINGS_FILE_OUTPUT_ENCODING`) to **UTF-8** in Xcode.
 
-#### Option 2: Strip comments automatically
+#### Option 2: Strip Comments Automatically
 
 String files can have comments that ship with the bundle. They help during translation but take space in production. A typical comment may look like: