Tweak README (#28)

Author: petterh

README.md

@@ -6,25 +6,25 @@
 |---|---|
 | [![Build Status](https://dev.azure.com/petter0012/react-native-android-activity/_apis/build/status/petterh.react-native-android-activity?branchName=master)](https://dev.azure.com/petter0012/react-native-android-activity/_build/latest?definitionId=1&branchName=master) | [[![Build Status](https://dev.azure.com/petter0012/react-native-android-activity/_apis/build/status/petterh.react-native-android-activity%20(1)?branchName=master)](https://dev.azure.com/petter0012/react-native-android-activity/_build/latest?definitionId=2&branchName=master) |
 
-This sample, which grew out of a [question on Stack Overflow](https://stackoverflow.com/questions/42253397/call-android-activity-from-react-native-code/43675819), demonstrates the interface between React Native JavaScript and Java code in Android host applications/Objective-C in iOS applications.
+This sample, which grew out of a [question on Stack Overflow](https://stackoverflow.com/questions/42253397/call-android-activity-from-react-native-code/43675819), demonstrates the interface between React Native JavaScript and native code – Java on Android, Objective-C on iOS.
 
-The original version was Android-only; support for iOS was added March 28 2019.
+The original version was Android-only; support for iOS was added in March 2019.
 
 This project demonstrates the following:
 
-* Call from JavaScript into native modules:
-  * These use a custom native module called `ActivityStarter`:
+* Calling from JavaScript into native modules:
+  * ...using a custom native module called `ActivityStarter`:
     * Navigate from React Native to a Java activity (or iOS view controller) internal to the host app;
     * Start an external intent to dial a phone number, passing data from JavaScript;
     * Query the host app for information.
-  * This uses the native module `Clipboard`, which [comes with React Native out of the box](https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/modules/clipboard/ClipboardModule.java):
+  * ...using the native module `Clipboard`, which [comes with React Native out of the box](https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/modules/clipboard/ClipboardModule.java):
     * Copy information to the clipboard.
-* Call a JavaScript method from Java or Objective-C, using an officially undocumented approach.
-* Demonstrate sending events from the native platform to JavaScript. (When possible, prefer this approach to the undocumented one.)
-* Verify that custom edit menu extensions work with React Native `TextInput`. (Android only.)
-* Add a custom menu option to React Native debug menu.
+* Calling a JavaScript method from Java or Objective-C, using an officially undocumented approach.
+* Sending events from the native platform to JavaScript. (When possible, prefer this approach to the undocumented one.)
+* Verifying that custom edit menu extensions work with React Native `TextInput`. (Android only.)
+* Adding a custom menu option to React Native debug menu.
 
-There is no technical difference between the `ActivityStarter` and `Clipboard` native modules, except one is defined here, while the other ships as part of React Native.
+There is no technical difference between the `ActivityStarter` and `Clipboard` native modules, except one is defined in this project while the other ships as part of React Native.
 
 The starting point for this sample is a slightly tweaked standard React Native project as generated by a long-outdated version of `react-native init`. We add six buttons to the generated page:
 
@@ -53,7 +53,8 @@ The `TextInput` box appears only in the Android version. Since both platforms us
 
 ### Android
 
-* Connect an Android device via USB, or use an emulator. [Don't forget to enable USB Debugging in Developer options](https://developer.android.com/studio/run/device).
+* Connect an Android device via USB, or use an emulator.
+* [Enable USB Debugging in Developer options](https://developer.android.com/studio/run/device).
 * Open the app in Android Studio and run it.
 * If this fails with the message "Could not get BatchedBridge, make sure your bundle is packaged correctly", your packager is likely not running.
 * If it complains about connecting to the dev server, run `adb reverse tcp:8081 tcp:8081`