Skip to content

Commit 294dc93

Browse files
author
Amanda Butler
authored
Copy edit networksocket.md
Copy edit, mostly for active voice and fixing some minor details left in the mesh section previously.
1 parent b3b3c44 commit 294dc93

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

docs/reference/api/connectivity/networksocket/networksocket.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -76,12 +76,12 @@ Existing network interfaces:
7676

7777
Here are example applications that are built on top of the network-socket API:
7878

79-
* [HTTP and HTTPS](https://os.mbed.com/teams/sandbox/code/http-example/).
80-
* [MQTT](https://os.mbed.com/teams/mqtt/code/HelloMQTT/).
81-
* [CoAP](https://os.mbed.com/teams/sandbox/code/coap-example/).
82-
* [Websockets](https://os.mbed.com/cookbook/Websockets-Server).
83-
* [TCP ping-pong with a computer](https://github.com/armmbed/mbed-tcp-ping-pong).
84-
* [UDP ping-pong with a computer](https://github.com/armmbed/mbed-udp-ping-pong).
79+
- [HTTP and HTTPS](https://os.mbed.com/teams/sandbox/code/http-example/).
80+
- [MQTT](https://os.mbed.com/teams/mqtt/code/HelloMQTT/).
81+
- [CoAP](https://os.mbed.com/teams/sandbox/code/coap-example/).
82+
- [Websockets](https://os.mbed.com/cookbook/Websockets-Server).
83+
- [TCP ping-pong with a computer](https://github.com/armmbed/mbed-tcp-ping-pong).
84+
- [UDP ping-pong with a computer](https://github.com/armmbed/mbed-udp-ping-pong).
8585

8686
##### Example
8787

@@ -134,25 +134,24 @@ You can use and extend a cellular interface in various different ways. For examp
134134

135135
[`mbed-os-example-cellular`](https://github.com/ARMmbed/mbed-os-example-cellular) uses [an easy cellular connection](https://github.com/ARMmbed/mbed-os/tree/master/features/cellular/easy_cellular). It depends on the modem whether the application uses PPP or AT mode. We can summarize this particular design as follows:
136136

137-
- It uses an external IP stack (for example, LWIP), or on-chip network stacks for example in case of PPP is not supported by the modem.
137+
- It uses an external IP stack, such as LWIP, or on-chip network stacks such as when the modem does not support PPP.
138138
- The easy cellular connection uses standard 3GPP AT 27.007 AT commands to set up the cellular modem and to register to the network.
139-
- After registration, the driver opens up a PPP (Point-to-Point Protocol) pipe using LWIP with the cellular modem and connects to the internet,
140-
or if AT only mode is in use, then modem specific AT commands are used for socket data control.
139+
- 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.
141140

142141
#### Arm Mbed Mesh
143142

144143
The Arm Mbed Mesh API allows the application to use the IPv6 mesh network topologies through the [Nanostack](/docs/v5.7/tutorials/mesh.html#nanostack) networking stack.
145144

146145
Mbed OS provides two types of IPv6 based mesh networks:
147146

148-
* 6LoWPAN_ND, loosely following the Zigbee-IP specification.
149-
* Thread, following the specification from Thread Group.
147+
- 6LoWPAN_ND, loosely following the Zigbee-IP specification.
148+
- Thread, following the specification from Thread Group.
150149

151-
Nanostack is the networking stack which provides both of these protocols. For more information on the stack internals, refer to [Nanostack documentation](/docs/v5.7/tutorials/mesh.html#nanostack). Application developers use Nanostack through Mbed Mesh API.
150+
Nanostack is the networking stack that provides both of these protocols. For more information on the stack internals, please refer to the [Nanostack documentation](/docs/v5.7/tutorials/mesh.html#nanostack). Application developers use Nanostack through the Mbed Mesh API.
152151

153-
The application can use the `LoWPANNDInterface` or `ThreadInterface` object for connecting to the mesh network and when successfully connected, the application can use the Mbed C++ socket APIs to create a socket to start communication with a remote peer.
152+
The application can use the `LoWPANNDInterface` or `ThreadInterface` object for connecting to the mesh network. When successfully connected, the application can use the Mbed C++ socket APIs to create a socket to start communication with a remote peer.
154153

155-
The `NanostackEthernetInterface` is provided for Ethernet.
154+
Mbed OS provides `NanostackEthernetInterface` for Ethernet.
156155

157156
##### Supported mesh networking modes
158157

0 commit comments

Comments
 (0)