6 files changed, 95 insertions, 99 deletions

diff --git a/_ont_xgs/ont-fs-XGS-ONU-25-20NI.md b/_ont_xgs/ont-fs-XGS-ONU-25-20NI.md
index 9b52603..bdfb733 100644
--- a/_ont_xgs/ont-fs-XGS-ONU-25-20NI.md
+++ b/_ont_xgs/ont-fs-XGS-ONU-25-20NI.md
@@ -58,7 +58,7 @@ By shorting these two points with solder, you can access the UART from SFP pins
 | RX                    | pin #2                     |
 | GND                   | pin #10                    |
 
-{% include alert.html content="USB TTL adapter may not work due to insufficient power supply. If possible, obtain 3.3V from the power supply device instead of the USB TTL adapter." alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="USB TTL adapter may not work due to insufficient power supply. If possible, obtain 3.3V from a dedicated power supply instead of the USB TTL adapter." alert="Note"  icon="svg-info" color="blue" %}
 
 {% include image.html file="XGS-ONU-25-20NI/UART_SFP.png" alt="XGS-ONU-25-20NI UART Short point" caption="XGS-ONU-25-20NI UART Short point" %}
 
@@ -95,18 +95,18 @@ Available from `#ONT/system>ontver build` and `#ONT/system/shell>cat /etc/versio
 
 This ONT supports dual boot. 
 
-`kernel0` and `rootfs0` respectively contain the kernel and firmware of the first image, `kernel1` and `rootfs1` the kernel and the firmware of the second one.
+`kernel0` and `rootfs0` respectively contain the kernel and firmware of the first image, `kernel1` and `rootfs1` the kernel and firmware of the second one.
 
 # Useful files and binaries
 
 ## scfg.txt
 In the XGS-ONU-25-20NI ONT, the settings are loaded by four `scfg.txt` files.
-For rewriting settings, `/userdata/scfg.txt` and `/tmp/scfg.txt` are used.
+For overwriting settings, `/userdata/scfg.txt` and `/tmp/scfg.txt` are used.
 
 - `/config/default_scfg.txt`  (read only): Contains the manufacturer's default settings, which are read first at ONT startup and are the lowest priority settings.
 - `/config/scfg.txt`  (read only): Contains settings set by the firmware creator, which have higher priority than `default_scfg.txt` and will overwrite the settings if there is a conflict.
 - `/userdata/scfg.txt` (read/write): Contains settings set by the user or ISP. It has a higher priority than `/config/scfg.txt` and will overwrite the settings if there is a conflict. Can be edited and saved.
-- `/tmp/scfg.txt` (temp): It contains dynamically generated settings based on values stored on its custom ROM (mtd9, mtd10). Since they are generated on tmpfs and cannot be saved directly, they are rewritten via the `#ONT> system/misc` command on the ONT.
+- `/tmp/scfg.txt` (temp): It contains dynamically generated settings based on values stored on its custom ROM (mtd9, mtd10). Because they are generated on tmpfs and cannot be saved directly, they are rewritten via the `#ONT> system/misc` command on the ONT.
 
 The settings are overwritten and loaded at startup with the following priority:
 
@@ -124,36 +124,36 @@ To configure settings using the MISC command, execute the following command:
 
 ## Login and Enable
 
-This stick does not have a web GUI.
-To configure it, you must log in via `UART` or `Telnet`.
+This stick does not have a web UI.
+To configure it, you must log in via `UART` or `telnet`.
 
-{% include alert.html content="FS.com Stick XGS-ONU-25-20NI does not have PON S/N on the label. (The S/N field stamped on the label is FS.com internal S/N, not PON S/N). In order to get it, you can either ask an FS.com sales representative or check the boot log from the UART!" alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="FS.com Stick XGS-ONU-25-20NI does not have its PON S/N on the label: the S/N field stamped on the label is FS.com's internal S/N, not the PON S/N. In order to obtain the actual PON S/N, either ask an FS.com sales representative or check the boot log from the UART!" alert="Note"  icon="svg-info" color="blue" %}
 
 | User                     | Password (Enable Password)                                  |
 | ------------------------ | ----------------------------------------------------------- |
 | ONU GPON Serial Number   | 8 digit HMAC-MD5 based on Uppercase ONU GPON Serial Number  |
 
-You can use the following form to generate login credentials:
+Use the following form to generate login credentials:
 
 {% include cig_password_xgspon.html password_len="8" %}
 
-Or you can follow this external documentation on how to [emulate the ONT in QEMU](https://github.com/YuukiJapanTech/CA8271x), so use it at your own risk.
+Or follow this external documentation on how to [emulate the ONT in QEMU](https://github.com/YuukiJapanTech/CA8271x), use at your own risk.
 
 UART does not ask for a login, it is possible to get a root shell without knowing the password.
 
 ## Root procedure
-After logging in via `telnet` or `UART`, you will first get the MiniShell with user privileges.
+After logging in via `telnet` or `UART`, you will first access the MiniShell with user privileges:
 ```
 ONT>
 ```
 
-The root MiniShell can be obtained by executing the `enable` command on this MiniShell.
+The root MiniShell can be accessed by executing the `enable` command on this MiniShell:
 ```
 ONT> enable
 #ONT>
 ```
 
-You can then switch to the Linux root shell by executing the following command:
+Switching to the Linux root shell is possible by executing the following command:
 
 ```
 #ONT> system/shell
@@ -164,7 +164,7 @@ You can then switch to the Linux root shell by executing the following command:
 
 # GPON ONU status
 
-## Get the operational status of the ONU
+## Getting the operational status of the ONU
 Check the ONU Registration State with the following command:
 
 ```
@@ -199,8 +199,8 @@ Check the ONU operation state with the following command:
 #ONT>
 ```
 
-## Get information of the OLT vendor
-OLT information can be extracted from the MIB with the following command:
+## Getting OLT vendor information
+OLT information can be extracted from MIB 131 with the following command:
 
 ```
 #ONT>system/mib/show 131
@@ -222,11 +222,11 @@ You can browse the MIB with the following command:
 #ONT/system/mib> 
 ```
 
-### Show a list of MIBs supported by ONT
+### Showing a list of supported MIBs
 
 ```
 #ONT/system/mib> show
-This command prints out the content of a mib table.
+This command prints out the content of a MIB table.
 Usage: show CLASSID
 CLASSID:
       the class ID of the ME, defined in 983.2/984.4, currently
@@ -236,7 +236,7 @@ ClassID  Name            Desc
 etc...
 ```
 
-### Show a specific MIB
+### Showing a specific MIB
 For example, to display MIB 256 (Ont-g):
 
 ```
@@ -261,8 +261,8 @@ OntState                  = 1
 #ONT/system/mib>
 ```
 
-### Dump of a MIB
-Output a dump of mib to `/tmp/mibdump.txt`
+### Dumping a MIB
+Output a dump of MIB to `/tmp/mibdump.txt`
 ```
 #ONT/system/mib> dump
 MIB is saved to the file /tmp/mibdump.txt.
@@ -317,11 +317,11 @@ type            28
 
 
 # GPON/OMCI settings
-XGS-ONU-25-20NI ONT uses `scfg.txt` file and misc command for configuration.
+XGS-ONU-25-20NI ONT uses the `scfg.txt` file and misc command for configuration.
 
 ## Getting/Setting ONU GPON Serial Number
 This setting must be changed with the `misc` CLI option and the `eqsn set "<serialnumber>"` command.
-For example, if the SN is like `GPONabcd1234` (`47504f4eabcd1234`):
+For example, if the desired S/N is `GPONabcd1234` (`47504f4eabcd1234`):
 ```
 #ONT/system/misc> eqsn set "GPONabcd1234"
 ```
@@ -334,7 +334,7 @@ eqsn: GPONabcd1234
 
 ## Getting/Setting ONU GPON PLOAM password
 This setting must be changed with the `misc` CLI option and the `exeep_w8 "<password>"` command.
-For example, if the PLOAM password is like `0123456789`:
+For example, if the desired PLOAM password is `0123456789`:
 ```
 #ONT/system/misc> exeep_w8 "0123456789"
 ```
@@ -363,19 +363,19 @@ The `exeep_r8` command can also be used to retrieve the configured PLOAM passwor
 
 ## Getting/Setting ONU GPON LOID
 This setting must be changed in `scfg.txt`, using the key `CHAR-ARRAY CFG_ID_LOID`. 
-To modify LOID username we add the following line to `/userdata/scfg.txt`:
+To modify the LOID username, add the following line to `/userdata/scfg.txt`:
 ```
 CHAR-ARRAY CFG_ID_LOID = { 0xXX,0xXX,0xXX,0xXX, 0xXX,0xXX,0xXX,0xXX, 0xXX,0xXX,0xXX,0xXX, 0xXX,0xXX,0xXX,0xXX, 0xXX,0xXX,0xXX,0xXX, 0xXX,0xXX,0xXX,0xXX };
 ```
 
-For example, if the LOID is like `0123456`:
+For example, if the desired LOID is `0123456`:
 ```
 CHAR-ARRAY CFG_ID_LOID = { 0x30,0x31,0x32,0x33, 0x34,0x35,0x36,0x00, 0x00,0x00,0x00,0x00, 0x00,0x00,0x00,0x00, 0x00,0x00,0x00,0x00, 0x00,0x00,0x00,0x00 };
 ```
 
 ## Getting/Setting ONU GPON LOID password
 This setting must be changed with the `misc` CLI option and the `pon_passwd set <password>` command.
-For example, if the LOID password is like `0123456789`:
+For example, if the desired LOID password is `0123456789`:
 ```
 #ONT/system/misc> pon_passwd set 0123456789
 ```
@@ -388,7 +388,7 @@ eqsn: 01234567890000000000
 
 ## Getting/Setting OMCI hardware version (ME 256)
 This setting must be changed with the `misc` CLI option and the `eqvid set "<hwver>"` command.
-For example, if the hardware version is like `abc123`:
+For example, if the desired hardware version is `abc123`:
 ```
 #ONT/system/misc> eqvid set "abc123"
 ```
@@ -401,7 +401,7 @@ eqvid: abc123
 
 ## Getting/Setting OMCI vendor ID (ME 256)
 This setting must be changed with the `misc` CLI option and the `vendor set "<vendor>"` command.
-For example, if the vendor is like `GPON`:
+For example, if the desired vendor is `GPON`:
 ```
 #ONT/system/misc> vendor set "GPON"
 ```
@@ -435,14 +435,15 @@ Stick's busybox (Linux shell) supports netcat and TFTP, which allow to send and
 # tftp -r remotefile.bin -g remotehost-ip
 ```
 
-## Backup of all partition
-To obtain a backup, use the `dd` command to save it on `/tmp`,
-or use the `cat` command to transfer it via netcat.
+## Backing up all partitions
+To obtain a backup, use the `dd` command to save it on `/tmp`: 
 ```
 # dd if=/dev/mtdX of=/tmp/mtdX.bin
 # tftp -l /tmp/mtdX.bin -r remotehost-ip
 ```
 
+Or use the `cat` command to transfer it via netcat:
+
 ```
 # cat /dev/mtdX | nc remotehost-ip 10000
 ```
@@ -456,13 +457,13 @@ When partition writing to the stick, use the flash command set.
 
 ## Setting management IP
 To change the management IP, set it with the `misc` CLI option and the `admin_ip set <ip>` command.
-For example, if the management IP is like `192.168.1.1`:
+For example, if the desired management IP is `192.168.1.1`:
 ```
 #ONT/system/misc> admin_ip set 192.168.1.1
 ```
 
 To change the management IP netmask, set it with the `misc` CLI option and the `admin_mask set <netmask>` command.
-For example, if the management IP mask is like `255.255.255.0`:
+For example, if the desired management IP mask is `255.255.255.0`:
 ```
 #ONT/system/misc> admin_mask set 255.255.255.0
 ```
@@ -481,7 +482,7 @@ ERROR: can't get kernel image!
 SATURN#
 ```
 
-Download stick's mtd dump from [mtd dump.](https://github.com/YuukiJapanTech/CA8271x/tree/main/mtd)
+Download the stick's mtd dump from [GitHub.](https://github.com/YuukiJapanTech/CA8271x/tree/main/mtd)
 
 Enable NAND with the following command:
 ```
@@ -505,7 +506,7 @@ SATURN# loadb 0x80000000
 Using Tera Term, send the Kernel image (mtd3 or mtd6) by kermit transfer.
 {% include image.html file="XGS-ONU-25-20NI/Stick_Rep.png" alt="XGS-ONU-25-20NI Repair" caption="XGS-ONU-25-20NI Repair" %}
 
-Erase NAND and write the transferred kernel.
+Erase the NAND and write the transferred kernel.
 ```
 SATURN# spi_nand erase 0x000000600000 0x600000
 SATURN# spi_nand erase 0x000003500000 0x600000
@@ -514,13 +515,13 @@ SATURN# spi_nand write 0x80000000 0x000003500000 0x600000
 ```
 
 Receive the file with the `loadb` command.
-and Using Tera Term, send the rootfs image (mtd4 or mtd7) by kermit transfer.
+Using Tera Term, send the rootfs image (mtd4 or mtd7) by kermit transfer.
 ```
 SATURN# loadb 0x81000000
 ## Ready for binary (kermit) download to 0x81000000 at 115200 bps...
 ```
 
-Erase NAND and write the transferred rootfs.
+Erase the NAND and write the transferred rootfs.
 ```
 SATURN# spi_nand erase 0x000000c00000 0x2800000
 SATURN# spi_nand erase 0x000003b00000 0x2800000
@@ -528,7 +529,7 @@ SATURN# spi_nand write 0x81000000 0x000000c00000 0x2800000
 SATURN# spi_nand write 0x81000000 0x000003b00000 0x2800000
 ```
 
-When the stick is turned back on, it will boot with the transferred kernel and rootfs.
+When the stick turns back on, it will boot with the transferred kernel and rootfs.
 
 
 # Known Bugs
diff --git a/_ont_xgs/ont-hisense-ltf7267-bha+.md b/_ont_xgs/ont-hisense-ltf7267-bha+.md
index c36ffb3..fb85d82 100644
--- a/_ont_xgs/ont-hisense-ltf7267-bha+.md
+++ b/_ont_xgs/ont-hisense-ltf7267-bha+.md
@@ -33,7 +33,7 @@ parent: HiSense
 
 ## Serial
 
-The stick has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. It's near the SFP header. TX, RX and ground pads need to be connected to a USB2TTL adapter supporting a logic level of 3.3V.
+The stick has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. It's near the SFP header. TX, RX and ground pads need to be connected to a USB2TTL adapter supporting 3V3 logic.
 
 {% include image.html file="ont-hisense-ltf7267-bha+_inside.jpg" alt="HiSense LTF7267-BHA+ Internals" caption="HiSense LTF7267-BHA+ Internals" %}
 
@@ -61,11 +61,11 @@ The stick has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be a
 
 This ONT supports dual boot. 
 
-`kernel0` and `rootfs0` respectively contain the kernel and firmware of the first image, `kernel1` and `rootfs1` the kernel and the firmware of the second one
+`kernel0` and `rootfs0` respectively contain the kernel and firmware of the first image, `kernel1` and `rootfs1` the kernel and firmware of the second one.
 
 # XGS-PON ONU status
 
-To access Cortina Shell (needed to check OMCI stuff and XGSPON status) you can use the following command:
+To access Cortina Shell, needed to check OMCI settings and XGSPON status, use the following command:
 
 ```sh
 # app-cli
@@ -73,7 +73,7 @@ To access Cortina Shell (needed to check OMCI stuff and XGSPON status) you can u
 This console can also be reached by opening a telnet connection to `192.168.0.1:2233`
 
 
-## Check Activation Status (from app-cli and telnet\ssh session)
+## Checking Activation Status (from app-cli and telnet\ssh session)
 
 Open two telnet sessions, one to `192.168.0.1` and one to `192.168.0.1:2233`
 
@@ -111,7 +111,7 @@ You will see the following output on the first shell:
 [260436.544953] ^M
 ```
 
-## Show ONT configuration (from app-cli session)
+## Showing ONT configuration (from app-cli session)
 
 ```sh
 Cortina> enable
@@ -163,7 +163,7 @@ XGe Port idx 0 map to Port 6
 ```
 Please note that some of the above fields are decoded incorrectly, such as `sn` and `versionId`
 
-## Get information of the OLT vendor (from app-cli session)
+## Getting OLT vendor information (from app-cli session)
 
 ```sh
 Cortina> enable
@@ -234,7 +234,7 @@ Me: oltG
     No linked ME
 ```
 
-## Check current connection type and configuration (GEM Port+Mac Brige)
+## Checking current connection type and configuration (GEM Port+Mac Brige)
 
 ```sh
 Cortina> enable
@@ -261,7 +261,7 @@ GEM: 1025  | (BI, TCONT:0x101, allocId:1281)
              |--Eth   :0x0301
 ```
 
-## Check VLAN filter 
+## Checking VLAN filter 
 
 ```sh
 Cortina> enable
@@ -298,7 +298,7 @@ Link to PPTP eth: ------->instance 0x301
 # vi /config/scfg.txt
 ```
 
-Append lines below to the file and save it to change Serial Number
+Append the lines provided below to the file and save it to change the PON S/N:
 
 ```
 STRING CFG_ID_PON_VENDOR_ID = SMBS;
@@ -348,9 +348,9 @@ Reboot ONT to apply the change
 
 ### Normal procedure
 
-This ONT seems to be supporting a PLOAM password up to 288 bits in lenghth (36 ASCII characters, 72 Hex digits).
+This ONT seems to support PLOAM passwords up to 288 bits in lenghth (36 ASCII characters, 72 Hex digits).
 
-The PLOAM password is stored into 32 bit chunks (4 ASCII characters / 8 Hex digits), each byte swapped. 
+The PLOAM password is stored into 32 bit chunks (4 ASCII characters / 8 Hex digits), with each chunk being byte-swapped. 
 
 So, starting from the following PLOAM in ASCII format
 
@@ -364,7 +364,7 @@ It gets translated into the following HEX value:
 0x41314232433344344535
 ```
 
-Which is then split into the following blocks (the last block gets padded with 0 to reach 8 digits)
+Which is then split into the following blocks (the last block gets padded with 0 to reach 8 digits):
 
 ```
 BLOCK 0: 0x41314232
@@ -372,7 +372,7 @@ BLOCK 1: 0x43334434
 BLOCK 2: 0x45350000
 ```
 
-Each block is then byte swapped (i.e. read each sequence of two digits from right to left)
+Each block is then byte-swapped (i.e. read each sequence of two digits from right to left):
 
 ```
 BLOCK 0: 0x32423141
@@ -380,13 +380,13 @@ BLOCK 1: 0x34443343
 BLOCK 2: 0x00003545
 ```
 
-And then you can finally persist it by changing the configuration file
+And then you can finally make the change persistent by modifying the configuration file:
 
 ```sh
 # vi /config/scfg.txt
 ```
 
-Append lines below to the file and save it to change the PLOAM password
+Append the lines provided below to the file and save it to change the PLOAM password:
 
 ```
 INT             CFG_ID_PON_REGISTRATION_ID0                                         = 0x32423141;
@@ -413,7 +413,7 @@ CHAR-ARRAY      CFG_ID_LOID
 CHAR-ARRAY      CFG_ID_PASSWD                                                       = {0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0};
 ```
 
-Reboot ONT to apply the change
+Reboot ONT to apply the change.
 
 ## Setting OMCI software version (ME 7)
 
@@ -422,7 +422,7 @@ Reboot ONT to apply the change
 # fw_setenv img_version1 20220527052622
 ```
 
-Reboot ONT to apply the change
+Reboot ONT to apply the change.
 
 ## Setting OMCI hardware version (ME 256)
 
@@ -430,13 +430,13 @@ Reboot ONT to apply the change
 # vi /config/scfg.txt
 ```
 
-Append line below to the file and save it to change HWVER
+Append the line provided below to the file and save it to change HWVER:
 
 ```
 CHAR-ARRAY      CFG_ID_GPON_VERSION = {0x46,0x35,0x36,0x38, 0x34,0x53,0x5f,0x76, 0x31,0x00,0x00,0x00, 0x00,0x00}; ##GPON version string, default value is V1.0
 ```
 
-Reboot ONT to apply the change
+Reboot ONT to apply the change.
 
 ## Setting OMCI equipment ID (ME 257)
 
@@ -444,13 +444,13 @@ Reboot ONT to apply the change
 # vi /config/scfg.txt
 ```
 
-Append the line below to the file and save it to change EQID
+Append the line providede below to the file and save it to change the EQID:
 
 ```
 CHAR-ARRAY      CFG_ID_GPON_EQID = {0x46,0x49,0x42,0x45, 0x52,0x20,0x42,0x6f, 0x78,0x00,0x00,0x00, 0x00,0x00,0x00,0x00, 0x00,0x00,0x00,0x00}; ##GPON ME ONU2G equiment id value, default is saturn
 ```
 
-Reboot ONT to apply the change
+Reboot ONT to apply the change.
 
 # Advanced settings
 
@@ -460,13 +460,13 @@ Reboot ONT to apply the change
 # vi /config/scfg.txt
 ```
 
-Append lines below to the file and save it to change Serial Number
+Append the lines provided below to the file and save it to change Emulation Type:
 
 ```
 STRING          CFG_ID_PON_OLT_TYPE                             = ALCL; ##GPON OLT Vendor name, support ZTE,ADTRAN,ALCL,CALIX,SUMITOMO,CORTINA,HUAWEI
 ```
 
-Reboot ONT to apply the change
+Reboot ONT to apply the change.
 
 ## Changing OMCC Version
 
@@ -475,16 +475,16 @@ Reboot ONT to apply the change
 # vi /config/scfg.txt
 ```
 
-Append the line below to the file and save it to change Serial Number
+Append the line provided below to the file and save it to change OMCC Version:
 
 ```
 CHAR            CFG_ID_OMCC_VERSION                             = 0xB2;
 ```
 
-Reboot ONT to apply the change
+Reboot ONT to apply the change.
 
 
 # Known Bugs
-- `ALCL` OLT mode uses some static configurations on MIBs, so if your OLT has strict configuration checks it might not work properly
-- During initial tests the only currently working mode of the stick is `PPTP EthUni`
-- Stick can be configured also emulate `VEIP` mode(adding it to the scfg.txt file), but current firmware doesn't link correctly the XGBE interface, so no traffic is passing between LAN and PON interfaces
+- `ALCL` OLT mode uses some static configurations on MIBs, so if your OLT has strict configuration checks it might not work properly.
+- During initial tests the only currently working mode of the stick is `PPTP EthUni`.
+- Stick can be configured to also emulate `VEIP` mode (adding it to the scfg.txt file), but the current firmware doesn't link correctly the XGBE interface, so no traffic is passing between LAN and PON interfaces.
diff --git a/_ont_xgs/ont-huawei-useful-command.md b/_ont_xgs/ont-huawei-useful-command.md
index 4f0e91c..e403050 100644
--- a/_ont_xgs/ont-huawei-useful-command.md
+++ b/_ont_xgs/ont-huawei-useful-command.md
@@ -1,8 +1,8 @@
 ## Enabling telnet
 
-We need access to a specific shell and in order to get it we have to enable telnet. On the unit, the telnet server accepts connections but doesn't read any input, nor does it send anything.
+We need access to a specific shell and in order to get it enabling telnet is required. On the ONT, the telnet server accepts connections but doesn't read any input, nor does it send anything.
 
-To enable telnet we’ll use one of the web interface’s features: the configuration backup and restore page. The configuration can be downloaded as an XML, which contains a lot more options than the web interface and a couple of them can be modified to enable telnet access: under the `X_HW_CLITelnetAccess` node, set the `Access` attribute to `1` and in `AclServices`, `TELNETLanEnable` should also be set to `1`. I had to set both but your mileage may vary.
+To enable telnet the configuration backup/restore web UI page will be used. The configuration can be downloaded as an XML, which contains a lot more options than the web interface and a couple of them can be modified to enable telnet access: under the `X_HW_CLITelnetAccess` node, set the `Access` attribute to `1` and, in `AclServices`, `TELNETLanEnable` should also be set to `1`. Both might have to be set but your mileage may vary.
 
 It is possible that this won't work/has been fixed in more recent versions.
 
diff --git a/_ont_xgs/ont-nokia-useful-command.md b/_ont_xgs/ont-nokia-useful-command.md
index c5af085..411335d 100644
--- a/_ont_xgs/ont-nokia-useful-command.md
+++ b/_ont_xgs/ont-nokia-useful-command.md
@@ -1,6 +1,6 @@
 # GPON ONU status
 
-## Get the operational status of the ONU
+## Getting the operational status of the ONU
 ```sh
 #ONT>traffic
 #ONT/system>pon
@@ -73,7 +73,6 @@ pon_passwd: 31323334353637383900
 ```
 
 ## Setting OMCI software version (ME 7)
-The following must be typed from the standard linux shell:
 ```sh
 # echo SWVER=3FE49337AOCK80 > /mnt/rwdir/sys.cfg
 ```
diff --git a/_ont_xgs/ont-nokia-xs-010x-q.md b/_ont_xgs/ont-nokia-xs-010x-q.md
index d2dd9dd..bb18aa2 100644
--- a/_ont_xgs/ont-nokia-xs-010x-q.md
+++ b/_ont_xgs/ont-nokia-xs-010x-q.md
@@ -42,7 +42,7 @@ parent: Nokia
 
 ## Serial
 
-The ONT has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. It's on the top left (with Ethernet\Power\Optical port faced down) of the board. TX, RX and ground pads need to be connected to a USB2TTL adapter supporting a logic level of 3.3V.
+The ONT has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface: it's on the top left of the board, when the Ethernet\Power\Optical ports are facing down. TX, RX and ground pads need to be connected to a USB2TTL adapter supporting 3V3 logic.
 
 {% include image.html file="ont-nokia_xs-010x-q_ttl.jpg" alt="Nokia XS-010X-Q TTL Pads" caption="Nokia XS-010X-Q TTL Pads" %}
 
@@ -73,7 +73,7 @@ The ONT has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be acc
 
 This ONT supports dual boot. 
 
-`kernel0` and `rootfs0` respectively contain the kernel and firmware of the first image, `kernel1` and `rootfs1` the kernel and the firmware of the second one
+`kernel0` and `rootfs0` respectively contain the kernel and firmware of the first image, `kernel1` and `rootfs1` the kernel and firmware of the second one.
 
 {% include_relative ont-nokia-use.md %}
 
@@ -81,11 +81,9 @@ This ONT supports dual boot.
 
 ## Enable SSH (not persistent)
 
-Port 22 is filtered by default and the SSH daemon can be only enabled in runtime. Here is the procedure but it's not persisten accross reboot:
+Port 22 is filtered by default and the SSH daemon can be only enabled in runtime. Here is the procedure but it's not persistent and will need to be done again after each reboot:
 
-Access UART with `ONTUSER`
-
-Enter `system\misc`
+Access UART with `ONTUSER`, then enter `system\misc`.
 
 Set `ssh_en` to `1` with the command:
 ```sh
@@ -103,14 +101,12 @@ Go back to `system`, then `shell` and run this command:
 ```
 ## Enable Telnet Full Shell
 
-When you're using default credentials to access telnet (`admin`\\`1234`), the prompt is limited to `GponSLID` shell that permits only to modify or display the `PLOAM`
-If you change the `admin_mask` to `255.255.255.255`, default credentials stop to work but you can logon with `ONTUSER` and generated password to have full shell like UART
+When using the default credentials to access telnet (`admin`\\`1234`), the prompt is limited to the `GponSLID` shell that only permits modifying or displaying the `PLOAM` password.
+If you change the `admin_mask` to `255.255.255.255`, default credentials stop working but you can login as `ONTUSER` using the generated password to have full shell like when using UART.
 
 Here is the procedure to change `admin_mask`:
 
-Access UART with `ONTUSER`
-
-Enter `system\misc`
+Access UART with `ONTUSER`, then enter `system\misc`.
 
 Set `admin_mask` to `255.255.255.255` with the command:
 ```sh
diff --git a/_ont_xgs/ont-zte-f2801s.md b/_ont_xgs/ont-zte-f2801s.md
index 8ecbab9..cde218a 100644
--- a/_ont_xgs/ont-zte-f2801s.md
+++ b/_ont_xgs/ont-zte-f2801s.md
@@ -54,16 +54,16 @@ parent: ZTE
 
 
 This ONT supports dual boot, as visible from the presence of `kernel1` and `kernel2`, which contain the rootfs.
-The boot image can be swapped with the following command:
+The boot images can be swapped with the following command:
 
 ```sh
 upgradetest switchver X
 ```
 
-Where `X` can be `0/1` based on the image you want to boot.
+Where `X` can be `0/1`, based on the image you want to boot from.
 
 
-You can also clone the currently running image into other slot using this command:
+You can also clone the currently running image into the other slot using this command:
 
 ```sh
 syn_version
@@ -73,7 +73,7 @@ syn_version
 {% include alert.html content="Commands have been tested on V2 HW rev. on OpenFiber firmwares" alert="Note"  icon="svg-info" color="blue" %}
 
 ## Enable Telnet
-{% include alert.html content="This is an external script ([ZTE Telnet enabled](https://github.com/douniwan5788/zte_modem_tools)), so use it at your own risk! Credential doesn't survive at reboot!" alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="This is an external script ([ZTE Telnet enabler](https://github.com/douniwan5788/zte_modem_tools)), use at your own risk! Credentials don't survive at reboot!" alert="Note"  icon="svg-info" color="blue" %}
 
 ```sh
 python3 zte_factroymode.py --user admin --pass admin --ip 192.168.1.1 --port 80 telnet open
@@ -108,7 +108,7 @@ Password: Eqb8X8Qt
 
 ## Enable console redirection
 
-To see omcidebug messages on Telnet you need to execute this command (just the first time of each connection):
+To see omcidebug messages on telnet, execute this command (just the first time of each connection):
 
 ```sh
 redir printf
@@ -116,21 +116,21 @@ redir printf
 
 # GPON ONU status
 
-## Get the operational status of the ONU
+## Getting the operational status of the ONU
 
-To see the connection state use the following command:
+To check the connection status use the following command:
 ```
 gpontest -gstate
 ```
 `[gpontest] gpon state is [O5]` for O5 state
 
-## Get information of the OLT vendor
+## Getting  OLT vendor information
 
 ```sh
 sendcmd 132 omcidebug showmedata 131
 ```
 
-This command will print out the result like this one:
+This command will print the following output:
 
 ```sh
 ##################################
@@ -156,7 +156,7 @@ MIB INFO:
 sendcmd 132 omcidebug showmedata ID_MIB (eg. 7 for Firmware version)
 ```
 
-This command will print out a result like this one:
+This command will print the following output:
 
 ```sh
 
@@ -184,7 +184,7 @@ MIB INFO:
 
 ## Setting ONU GPON Serial Number
 
-{% include alert.html content="You have to change S/N and the VID. 2176 is for the VID (first 4 letters of the S/N) and 2177 is for the last 8 digits of the S/N" alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="Both S/N and VID have to be changed. 2176 is for the VID (first 4 letters of the S/N) and 2177 is for the last 8 digits of the S/N" alert="Note"  icon="svg-info" color="blue" %}
 ```sh
 setmac 1 2176 ZTEG
 setmac 1 2177 AABBCCDD
@@ -193,7 +193,7 @@ setmac 1 2177 AABBCCDD
 ## Setting ONU GPON PLOAM password
 
 {% include alert.html content="The PLOAM password is stored in the ASCII format." alert="Note"  icon="svg-info" color="blue" %}
-This can be done easily via web ui. If you prefer to do it via the shell use:
+This can be done easily via the web UI. To do it via the shell use:
 ```sh
 setmac 1 2181 1234567890
 setmac 1 2178 1234567890
@@ -201,17 +201,17 @@ setmac 1 2178 1234567890
 
 # Advanced settings
 
-## Backup ONT Paritions for HW\SW Version Mod
+## Backing up ONT Paritions for HW/SW Version Mod
 
 This step is suggested if you want to replace firmware on your ONT to spoof HW and SW version:
 
 Needed tools:
 
 - Linux VM or WSL with Python >3.3
-- [ZTE Telnet enabled](https://github.com/douniwan5788/zte_modem_tools)
+- [ZTE Telnet enabler](https://github.com/douniwan5788/zte_modem_tools)
 - TFTP server
 
-First step is to login over telnet with `zte_factroymode.py` then execute ALL this command for a full backup:
+The first step is to login over telnet with `zte_factroymode.py`, then execute ALL these commands for a full backup:
 
 **Go to `/tmp` folder to create tmp files**
 
@@ -221,7 +221,7 @@ cd /tmp
 
 **Dump and transfer all mtd **
 
-Here 192.168.1.2 is the IP of the machine running the TFTP server, change it as needed
+In the following commands, 192.168.1.2 is the IP of the machine running the TFTP server, change it as needed.
 
 ```sh
 cat /dev/mtd1 > u-boot.bin && tftp -l u-boot.bin -r u-boot.bin -p 192.168.1.2 && rm u-boot.bin
@@ -236,7 +236,7 @@ cat /dev/mtd9 > rootfs.bin && tftp -l rootfs.bin -r rootfs.bin -p 192.168.1.2 &&
 
 ```
 
-## Change region code
+## Changing region code
 
 {% include alert.html content="Be aware that changing the region code may break features such as PPPoE depending on your ISP" alert="Note"  icon="svg-info" color="blue" %}
 
@@ -260,7 +260,7 @@ Where X is the number of supported regioncode into file `/etc/init.d/regioncode`
 ```
 
 # Random notes
-- F2801S reads the software version exposed thru gpon_omci deamon from each kernel partition's header, so only way to spoof this parameter is to change the version in the header and recalculate CRC, otherwise bootloader refuse to load image
+- The F2801S reads the software version exposed through the gpon_omci deamon from each kernel partition header, so the only way to spoof this parameter is to change the version in the header and recalculate CRC, otherwise the bootloader will refuse to load the image
 
 # Miscellaneous Links