Editorial changes, streamlining sentences

Author: Mel W

README.md

@@ -4,7 +4,7 @@ The Mbed OS driver for the ESP8266 WiFi module.
 
 ## Firmware version
 
-ESP8266 modules come in different shapes and formats, but the most important factor is the firmware version in it. To
+ESP8266 modules come in different shapes and formats, but the firmware version is the most important factor. To
 make sure that the firmware in your module is compatible with Mbed OS, follow the
 [Update guide](https://developer.mbed.org/teams/ESP8266/wiki/Firmware-Update).
 
@@ -13,18 +13,18 @@ This driver supports AT firmware versions 1.3.0 to 1.7.0. We advise updating the
 
 ## Restrictions
 
-- The ESP8266 Wi-Fi module does not allow the TCP client to bind on a specific port.
+- The ESP8266 Wi-Fi module does not allow the TCP client to bind to a specific port.
 - Setting up a UDP server is not possible.
 - The serial port does not have hardware flow control enabled by default. Additionally, the AT command set does not have a method for limiting the download rate. Therefore, downloading anything larger than the serial port input buffer is unreliable 
 unless you use [AT firmware](https://www.espressif.com/en/support/download/at?keys=) version 1.7.0 or later. With older
 firmware, an application should be able to read fast enough to stay ahead of the network. This applies mostly to TCP
-protocol, where data would be lost without notification. With all firmware versions on UDP, this would lead to packet loss that the higher-layer protocol should recover from.
+protocol, where data would be lost without notification. On UDP using all firmware versions, the higher-layer protocol should recover from packet loss.
 
 ## Mandatory configuration
 
 ![mbed_lib.json](mbed_lib.json) configuration assumes Arduino form factor. Please adjust according to your board. You can override parameters from your app config file.
 
-Least one is expected to check are the following configuration parameters
+At minimum, check the following configuration parameters:
 
 ```javascript
 {
@@ -54,14 +54,12 @@ Least one is expected to check are the following configuration parameters
 ## UART HW flow control
 
 UART HW flow control requires you to additionally wire the CTS and RTS flow control pins between your board and your
-ESP8266 module. Once this is done remember to add configuration option for flow control in your app config file. Here a
-[ST NUCLEO-F429ZI](https://os.mbed.com/platforms/ST-Nucleo-F429ZI/) board and
-[ESPBee XBee Module](https://www.cascologix.com/product/espbee/) are used as an example.
+ESP8266 module. After this, remember to add the configuration option for flow control to your app configuration file. This example uses the [ST NUCLEO-F429ZI](https://os.mbed.com/platforms/ST-Nucleo-F429ZI/) board and
+[ESPBee XBee Module](https://www.cascologix.com/product/espbee/).
 
-**NOTE** Not all modules expose ESP8266's RTS and CTS pins so beware when you are choosing one.
+**Note:** Not all modules expose ESP8266's RTS and CTS pins, so choose modules carefully.
 
-Once you have your HW set up add configuration like this in your app config - Arduino pins D1 and D0 assumed to be used
-as TX and RX:
+Once you have your hardware set up, add a configuration like the following to your app configuration file. Arduino pins D1 and D0 are used as TX and RX:
 
 ``` javascript
 "target_overrides": {
@@ -72,23 +70,26 @@ as TX and RX:
 ```
 
 ### Example board pins
+
     1. TX - D1 (Arduino Uno Revision 3 connectivity  headers)
     2. RX - D0 (Arduino Uno Revision 3 connectivity headers)
     3. RTS - PG_12 (STMicroelectronics Morpho extension pin headers)
     4. CTS - PG_15 (STMicroelectronics Morpho extension pin headers)
 
 ### Example ESP8266 pins
-    1. TX - D1 (Arduino Wireless Protoshield headers)/ TX (ESPBee XBee headers)
+
+1. TX - D1 (Arduino Wireless Protoshield headers)/ TX (ESPBee XBee headers)
     2. RX - D0 (Arduino Wireless Protoshield headers)/ RX (ESPBee XBee headers)
     3. RTS - RTS (ESPBee XBee headers)
     4. CTS - CTS (ESPBee XBee headers)
 
 ### Connections
+
 With these pictures only consider the green and yellow wires which are connected to ESP8266. Pink wire is for reset and
 the rest for firmware update. TX and RX go through Arduino pins D1 and D0.
 
-**NOTE** GPIO15(ESPBee RTS) needs to be pulled down during startup to boot from flash, instead of firmware update or
-boot from SD card. Once the software is running the same pin is used as the RTS pin.
+**Note:** Pull down GPIO15(ESPBee RTS) during startup to boot from flash, instead of **firmware update** or
+**boot from SD card**. Once the software is running, the same pin is used as the RTS pin:
 
     1. Board TX - ESP8266 RX
     2. Board RX - ESP8266 TX