Fix typos

Author: kianmeng

README.md

@@ -54,7 +54,7 @@ The server:
      over-the-air activation (OTAA).
    * Supports both unconfirmed and confirmed data uplink and downlink.
    * Supports multicast to user-defined groups.
-   * Supports all regions standartized in LoRaWAN 1.0.3 Regional Parameters for
+   * Supports all regions standardized in LoRaWAN 1.0.3 Regional Parameters for
      Europe, US, China, Australia, Asia, South Korea, India and Russia.
  * Provides a network management interface.
    * Supports both manual and automatic configuration of data rate (ADR) and other parameters.

doc/Applications.md

@@ -138,7 +138,7 @@ The function may return:
 
 ### handle_delivery({Network, Profile, Node}, Result, Receipt)
 
-The `handle_delivery/3` will be called after successfull or unsuccessfull delivery
+The `handle_delivery/3` will be called after successful or unsuccessful delivery
 of a confirmed downlink frame:
   - **Network** parameters where the node is operating
   - **Profile** of the node

doc/Connectors.md

@@ -28,7 +28,7 @@ To create a new connector you set:
    topic for event messages.
  - **Subscribe QoS** determines reliability of the subscriptions.
  - **Subscribe**, which is a topic to be subscribed. It may include broker specific
-   wilcards, e.g. `in/#`. The MQTT broker will then send messages with a matching
+   wildcards, e.g. `in/#`. The MQTT broker will then send messages with a matching
    topic to this connector.
  - **Received Topic**, which is a template for parsing the topic of received
    (subscribed) messages, e.g. `in/{devaddr}`. This can be used to retrieve the
@@ -44,7 +44,7 @@ If the Connector is *Enabled* the server will automatically connect to the
 backend server and subscribe this topic.
 
 When a *Failed* flag is raised, the connector is inactive and no connection is
-established. To re-establish the connection after an error occures, fix the
+established. To re-establish the connection after an error occurs, fix the
 indicated root cause and then remove the flag to reactivate the connector.
 
 On the Authentication tab:

doc/Development.md

@@ -29,7 +29,7 @@ starts one process for each incoming each connection:
  - **lorawan_admin_...** modules provide handlers for the REST API. They interact with
    the mnesia database only.
  - **lorawan_connector_ws** provide handler for the WebSocket interface. One
-   handler invoked for each incoming connection, ot joins a given pg2 group as
+   handler invoked for each incoming connection, to joins a given pg2 group as
    every connector and then filters the uplink frames based on given URI.
 
 

doc/Handlers.md

@@ -2,7 +2,7 @@
 
 Handlers define externally handled application, including:
  * Format of the uplink and downlink messages
- * Data fields forwared via the backend *Connectors*
+ * Data fields forwarded via the backend *Connectors*
  * Retransmission logic for confirmed downlinks
 
 Each Handler may be linked with one or more backend *Connectors*, which handle

doc/Installation.md

@@ -147,7 +147,7 @@ You will need the following prerequisites:
    * On Windows follow the [installation instructions](https://www.rebar3.org/docs/getting-started).
    * On Mac OS, run `brew install rebar`.
  * npm, the JavaScript package manager.
-   * On Linux follow the instructions bellow.
+   * On Linux follow the instructions below.
    * On Windows, install the [Node.js](https://nodejs.org/en/).
    * On Mac OS, run `brew install node`.
 

doc/Integration.md

@@ -1,6 +1,6 @@
 # Integration Guide
 
-This document desribes specific configuration required to integrate with the
+This document describes specific configuration required to integrate with the
 following IoT cloud platforms:
  * [Amazon AWS IoT](https://aws.amazon.com/iot/)
  * [IBM Watson IoT Platform](https://www.ibm.com/cloud-computing/bluemix/internet-of-things)

doc/Introduction.md

@@ -65,7 +65,7 @@ frames and (optionally) send downlink frames.
 
 Handlers define externally handled application, including:
  * Format of the uplink and downlink messages
- * Data fields forwared via the backend *Connectors*
+ * Data fields forwarded via the backend *Connectors*
  * Retransmission logic for confirmed downlinks
 
 Each Handler may be linked with one or more backend Connectors, which handle

doc/Server.md

@@ -76,7 +76,7 @@ listing of errors and warnings is in the server logs.
 Each record contains
  - **Severity** of the issue: error, warning or info.
  - **First Occurred** timestamp
- - **Last Occurred** timestamp, which gets updated everytime this event occurs.
+ - **Last Occurred** timestamp, which gets updated every time this event occurs.
  - **Count** of occurrences, which gets increased by 1.
  - **Entity** concerned by the event: server, gateway, device, node, connector.
  - **EId**, which is an identifier of the concerned entity.

include/lorawan_db.hrl

@@ -218,7 +218,7 @@
     app :: binary(),
     devaddr :: devaddr(),
     location :: any(),
-    gateways :: [{binary(), #rxq{}}], % singnal quality at each gateway
+    gateways :: [{binary(), #rxq{}}], % signal quality at each gateway
     average_qs :: 'undefined' | {number(), number()}, % average RSSI and SNR
     powe:: integer(),
     fcnt :: integer(),

src/lorawan_gw_forwarder.erl

@@ -83,7 +83,7 @@ handle_info({udp, Socket, _Host, _Port, <<_Version, Token:16, 5, MAC:8/binary, D
         end,
     case trim_json(Data) of
         <<>> ->
-            % no error occured
+            % no error occurred
             ok;
         _ ->
             case catch jsx:decode(Data, [return_maps, {labels, atom}]) of

src/lorawan_mac.erl

@@ -296,7 +296,7 @@ check_fcnt({Network, Profile, Node}, FCnt) ->
                 rxwin_use=Network#network.rxwin_init, rxwin_failed=[],
                 last_reset=calendar:universal_time(), devstat_fcnt=undefined, last_qs=[]}};
         Profile#profile.fcnt_check == 3, FCnt == 0 ->
-            % somebody might be constantly reseting the device
+            % somebody might be constantly resetting the device
             {ok, uplink, Node#node{fcntup = 0, fcntdown = 0}};
         Profile#profile.fcnt_check == 3 ->
             % checks disabled