docs: contains lily's revision

Author: alipsilv

content/pybytes/networks/_index.md

@@ -3,7 +3,7 @@ title: "Networks"
 aliases:
 ---
 
-Pybytes supports four Network Types which you can configure both for each device and for the group of the devices within a project. Those Networks are WiFi, LoRa, Sigfox, and LTE CAT M1 / NB1.  In this section the detailed setting procedure of every network type will be explained.
+Pybytes supports four network types, which you can configure for each device or for a group of devices within a project. The compatible networks are WiFi, LoRa, Sigfox, and LTE CAT M1 / NB1. In this section, a detailed list of the settings for each network has been compiled.
 
 [**Sigfox**](/pybytes/networks/sigfox)
 

content/pybytes/networks/lora/_index.md

@@ -5,20 +5,16 @@ aliases:
 
 ## Overview
 
-Pybytes supports LoRa servers from [The Things Network](https://www.thethingsnetwork.org/) and from [ChirpStack](https://www.chirpstack.io/). During setup of the LoRa connection for your device, whether with TTN or with ChirpStack, Pybytes will automatically create the user profile on those servers.
-
-About the traits of the different LoRa servers, you can uncover more following the links below.
-
+Pybytes supports LoRa servers from [The Things Network](https://www.thethingsnetwork.org/) and from [ChirpStack](https://www.chirpstack.io/). During the set-up of the LoRa connection to your device, whether with TTN or with ChirpStack, Pybytes will automatically create a user profile on those servers.
 
+Follow the links below for more information about the different LoRa servers.
 
 ![TTN Server](/gitbook/assets/pybytes/lora/ttn_logo.svg)
 
 Once a device is created in Pybytes with LoRa network, and the TTN Server is selected, the device is automatically created in TTN server.
 
 For more information check out [The Things Network](https://www.thethingsnetwork.org/docs/)
 
-
-
 ![ChirpStack](/gitbook/assets/pybytes/lora/chirpstack_logo.png)
 
 Pybytes has its own LoRa Server based on [ChirpStack](https://www.chirpstack.io/).

content/pybytes/networks/lora/chirpstack.md

@@ -6,15 +6,15 @@ aliases:
 
 ## Overview
 
-When a LoRa device is created or LoRa network is configured in **Pybytes → Settings -> LoRa** the user profile is automatically created at [ChirpStack](https://loraserver.pycom.io/).
+When a LoRa device is added or the LoRa network is configured in Pybytes → Settings -> LoRa, a user profile is automatically created on [ChirpStack](https://loraserver.pycom.io/). This will only happen if there is no pre-existing user profile.
 
 ## User profile
 
-After creating a LoRa device or configure Pybytes to use ChirpStack, you should receive an email with ChirpStack username and password what you can use for accessing the data on <a href="https://loraserver.pycom.io/"> loraserver.pycom.io</a>.  
+After creating a LoRa device or configuring Pybytes to use ChirpStack, you should receive an email with the ChirpStack username and password. Use this for accessing the data on <a href="https://loraserver.pycom.io/"> loraserver.pycom.io</a>.
 
-The basic configurations are made by Pybytes, but if you want to overwrite the LoRa settings, it is possible to use these credentials.
+The basic configurations are made by Pybytes. If you want to overwrite the LoRa settings, use the ChirpStack username and password to do so.
 
-### What is created by ChirpStack:
+### Basic ChirpStack Settings in Pybytes
 
 **Network-server** - Pycom  
 
@@ -24,40 +24,41 @@ You can add your own server in the section Network-servers
 
 **User** - Value
 
-The User will be created based on the same credentials that are used in Pybytes and it can be managed in the section Org. Users. At the same place, the Admin status of the user can be changed.  
+The User will be created based on the same credentials that are used in Pybytes. This, as well as the Admin status of the user, can be managed in the Org > Users section.
 
 **Organization** - Value (by default)
 
-The Organization Value will be created based on the same credentials used by Pybytes and can be changed in the section Org. Settings.
+The Organization Value will be created, based on the same credentials used in Pybytes. This can be changed in the section Org > Settings.
 
 **Service Profile** - Value (by default)
 
 The Service Profile Name is connected to the Organization’s name.
 
 **Device Profiles** - OTAA or ABP
 
-There are two different devices profiles among which you should select the preferable.  
+There are two different devices profiles, OTAA or ABP. Select which one you prefer.  
 
 **Applications** - Value (by default)
 
-All devices created in Pybytes will be connected to this app.
+All LoRa devices that have been created in Pybytes and linked to the ChirpStack server will be connected to the ChirpStack app.
 
-**Devices** All devices that will be created in Pybytes.
+**Devices**
 
+All LoRa devices that have been created in Pybytes.
 
 ## Gateway
 
 The user should set up their own Gateway in order to communicate with ChirpStack.
 
 ![Gateway](/gitbook/assets/pybytes/lora/screenshots/gateway.png)
 
-### How to set up a gateway: 
+### How to set up a gateway
 
 1 - Login in ChirpStack (https://loraserver.pycom.io/)
 
-2 - Click on **Gateway** on the main sidebar
+2 - Click on the **Gateway** on the main sidebar
 
-3 - Click on **Create** button
+3 - Click on the **Create** button
 
 4 - Fill the form with the information below
 
@@ -75,15 +76,15 @@ The gateway ID.
 
 **Network-server**
 
-Select the network-server to which the gateway will connect. When no network-servers are available in the dropdown, make sure a service-profile exists for this organization.
+Select the network server that the gateway will connect to. When no network servers are available in the dropdown, make sure a service-profile exists for the organization.
 
 **Gateway-profile**
 
-An optional gateway-profile which can be assigned to a gateway. This configuration can be used to automatically re-configure the gateway when LoRa Gateway Bridge is configured so that it manages the packet-forwarder configuration.
+This is an optional gateway profile that can be assigned to a gateway. This can be used to automatically re-configure the gateway when the LoRa Gateway Bridge is set up so that it manages the packet-forwarder settings.
 
 **Gateway discovery enabled**
 
-When enabled (and LoRa Server is configured with the gateway discover feature enabled), the gateway will send out periodical pings to test its coverage by other gateways in the same network.
+When enabled (and LoRa Server is configured with the 'gateway discover' feature enabled), the gateway will send out periodical pings to test its coverage by other gateways in the same network.
 
 **Gateway altitude** (meters)