Copy edit README.md

Copy edit for branding rollout.

Author: Amanda Butler

README.md

@@ -1,4 +1,4 @@
-# Example cellular application for mbed OS
+# Example cellular application for Mbed OS
 
 This is an example based on `mbed-os` cellular APIs that demonstrates a TCP or UDP echo transaction with a public echo server.
 
@@ -10,7 +10,7 @@ The program uses a [generic cellular modem driver](https://github.com/ARMmbed/mb
 
 After registration, the driver opens a point-to-point protocol (PPP) pipe using LWIP with the cellular modem and connects to internet. This driver currently supports UART data connection type only between your cellular modem and MCU.
 
-For more information on ARM mbed OS cellular APIs and porting guide, please visit the [mbed OS cellular documentation](https://os.mbed.com/docs/latest/reference/cellular-api.html).
+For more information on Arm Mbed OS cellular APIs and porting guide, please visit the [Mbed OS cellular API](https://os.mbed.com/docs/latest/reference/cellular-api.html) and [contributing documentation](https://os.mbed.com/docs/latest/reference/contributing-connectivity.html#cellularinterface).
 
 ### Download the application
 
@@ -50,7 +50,7 @@ See the file `mbed_app.json` in the root directory of your application. This fil
 ### Selecting socket type (TCP or UDP)
 
 
-You can choose which socket type the application should use, however please note that TCP is a more reliable tranmission protocol. For example:
+You can choose which socket type the application should use; however, please note that TCP is a more reliable tranmission protocol. For example:
 
 
 ```json
@@ -72,21 +72,21 @@ If you like details and wish to know about all the AT interactions between the m
 
 ### Board support
 
-The [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) this application uses was written using only a standard AT command set. It uses PPP with an mbed-supported external IP stack. These abilities make the driver essentially generic, or nonvendor specific. However, this particular driver is for onboard-modem types. In other words, the modem exists on the mbed Enabled target as opposed to plug-in modules (shields). For more details, please see our [mbed OS cellular documentation](https://docs.mbed.com/docs/mbed-os-api-reference/en/latest/APIs/communication/cellular/).
+The [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) this application uses was written using only a standard AT command set. It uses PPP with an Mbed-supported external IP stack. These abilities make the driver essentially generic, or nonvendor specific. However, this particular driver is for onboard-modem types. In other words, the modem exists on the Mbed Enabled target as opposed to plug-in modules (shields). For more details, please see our [Mbed OS cellular documentation](https://os.mbed.com/docs/latest/reference/cellular-api.html).
 
-Examples of mbed Enabled boards with onboard modem chips include [u-blox C027](https://developer.mbed.org/platforms/u-blox-C027/) and [MultiTech MTS Dragonfly](https://developer.mbed.org/platforms/MTS-Dragonfly/).
+Examples of Mbed Enabled boards with onboard modem chips include [u-blox C027](https://os.mbed.com/platforms/u-blox-C027/) and [MultiTech MTS Dragonfly](https://os.mbed.com/platforms/MTS-Dragonfly/).
 
 ## Compiling the application
 
-Use mbed CLI commands to generate a binary for the application. For example, in the case of GCC, use the following command:
+Use Mbed CLI commands to generate a binary for the application. For example, in the case of GCC, use the following command:
 
 ```sh
 $ mbed compile -m YOUR_TARGET_WITH_MODEM -t GCC_ARM
 ```
 
 ## Running the application
 
-Drag and drop the application binary from `BUILD/YOUR_TARGET_WITH_MODEM/GCC_ARM/mbed-os-example-cellular.bin` to your mbed Enabled target hardware, which appears as a USB device on your host machine.
+Drag and drop the application binary from `BUILD/YOUR_TARGET_WITH_MODEM/GCC_ARM/mbed-os-example-cellular.bin` to your Mbed Enabled target hardware, which appears as a USB device on your host machine.
 
 Attach a serial console emulator of your choice (for example, PuTTY, Minicom or screen) to your USB device. Set the baudrate to 115200 bit/s, and reset your board by pressing the reset button.