Cellular docs updated

Author: Ari Parkkila

docs.json

@@ -1147,10 +1147,6 @@
  "type": "markdown",
  "url": "https://github.com/ARMmbed/mbed-os-5-docs/blob/development/docs/tutorials/using_apis/flow_control.md"
  },
- {
- "type": "markdown",
- "url": "https://github.com/ARMmbed/mbed-os-5-docs/blob/development/docs/tutorials/using_apis/connectivity/cellular_tcp.md"
- },
  {
  "type": "markdown",
  "url": "https://github.com/ARMmbed/mbed-os-5-docs/blob/development/docs/tutorials/using_apis/ble_tutorial.md"

docs/api/networkinterfaces/CellularInterface.md

@@ -1,10 +1,8 @@
-<h2 id="cellular-api">Cellular</h2>
+<h2 id="cellular-api">Cellular API</h2>
 
-<span class="images">![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_base.png)<span>CellularBase class hierarchy</span></span>
+<span class="images">![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.png)<span>CellularInterface class hierarchy</span></span>
 
-The [CellularBase](https://os.mbed.com/docs/development/mbed-os-api-doxy/_cellular_base_8h_source.html) provides a C++ API for connecting to the internet over a Cellular device.
-
-Arm Mbed OS provides a [reference implementation of CellularBase](https://os.mbed.com/docs/development/mbed-os-api-doxy/_cellular_context_8h_source.html), which has more information.
+The [CellularInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.html) class provides a C++ API for connecting to the internet over a Cellular device.
 
 ##### Getting started
 
@@ -48,15 +46,15 @@ You can use and extend a cellular interface in various different ways. For examp
 - The easy cellular connection uses standard 3GPP AT 27.007 AT commands to set up the cellular modem and to register to the network.
 - After registration, the driver opens a PPP pipe using LWIP with the cellular modem and connects to the internet. If AT only mode is in use, then modem-specific AT commands are used for socket data control.
 
-### CellularBase class reference
+### CellularInterface class reference
 
-[![View code](https://www.mbed.com/embed/?type=library)](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_base.html)
+[![View code](https://www.mbed.com/embed/?type=library)](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.html)
 
 ### Usage
 
 To bring up the network interface:
 
-1. Instantiate an implementation of the CellularBase class.
+1. Instantiate an implementation of the CellularInterface class.
 1. Call the `connect(pincode, apn)` function with a PIN code for your SIM card and an APN for your network.
 1. Once connected, you can use Mbed OS [network sockets](network-socket.html) as usual.
 
@@ -69,6 +67,6 @@ This example establishes connection with the cellular network using Mbed OS Cell
 ### Related content
 
 - [Network socket](network-socket.html) API reference overview.
-- [Cellular architecture](../reference/cellular.html).
+- [Cellular overview](../reference/cellular.html) describes more details about the cellular architecture and its usage.
 - [Cellular TCP sockets example](../tutorials/cellular-tcp-sockets.html).
 - [Cellular configuration documentation](../reference/configuration-connectivity.html).

docs/api/networkinterfaces/networkinterface.md

@@ -79,7 +79,7 @@ Applications may also ask for a specific type of connection, as the following ta
 |`*WiFiInterface::get_default_instance()`| Wi-Fi interface | Requires security parameters (mode, SSID, password). |
 |`*EthInterface::get_default_instance()` | Wired Ethernet interface, not Wi-Fi | none |
 |`*MeshInterface::get_default_instance()` | Returns either `LoWPANNDInterface` or `ThreadInterface`, depending on which is set to default | Target provides a driver or macro `DEVICE_802_15_4_PHY` is enabled. |
-| `*CellularBase::get_default_instance()` | Return cellular connectivity | Requires network parameters (pin, APN, username, password). |
+| `*CellularInterface::get_default_instance()` | Return cellular connectivity | Requires network parameters (pin, APN, username, password). |
 | `*NetworkInterface::get_default_instance()` | One of the above, depending on `target.network-default-interface-type`. | |
 
 Note that the calls for a specific interface type do not preconfigure credentials such as SSID because an interface-type-specific application is expected to configure these in code. `NULL` is returned if no interface of that type is available.

docs/porting/connectivity/CellularInterface.md

@@ -1,8 +1,8 @@
-## Cellular module porting
+## Cellular device porting
 
-This document provides guidelines how to make a cellular modem adaptation for Mbed OS. Please see [Cellular API usage](../apis/cellular-api.html) about how to use cellular modules from an application point of view.
+This document provides guidelines how to make a cellular device adaptation for Mbed OS.
 
-### Adding modem target support
+### Adding cellular on Mbed OS target
 
 For new targets, you may need to modify [targets.json](../reference/adding-and-configuring-targets.html), which defines all the target platforms that Mbed OS supports. If Mbed OS supports your specific target, an entry for your target is in this file. To tell the Mbed OS build configuration that your target board has an onboard cellular module, you need to define `modem_is_on_board` and `modem_data_connection_type`.
 
@@ -56,7 +56,7 @@ typedef enum {
 
 ```
 
-### Adding a new cellular target
+### Adding a new cellular device
 
 You need to specify in [CellularTargets.h](https://os.mbed.com/docs/development/mbed-os-api-doxy/_cellular_targets_8h_source.html) the `<manufacturer-module>` that is mounted on your board.
 

docs/porting/connectivity/NetworkStack.md

@@ -14,7 +14,7 @@ Please refer to the [IP networking architecture](../reference/ip-networking.html
 
 #### NetworkInterface Class
 
-The current NetworkInterface subclasses are [CellularInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_base.html), [EthernetInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_eth_interface.html), [MeshInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_mesh_interface.html) and [WiFiInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_wi_fi_interface.html). Your communication interface is a subclass of one of these, as well as the NetworkStack. For example, the [ESP8266Interface](https://github.com/ARMmbed/esp8266-driver) inheritance structure looks like this:
+The current NetworkInterface subclasses are [CellularInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.html), [EthernetInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_eth_interface.html), [MeshInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_mesh_interface.html) and [WiFiInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_wi_fi_interface.html). Your communication interface is a subclass of one of these, as well as the NetworkStack. For example, the [ESP8266Interface](https://github.com/ARMmbed/esp8266-driver) inheritance structure looks like this:
 
 <span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/esp-class.png)<span>Class</span></span>
 

docs/porting/connectivity/connectivity.md

@@ -12,7 +12,7 @@ The **DeviceInterface** should also inherit one of the following (unless it is a
 
 - [EthInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_eth_interface.html).
 - [WiFiInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_wi_fi_interface.html).
-- [CellularInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_base.html).
+- [CellularInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.html).
 - [MeshInterface](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_mesh_interface.html).
 
 The **NetworkInterface** implementation provides the following methods:

docs/reference/configuration/Connectivity.md

@@ -198,11 +198,11 @@ Boards that provide only Ethernet connectivity do not require any configuration.
 
 Select the default interface type by using one of the following `target.network-default-interface-type` parameters:
 
-| `target.network-default-interface-type` | Required configuration |
+| `target.network-default-interface-type` | Configuration parameters |
 |-----------------------------------------|------------------------|
 | `ETHERNET` | nothing |
 | `WIFI` | `nsapi.default-wifi-security`, `nsapi.default-wifi-ssid` and `nsapi.default-wifi-password` |
-| `CELLULAR` | `nsapi.default-cellular-apn`, `nsapi.default-cellular-username` and `nsapi.default-cellular-password` |
+| `CELLULAR` | `nsapi.default-cellular-sim-pin`, `nsapi.default-cellular-apn`, `nsapi.default-cellular-username` and `nsapi.default-cellular-password`, `nsapi.default-cellular-plmn` |
 | `MESH` | `nsapi.default-mesh-type` |
 
 ```
@@ -223,9 +223,6 @@ Name: nsapi.default-wifi-ssid
 Name: nsapi.default-wifi-password
  Defined by: library:nsapi
  No value set
-Name: nsapi.default-cellular-plmn
-Defined by: library:nsapi
- No value set
 Name: nsapi.default-cellular-sim-pin
 Defined by: library:nsapi
  No value set
@@ -238,6 +235,9 @@ Name: nsapi.default-cellular-password
 Name: nsapi.default-cellular-username
  Defined by: library:nsapi
  No value set
+Name: nsapi.default-cellular-plmn
+ Defined by: library:nsapi
+ No value set
 Name: nsapi.default-mesh-type
  Defined by: library:nsapi
  Macro name: MBED_CONF_NSAPI_DEFAULT_MESH_TYPE