doc: Cleanup README wording

Author: qdot

README.md

@@ -113,38 +113,24 @@ setup.
 
 There is now a build script at `./scripts/build-java.sh` for building the java portion of the library on linux or macOS. This can also be used as a guide for manual building if need be.
 
-Proguard optimization can be an issue when using btleplug, as the .aar file generated by the java
-code in btleplug is only accessed by native code, and can be optimized out as part of dead code
-removal and resource shrinking. To fix this, changes will need to be made to your build.gradle file, and proguard rules will need to be defined.
+If your app uses Proguard/R8 with `minifyEnabled true`, you must add keep rules for btleplug's
+Java classes. All of btleplug's Java code (including vendored jni-utils classes) is only accessed
+via JNI from native code, so R8 will treat it as dead code and strip it without these rules.
 
-For build.gradle:
+In your `build.gradle`, ensure Proguard is configured for release builds:
 ```groovy
     buildTypes {
         release {
-            // TODO: Add your own signing config for the release build.
-            // Signing with the debug keys for now, so `flutter run --release` works.
-            signingConfig signingConfigs.debug
-
             shrinkResources true
             minifyEnabled true
-
             proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
-
         }
     }
 ```
 
 proguard-rules.pro:
 ```
-#Flutter Wrapper - Only needed if using flutter
--keep class io.flutter.app.** { *; }
--keep class io.flutter.plugin.**  { *; }
--keep class io.flutter.util.**  { *; }
--keep class io.flutter.view.**  { *; }
--keep class io.flutter.**  { *; }
--keep class io.flutter.plugins.**  { *; }
-
-#btleplug resources
+# btleplug Java classes (accessed only via JNI)
 -keep class com.nonpolynomial.** { *; }
 -keep class io.github.gedgygedgy.** { *; }
 ```
@@ -202,13 +188,13 @@ west build -b nrf52840dk/nrf52840 && west flash
 cargo test --test '*' -- --ignored
 ```
 
-**Quick start without hardware:**
+**Quick start with a virtual peripheral (requires USB BLE dongle):**
 
 ```bash
-# Start the Bumble virtual peripheral (requires USB BLE dongle)
+# Start the Bumble virtual peripheral
 cd test-peripheral/bumble
 pip install -r requirements.txt
-./run.sh usb:0
+./run.sh usb:0  # transport argument may vary; see Bumble docs
 
 # In another terminal, run integration tests
 cargo test --test '*' -- --ignored