23 files changed, 130 insertions, 128 deletions
diff --git a/_gpon/gpon-auth.md b/_gpon/gpon-auth.md
index e4ec6ba..c2a84fe 100644
--- a/_gpon/gpon-auth.md
+++ b/_gpon/gpon-auth.md
@@ -38,9 +38,9 @@ graph TD
 
 # Fake O5 Status
 
-This known issue with Alcatel/Nokia OLT giving fake `O5` ONU Status, OLT will hold OMCI Provisioning until correct OMCI Information
+There is a known issue with Alcatel/Nokia OLTs giving fake `O5` ONU Status, OLTs will hold OMCI Provisioning until correct OMCI Information is received.
 
-It happens when the OLT detects that the ONT is `drunk`. And try to update the firmware before opening the GEM link. One must try to change the software version or other data.
+It happens when the OLT detects that the ONT is `drunk`, so it tries to update the firmware before opening the GEM link. If this happens, the user has to try changing the software version or other data.
 
 - [The Process for an ONU to go Online](https://forum.huawei.com/enterprise/en/the-process-for-an-onu-to-go-online-gpon-technical-posts-12/thread/462895-100181)
 - [What’s the Authentication of GPON](http://zhangjorna.blogspot.com/2016/05/whats-authentication-of-gpon.html)
diff --git a/_gpon/ont.md b/_gpon/ont.md
index f6bcd7a..98471fe 100644
--- a/_gpon/ont.md
+++ b/_gpon/ont.md
@@ -9,7 +9,7 @@ layout: default
 
 # Major Chipset Manufacturers
 
-Currently, there are ony two main GPON chipsets vendors:
+Currently, there are only two main GPON chipset vendors:
 
 - Realtek manufactures these chipsets:
     * RTL9601B  
@@ -21,12 +21,12 @@ Currently, there are ony two main GPON chipsets vendors:
 
 ## Realtek Chipsets
 
-HSGMII chipsets are relatively recent, starting from 2020, and are used in many ONTs. Realtek offers an official SDK, Luna SDK, which offers very good performance in queue management, unfortunately it is not used by all devices based on these chipsets.
+HSGMII chipsets are relatively recent, they became more common starting in 2020, and are used in many ONTs. Realtek offers an official SDK, Luna SDK, which offers very good performance in queue management, unfortunately it is not used by all devices based on these chipsets.
 
 ## Lantiq Chipsets
 
 Unfortunately Lantiq no longer exists as it has been bought out and dismembered by Intel. This purchase was a huge deal as at the time Lantiq was at the forefront of the GPON and xDSL chipset market.
-The GPON part of Lantiq ended up in `/dev/null`, while the XGS-PON sector ended up in the hands of MaxLinear and the whole Wi-Fi part remained in the hands Intel itself.
+The GPON part of Lantiq ended up in `/dev/null`, while the XGS-PON sector ended up in the hands of MaxLinear and the whole Wi-Fi part remained in the hands of Intel itself.
 
 The last produced batches of these SFPs date back to 2020/2021. All OEMs are currently migrating to Realtek.
 
diff --git a/_gpon/vendor.md b/_gpon/vendor.md
index 2a68b1f..7e7eeb1 100644
--- a/_gpon/vendor.md
+++ b/_gpon/vendor.md
@@ -7,9 +7,9 @@ layout: default
 
 > 4 ASCII character maximum
 
-Need to set for OLT Authenticate your ONT stick, please read your original ONT Serial Number, either in HEX digit or ASCII, if in HEX digit, you need convert first eight HEX digit to ASCII, for example `48575443` = `HWTC`.
+Needs to be set for the OLT to authenticate your ONT; please read your original ONT's Serial Number, it can be either in HEX or ASCII: if it's codified in HEX, you need to convert the first eight HEX digits to ASCII, for example `48575443` = `HWTC`.
 
-Here some popular list if want to fool the OLT:
+Here is a list of the most popular Vendor IDs:
 
 
 | ID     | Vendor Name          |
diff --git a/_ont/ont-fs-com-gpon-onu-stick-with-mac.md b/_ont/ont-fs-com-gpon-onu-stick-with-mac.md
index 966fbf1..8784290 100644
--- a/_ont/ont-fs-com-gpon-onu-stick-with-mac.md
+++ b/_ont/ont-fs-com-gpon-onu-stick-with-mac.md
@@ -63,7 +63,7 @@ Or:
 sfp_i2c -i8 -s "ABCD12345678"
 ```
 
-## Obtain S/N setted
+## Checking whether the S/N has been correctly set
 ```sh
 fw_printenv | grep nSerial
 ```
@@ -73,7 +73,7 @@ sfp_i2c -g
 ```
 
 ## Setting PLOAM Password
-Software 6BA1896SPLQA41 and before (See [Carlito Firmware](/ont-huawei-ma5671a-carlito))
+Software 6BA1896SPLQA41 and earlier (See [Carlito Firmware](/ont-huawei-ma5671a-carlito))
 ```sh
 fw_setenv nPassword "0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39"
 ```
@@ -84,7 +84,7 @@ sfp_i2c -i11 -s "0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39"
 ```
 
 ## Setting LOID and Checkcode Password
-Software 6BA1896SPLQA41 and before (See [Carlito Firmware](/ont-huawei-ma5671a-carlito))
+Software 6BA1896SPLQA41 and earlier (See [Carlito Firmware](/ont-huawei-ma5671a-carlito))
 ```sh
 fw_setenv omci_loid 1234567890
 fw_setenv omci_lpwd password01
@@ -96,23 +96,23 @@ sfp_i2c -i9 -s "1234567890"
 sfp_i2c -i10 -s "password01"
 ```
 
-## Setting eqipment id (ME 257)
+## Setting Eqipment ID (ME 257)
 ```sh
 sfp_i2c -i6 -s "YOUR_EQUIPMENT_ID"
 ```
 
-## Setting vendor id (ME 256)
+## Setting Vendor ID (ME 256)
 ```sh
 sfp_i2c -i7 -s "YOUR_VENDOR_ID"
 ```
 
-## Change ONU hardware version (ME 256)
+## Changing ONU hardware version (ME 256)
 ```sh
 cp /etc/mibs/data_1g_8q.ini /etc/mibs/data_1g_8q.ini.bak
 sed 's/256 0 HWTC 0000000000000/256 0 YOUR_VENDOR_ID YOUR_ONU_VERSION/' -i /etc/mibs/data_1g_8q.ini
 ```
 
-## Enable `data_1g_8q_us1280_ds512.ini` OMCI MIB file for 2500 Mbps profiles
+## Enabling `data_1g_8q_us1280_ds512.ini` OMCI MIB file for 2500 Mbps profiles
 {% include alert.html content="The patch below is only compatible with the firmware version `6BA1896SPLQA42`" alert="Info" icon="svg-info" color="blue" %}
 {% include alert.html content="If you need to set the ONU version remember that you will have to do it using the MIB file `/etc/mibs/data_1g_8q_us1280_ds512.ini` instead of `/etc/mibs/data_1g_8q.ini`" alert="Info" icon="svg-info" color="blue" %}
 
@@ -121,7 +121,7 @@ The MIB file `data_1g_8q_us1280_ds512.ini` is very useful to avoid performance p
 fw_setenv mib_file data_1g_8q_us1280_ds512.ini
 ```
 
-## Use custom OMCI MIB file
+## Using custom OMCI MIB file
 {% include alert.html content="If you need to set the ONU version remember that you will have to do it using your custom MIB file instead of `/etc/mibs/data_1g_8q.ini`" alert="Info" icon="svg-info" color="blue" %}
 
 You have to copy the MIB file to /etc/mibs and then run this command:
@@ -129,7 +129,7 @@ You have to copy the MIB file to /etc/mibs and then run this command:
 fw_setenv mib_file YOUR_MIB_FILENAME
 ```
 
-## Change image software version (ME 7)
+## Changing image software version (ME 7)
 {% include alert.html content="The patch below is only compatible with the firmware version `6BA1896SPLQA42`" alert="Info" icon="svg-info" color="blue" %}
 
 The image version normally couldn't be changed because it was hard-coded into the `/opt/lantiq/bin/omcid` binary, 
@@ -167,12 +167,13 @@ cd /opt/lantiq/bin
 cp omcid omcid.original
 ```
 
-And finally to copy via SCP the modified `omcid` binary in the `/opt/lantiq/bin/omcid` path.
-Before restarting the stick and applying changes, make sure omcid has execution bit set.
+Now you have to use SCP to copy the modified `omcid` binary in `/opt/lantiq/bin/omcid`.
+Before restarting the stick and applying changes, make sure `omcid` has its execution bit set, then reboot the stick and change the image version with the following command:
 
 ```sh
 chmod ugo+x /opt/lantiq/bin/omcid
-```
+>>>>>>> main
+
 
 Is also a good time to set the image0/image1_version. Crash has reported if they are not set correctly before reboot.
 ```sh
@@ -197,33 +198,33 @@ fw_setenv ipaddr 192.168.20.60
 fw_setenv gatewayip 192.168.20.1
 ```
 
-## Read all EEPROM
+## Reading all EEPROM
 ```sh
 sfp_i2c -r
 ```
 
-## Get Firmware version
+## Getting Firmware version
 ```sh
 strings /opt/lantiq/bin/omcid | grep ^software_Version | awk -F[=,] '{print $2}'
 ```
 
-## Get Firmware build time
+## Getting Firmware build time
 ```sh
 strings /opt/lantiq/bin/omcid | grep compiled
 ```
 
-## Setting Onu reboot
+## Rebooting the ONU
 ```sh
 reboot
 ```
 
-## Reinitialize the EEPROM without rebooting 
+## Reinitializing the EEPROM without rebooting 
 {% include alert.html content="This will cause you to disconnect from the current ssh session."  alert="Warning"  icon="svg-warning" color="yellow" %}
 ```sh
 reload_i2c.sh
 ```
 
-## Reset EEPROM to default values and reinitialize 
+## Resetting EEPROM to default values and reinitializing 
 {% include alert.html content="This command is not reversible, all the EEPROM data will be restored to the factory values!"  alert="Warning"  icon="svg-warning" color="red" %}
 {% include alert.html content="This will cause you to disconnect from the current ssh session."  alert="Warning"  icon="svg-warning" color="yellow" %}
 ```sh
diff --git a/_ont/ont-huawei-hg8010h.md b/_ont/ont-huawei-hg8010h.md
index 31b4418..64a872c 100644
--- a/_ont/ont-huawei-hg8010h.md
+++ b/_ont/ont-huawei-hg8010h.md
@@ -33,9 +33,9 @@ parent: Huawei
 
 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.
 
-To enable telnet we’ll use one of the web interface’s feature: the configuration backup and restore page. The configuration can be downloaded as XML, an XML file that 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 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. 
 
-It is possible that in more recent versions this won't work/has been fixed.
+It is possible that this won't work/has been fixed in more recent versions.
 
 Now that this is done, the modified configuration file can be uploaded via the web interface, the ONT will restart and telnet should be accessible on port 23.
 
@@ -69,7 +69,7 @@ Now that this is done, the modified configuration file can be uploaded via the w
 ## List of useful commands
 
 > **Warning**  
-> All results need to be converted from Hex to Ascii  
+> All results need to be converted from HEX to ASCII  
 > [Converter](/ascii-hex)
 
 - Get OLT information:
diff --git a/_ont/ont-huawei-ma5671a-carlito.md b/_ont/ont-huawei-ma5671a-carlito.md
index 8f0247b..36ae772 100644
--- a/_ont/ont-huawei-ma5671a-carlito.md
+++ b/_ont/ont-huawei-ma5671a-carlito.md
@@ -7,7 +7,7 @@ layout: default
 
 # General setting
 
-{% include alert.html content="Be careful, back up the goi_config from ubot before changing firmware." alert="Info" icon="svg-info" color="blue" %}
+{% include alert.html content="Be careful, back up the goi_config from uboot before changing firmware." alert="Info" icon="svg-info" color="blue" %}
 
 ## Setting image version
 ```sh
@@ -42,13 +42,13 @@ fw_setenv omci_lpwd password01
 ```
 If LOID is disabled in the firmware try alternative software.
 
-## Setting and check oem-generic
+## Setting and checking oem-generic
 ```sh
 fw_setenv target oem-generic
 fw_printenv target=oem-generic
 ```
 
-## Setting HSMIII
+## Setting HSGMII Mode
 ```sh
 fw_setenv sgmii_mode 5
 ```
 \ No newline at end of file
diff --git a/_ont/ont-huawei-ma5671a-china.md b/_ont/ont-huawei-ma5671a-china.md
index c00fb6d..ddbfb18 100644
--- a/_ont/ont-huawei-ma5671a-china.md
+++ b/_ont/ont-huawei-ma5671a-china.md
@@ -7,9 +7,9 @@ parent: Huawei MA5671A
 
 # General setting
 
-{% include alert.html content="Be careful, use this firmware only if you have performance problems with all other firmware." alert="Info" icon="svg-info" color="blue" %}
+{% include alert.html content="Be careful, use this firmware only if you have performance problems with all other firmwares." alert="Info" icon="svg-info" color="blue" %}
 
-{% include alert.html content="Do not use translator on the browser, use a translation app on the phone through virtual reality." alert="Danger" icon="svg-warning" color="red" %}
+{% include alert.html content="Do not use in-browser translators, use a translation app on your phone through virtual reality." alert="Danger" icon="svg-warning" color="red" %}
 
 1. Flash on the 0 partition
 
@@ -25,6 +25,6 @@ jffs2reset
 
 5. Reboot
 
-6. Edit the incorrect data and make save and apply from pending changes
+6. Edit the incorrect data, save and apply the pending changes
 
 7. Reboot
 \ No newline at end of file
diff --git a/_ont/ont-huawei-ma5671a-root.md b/_ont/ont-huawei-ma5671a-root.md
index 894828b..c8e9b73 100644
--- a/_ont/ont-huawei-ma5671a-root.md
+++ b/_ont/ont-huawei-ma5671a-root.md
@@ -5,7 +5,7 @@ parent: Huawei MA5671A
 layout: default
 ---
 
-1. Take the SFP molex and the 4 coloured cables and solder them to the molex according to the following diagram:
+1. Take the SFP molex and four coloured cables and solder them to the molex according to the following diagram:
 
 | USB TTL(UART) Adapter | wire colour in picture | SFP 20pins Molex connector |
 | --------------------- | ---------------------- | -------------------------- |
@@ -14,25 +14,25 @@ layout: default
 | RX                    | yellow                 | pin #7                     |
 | GND                   | green                  | pin #14                    |
 
-{% include alert.html content="Use GND wire as ON/OFF switch, otherwise there will be a slight delay before data is displayed on the console (putty/TeraTerm)." alert="Important"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Use the GND wire as an ON/OFF switch, otherwise there will be a slight delay before data is displayed on the console (putty/TeraTerm)." alert="Important"  icon="svg-warning" color="yellow" %}
 
-{% include alert.html content="Try PIN 10 or other GND PINs if it doesn't work with 14." alert="Note"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Try PIN 10 or other GND PINs if the connection doesn't work with PIN 14." alert="Note"  icon="svg-warning" color="yellow" %}
 
-{% include alert.html content="Some USB TTL adapters label TX and RX pins the other way around: try to swap them if it doesn't work." alert="Note"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Some USB TTL adapters label TX and RX pins the other way around: try to swap them if the connection doesn't work." alert="Note"  icon="svg-warning" color="yellow" %}
 
 {:style="counter-reset:none"}
 1. Install python and `pyserial` with `pip`
 ```shell
 pip install pyserial
 ```
-1. Make the connections as shown to a TTL adapter except for GND (which remains detached and is used as a switch)
+1. Make the connections as shown to a TTL adapter except for GND (which should remain detached as it is used as a switch)
 
 {% include image.html file="ma5671a-root-1.jpg"  alt="Example of how the sfp-ttl connection should look like" caption="Example of how the sfp-ttl connection should look like" %}
 {% include image.html file="new-root-procedure\board-molex-arduino.jpg"  alt="Example of how the sfp-ttl connection should look like with a custom board" caption="Example of how the sfp-ttl connection should look like with a custom board" %}
-{% include image.html file="ma5671a-root-2.jpg"  alt="Molex SFP" caption="Molex SFP" %}
+{% include image.html file="ma5671a-root-2.jpg"  alt="SFP Molex" caption="SFP Molex" %}
 
 {:style="counter-reset:none"}
-1. Open Tera Term (or other serial terminal emulator), find the correct serial port of the TTL adapter, change the port on the script on line 7 instead of `COM8`.
+1. Open Tera Term (or other serial terminal emulators), find the correct serial port of the TTL adapter, change the port on the script on line 7 instead of `COM8`.
 1. After this, run the following python script and connect the GND pin:
 
 ```py
@@ -92,19 +92,19 @@ except (KeyboardInterrupt, SystemExit):
 
 {:style="counter-reset:none"}
 1. Reboot the stick
-1. Open Tera Term (or other serial terminal emulator), after load press `enter` to activate the console
+1. Open Tera Term (or other serial terminal emulators), after it has loaded press `enter` to activate the console
 
-{% include image.html file="new-root-procedure\press-enter.jpg"  alt="Press enter for activate the console" caption="Press enter for activate the console" %}
+{% include image.html file="new-root-procedure\press-enter.jpg"  alt="Press enter to activate the console" caption="Press enter to activate the console" %}
 
 {:style="counter-reset:none"}
-1. With `sed` change the default shell from `/opt/lantiq/bin/minishell` to `/bin/ash` the file `/etc/passwd`:
+1. With `sed` change the default shell from `/opt/lantiq/bin/minishell` to `/bin/ash` by editing the file `/etc/passwd`:
 
 ```shell
 sed -i  "s|/opt/lantiq/bin/minishell|/bin/ash|g" /etc/passwd
 ```
 {% include alert.html content="Do not use `vim`!" alert="Important" icon="svg-warning" color="red" %}
 
-{% include alert.html content="Take attention to kernel panics, they happen often! Be quick, if a kernel panic happens wait for the reboot and try again." alert="Important"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Be aware that kernel panics happen often! If a kernel panic happens wait for the reboot and quickly try again." alert="Important"  icon="svg-warning" color="yellow" %}
 
 
 ```shell
@@ -112,14 +112,14 @@ sed -i  "s|/opt/lantiq/bin/minishell|/bin/ash|g" /etc/passwd
 [   34.612000] Rebooting in 3 seconds..
 ```
 
-{% include alert.html content="The cause of these kernel panics could be insufficient power supply." alert="Info"  icon="svg-info" color="blue" %}
+{% include alert.html content="The cause of these kernel panics could be insufficient supply of power." alert="Info"  icon="svg-info" color="blue" %}
 
 {:style="counter-reset:none"}
-1. Reboot it this time connected to the router with cage or mediaconverter, with the port set to an IP on the 192.168.1.0/24 subnet (the stick has the IP 192.168.1.10)
+1. After this is done, reboot the stick, after connecting it to the router via an ethernet mediaconverter or directly plug it in in an SFP port, with the port's IP set to whatever IP of the 192.168.1.0/24 subnet (the stick has the IP 192.168.1.10)
 
 {% include alert.html content="If your subnet is 192.168.1.0/24 make sure you have no ip conflicts." alert="Note"  icon="svg-warning" color="yellow" %}
 
-{% include alert.html content="Be sure to disable SFP TX fault detection otherwise the RX loss will prevent you from connecting to the mini SFP ONT at this point. Don't simply attach the fiber optic to work it around or you OLT may ban you." alert="Note"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Make sure to disable SFP TX fault detection, otherwise the RX loss will prevent you from connecting to the mini SFP ONT at this point. Don't simply attach the fiber cable to work around this issue as the OLT may ban you." alert="Note"  icon="svg-warning" color="yellow" %}
 
 {:style="counter-reset:none"}
 1. Run the terminal and login to the stick with ssh
diff --git a/_ont/ont-huawei-ma5671a-rooted.md b/_ont/ont-huawei-ma5671a-rooted.md
index a4a6d14..76fb93e 100644
--- a/_ont/ont-huawei-ma5671a-rooted.md
+++ b/_ont/ont-huawei-ma5671a-rooted.md
@@ -8,7 +8,7 @@ layout: default
 # General setting
 
 
-{% include alert.html content="Unlike the other firmware in this firmware, the data must be modified in a base64-encoded file. To simplify this, you can use the following web application." alert="Info" icon="svg-info" color="blue" %}
+{% include alert.html content="In this firmware, unlike the other ones, the data must be modified in a base64-encoded file. To simplify this, you can use the following web application." alert="Info" icon="svg-info" color="blue" %}
 
 ## Web procedure
 
@@ -107,7 +107,7 @@ fw_setenv sfp_a2_info "<output>"
 
 ## Temporary file procedure
 
-1. Save `sfp_a2_info` in into temporary file
+1. Save `sfp_a2_info` in a temporary file
 
 ```shell
 fw_printenv sfp_a2_info | sed "s/^sfp_a2_info=//" > /tmp/sfp_a2.txt
@@ -119,41 +119,41 @@ fw_printenv sfp_a2_info | sed "s/^sfp_a2_info=//" | tr '@' '\n'
 
 2. Setting S/N
 
-The S/N is stored on the 6th line, for sample `4857544311223344` (where `48575443` are hex encoding of `HWTC`) are stored:
+The S/N is stored on the 6th line, for example `4857544311223344` (where `48575443` is the HEX encoding of `HWTC`):
 ```
 AAAAAAAAAAJIV1RDESIzRP///////////////////wAAAAAAAAAAAAAAAAAA
 00000000000000024857544311223344ffffffffffffffffffffffffffffff0000000000000000000000000000
 ```
 
-The entire S/N, including the PON ID, is encoded first in hex and then in base64
+The entire S/N, including the PON ID, is encoded first in hexadecimal and then in base64
 
-3. Setting Ploam Password
+3. Setting PLOAM Password
 
-The Ploam Password is stored on the 5th line, for sample (`1234567890`) are stored:
+The PLOAM Password is stored on the 5th line, for example (`1234567890`):
 ```
 ffffffffffffffff00021437d77db7df7e37e77eb7ef7f37f77d00000000000000000000000000000000000000
 //////////8AAhQ31323334353637383930AAAAAAAAAAAAAAAAAAAAAAAAA
 ```
 
-The entire Ploam, is encoded first in hex and then in base64
+The entire PLOAM, is encoded first in hexadecimal and then in base64
 
 4. Setting MAC Address
 
-The Ploam Password is stored on the 9th line, for sample (`48:57:02:da:be:ef`) are stored:
+The MAC Address is stored on the 9th line, for example (`48:57:02:da:be:ef`):
 ```
 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASFcC2r7vAAAAAAAAAAAAAAAAAAAA
 000000000000000000000000000000000000000000000000485702dabeef000000000000000000000000000000
 ```
 
-5. Transfer modified file back into variable `sfp_a2_info`
+5. Transfer the modified file back into variable `sfp_a2_info`
 
 ```shell
 fw_setenv sfp_a2_info $(cat /tmp/sfp_a2.txt)
 ```
 
-## Review and testing
+## Reviewing and testing
 
-After reboot I check for new variables:
+After rebooting, check whether the new variables have been saved correctly:
 
 ```shell
 fw_printenv nPassword
@@ -161,15 +161,13 @@ fw_printenv gSerial
 fw_printenv ethaddr
 ```
 
-After reboot I check for new variables:
-
-## Check registration status for O5 (successful)
+## Checking whether the connection with the OLT was successful (O5 state)
 
 ```shell
 onu ploamsg
 ```
 
-# Disable dying gasp
+# Disabling dying gasp
 
 ```shell
 fw_setenv nDyingGaspEnable 0 
diff --git a/_ont/ont-huawei-ma5671a.md b/_ont/ont-huawei-ma5671a.md
index d8c37c8..e7fb530 100644
--- a/_ont/ont-huawei-ma5671a.md
+++ b/_ont/ont-huawei-ma5671a.md
@@ -45,9 +45,9 @@ parent: Huawei
 
 Configuration: asc0=0 115200 8-N-1
 
-{% include alert.html content="Try PIN 10 or other GND PINs if it doesn't work with 14." alert="Note"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Try PIN 10 or other GND PINs if the connection doesn't work by using PIN 14." alert="Note"  icon="svg-warning" color="yellow" %}
 
-{% include alert.html content="Some USB TTL adapters label TX and RX pins the other way around: try to swap them if it doesn't work." alert="Note"  icon="svg-warning" color="yellow" %}
+{% include alert.html content="Some USB TTL adapters label TX and RX pins the other way around: try to swap them if the connection doesn't work." alert="Note"  icon="svg-warning" color="yellow" %}
 
 
 ## Root procedure
@@ -104,7 +104,7 @@ For more info [XPONos partition layout](https://github.com/XPONos/linux_lantiq-f
 
 ## List of firmwares and files
 
-{% include alert.html content="With the root procedure without tweezers, the firmware already on the Huawei Stick corresponds to rooted firmware in this list." alert="Info" icon="svg-info" color="blue" %}
+{% include alert.html content="If the root procedure without tweezers is used, the firmware already on the Huawei Stick corresponds to rooted firmware in this list." alert="Info" icon="svg-info" color="blue" %}
 
 - [Carlito MTD2](https://ma5671a.s3.nl-ams.scw.cloud/mtd2.bin){: .btn }  md5hash: d3cb6f7efec201b37931139feb4bb23b
 - [Huawei Rooted MTD2](https://ma5671a.s3.nl-ams.scw.cloud/mA5671a_root_mtd2.img){: .btn } md5hash: 3138d2dd06a32bb92bc63610fec6fcd6
@@ -152,7 +152,7 @@ cat /dev/mtdX | nc 192.168.1.11 1234
 
 {% include alert.html content="Only the inactive image can be flashed" alert="Info" icon="svg-info" color="blue" %}
 
-The follwing examples flashes a new rootfs to image1 and boots to it
+The following commands are used to flash a new rootfs to image1 and then boot to it
 ```sh
 # mtd -e image1 write /tmp/rootfs.bin image1
 # fw_setenv committed_image 1
@@ -160,13 +160,13 @@ The follwing examples flashes a new rootfs to image1 and boots to it
 # reboot
 ```
 
-{% include alert.html content="Some OLTs only want to boot from image 0 and therefore this procedure must be preceded by the following procedure with obviously inverted images" alert="Warning" icon="svg-warning" color="yellow" %}
+{% include alert.html content="Some OLTs don't like when ONTs don't boot from image 0, therefore the previous procedure must be preceded by the following procedure with inverted images, as to clone image 1 into image 0" alert="Warning" icon="svg-warning" color="yellow" %}
 
 ## Cloning of mtd1 (image 0) into mtd5 (image 1)
 
-{% include alert.html content="Image 0 can be flashed to image 1 while image 1 cannot be flashed to image 0 because it has larger rootfs_data" alert="Warning" icon="svg-warning" color="yellow" %}
+{% include alert.html content="Image 0 can be flashed to image 1, while image 1 cannot be flashed to image 0 because it has larger rootfs_data" alert="Warning" icon="svg-warning" color="yellow" %}
 
-The follwing examples clones a image0 to image1 and boots to it
+The following commands are used to clone image0 to image1 and then boot to it
 ```sh
 # cat /dev/mtd2 > /tmp/mtd2.bin
 # mtd -e image1 write /tmp/mtd2.bin image1
diff --git a/_ont/ont-leox-lxt-010s-h.md b/_ont/ont-leox-lxt-010s-h.md
index c2e0878..5b4467b 100644
--- a/_ont/ont-leox-lxt-010s-h.md
+++ b/_ont/ont-leox-lxt-010s-h.md
@@ -45,18 +45,18 @@ parent: Leox
 
 This stick supports dual boot. 
 
-`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and the firmware of the second one
+`k0` and `r0` respectively contain the kernel and firmware of the first image, while `k1` and `r1` respectively contain the kernel and the firmware of the second one.
 
 ## Serial Console
 
 
-The stick has a TTL 3.3v UART console (configured as 115200 8-N-1)  that can be accessed from the top surface. To accept TX line commands, GND of TTL adapter should be attached to the stick's shield:
+The stick has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. To accept TX line commands, the GND of the TTL adapter should be attached to the stick's shield:
 
 {% include image.html file="ont-leox-lxt-010s-h_ttl.jpg" alt="Leox LXT-010S-H TTL Pinout" caption="Leox LXT-010S-H TTL Pinout" %}
 
 ## List firmware version
 
-{% include alert.html content="There is a new firmware avaliable from LeoLabs that fix the 2.5GbE" alert="Note" icon="svg-info" color="blue" %}
+{% include alert.html content="There is a new firmware avaliable from LeoLabs that fixes the 2.5GbE" alert="Note" icon="svg-info" color="blue" %}
 
 - V3.3.4L3
 - V3.3.4L4rc1 (Fix 2.5GbE HiSGMII)
@@ -95,9 +95,9 @@ GPON_PLOAM_PASSWD=AAAAAAAAAA
 | LAN_SDS_MODE = 7     | 1GbE with auto-neg off               |
 | LAN_SDS_MODE = 8     | 2.5GbE with auto-neg off             |
 
-If you try to use a mode not listed here, stick will use 1 as default
+If you try to use any mode not listed here, stick will default to mode 1.
 
-to change the link mode use this command:
+To change the link mode use this command:
 
 ```sh
 # /etc/scripts/flash get LAN_SDS_MODE
@@ -107,7 +107,7 @@ LAN_SDS_MODE=1
 
 # Known Bugs
 
-Stock firmware doesn't work @ 2.5GbE. There is a new firmware avaliable from LeoLabs that fix this issue
+The stock firmware doesn't work @ 2.5GbE. There is a new firmware avaliable from LeoLabs that fixes this issue.
 
 
 # Miscellaneous Links
diff --git a/_ont/ont-nokia-g-010g-q.md b/_ont/ont-nokia-g-010g-q.md
index 0c6e078..47e13c5 100644
--- a/_ont/ont-nokia-g-010g-q.md
+++ b/_ont/ont-nokia-g-010g-q.md
@@ -40,7 +40,7 @@ parent: Nokia
 | mtd2 | 00700000 | 00010000  | "ImageA" |
 | mtd3 | 00700000 | 00010000  | "ImageB" |
 
-This ont seems to support dual boot (notice partitions "ImageA" and "ImageB"), however this has not been tested. 
+This ONT seems to support dual boot (notice partitions "ImageA" and "ImageB"), however this has not been tested. 
 ## List of firmwares and files
 
 # Serial
@@ -52,7 +52,7 @@ You can easily communicate with the ONT using a TTL converter (for example the C
 
 {% include alert.html content="The ONT's serial logic is 3V3." alert="Warning"  icon="svg-warning" color="red" %}
 
-Make sure the logic of your TTL converter is 3V3 too otherwise you might damage the ONT, in my case I wasn't sure the CH341A had a 3V3 logic for the TTL part so I set up a voltage divider made of 2 resistors between the TX pin and ground as shown in the image below.
+Make sure the logic of your TTL converter is 3V3 too otherwise you might damage the ONT, in my case I wasn't sure whether the CH341A programmer used 3V3 logic for the TTL part so I set up a voltage divider made of 2 resistors between the TX pin and ground as shown in the image below.
 
 *Also make sure that your TTL converter RX pin voltage threshold is less than (or equal to) 3V3*
 
diff --git a/_ont/ont-nokia-g-010g-t.md b/_ont/ont-nokia-g-010g-t.md
index bc088e3..538ebd7 100644
--- a/_ont/ont-nokia-g-010g-t.md
+++ b/_ont/ont-nokia-g-010g-t.md
@@ -45,7 +45,7 @@ parent: Nokia
 
 ## Serial Console
 
-The ONT has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. To accept TX line commands, GND of TTL adapter should be attached to the ONT's shield (central GND PIN is not connected):
+The ONT has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. To accept TX line commands, the GND of the TTL adapter should be attached to the ONT's shield:
 
 {% include image.html file="q-010g-t_ttl.jpg"  alt="Nokia G-010G-T TTL" caption="Nokia G-010G-T TTL" %}
 
diff --git a/_ont/ont-nokia-g-010s-p.md b/_ont/ont-nokia-g-010s-p.md
index 2241c3e..7d9f3d4 100644
--- a/_ont/ont-nokia-g-010s-p.md
+++ b/_ont/ont-nokia-g-010s-p.md
@@ -26,7 +26,7 @@ parent: Nokia
 <br/>
 {% include image.html file="g-010s-p-and-ma5671a.jpg"  alt="G-010S-P and MA5671A Teardown" caption="G-010S-P and MA5671A Teardown" %}
 <br/>
-{% include alert.html content="G-010S-P and other models will not expose ethernet interface unless fiber cable is connected ([source](https://forum.mikrotik.com/viewtopic.php?t=116364&start=300))" alert="Warning" icon="svg-warning" color="yellow" %}
+{% include alert.html content="G-010S-P and other models will not expose an ethernet interface unless fiber cable is connected ([source](https://forum.mikrotik.com/viewtopic.php?t=116364&start=300))" alert="Warning" icon="svg-warning" color="yellow" %}
 
 ## Firmware is interchangeable with:
 
diff --git a/_ont/ont-odi-realtek-dfp-34x-2c2.md b/_ont/ont-odi-realtek-dfp-34x-2c2.md
index 67298c2..1f7cc29 100644
--- a/_ont/ont-odi-realtek-dfp-34x-2c2.md
+++ b/_ont/ont-odi-realtek-dfp-34x-2c2.md
@@ -23,7 +23,7 @@ parent: ODI
 | SSH         | ✅ user `admin`, password `admin` |
 | Form Factor | miniONT SFP                       |
 
-{% include alert.html content="SSH uses an outdated set of algorithm/ciphers, you can connect using the following command:" alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="SSH uses an outdated set of algorithms/ciphers, you can connect using the following command:" alert="Note"  icon="svg-info" color="blue" %}
 
 ```shell
 ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -oCiphers=+3des-cbc admin@192.168.1.1
@@ -39,7 +39,7 @@ ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -oCiphers=+3des-cbc admin@192.16
 
 ## List of firmwares and files
 - [V1.0-220530 Modded](https://github.com/Anime4000/RTL960x/files/8821809/M114_sfp_ODI_hybrid_220527_stich86_220530.tar.zip){: .btn } 
- by [stich86](https://github.com/stich86) **SUGGESTED** since it has working VLAN translation.  
+ by [stich86](https://github.com/stich86) **RECOMMENDED** because it has working VLAN translation.  
 
 ## List of partitions
  
@@ -62,7 +62,7 @@ ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -oCiphers=+3des-cbc admin@192.16
 
 This stick supports dual boot. 
 
-`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and the firmware of the second one
+`k0` and `r0` respectively contain the kernel and firmware of the first image, while `k1` and `r1` respectively contain the kernel and the firmware of the second one
 
 # Serial
 
@@ -91,7 +91,7 @@ GPON_SN=TMBB00000000
 
 ## Getting/Setting the ONT's PLOAM password
 
-{% include alert.html content="The PLOAM password is stored in HEX format, with no 0x or separator" alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="The PLOAM password is stored in HEX format, without any 0x or separators" alert="Note"  icon="svg-info" color="blue" %}
 
 ```sh
 # flash get GPON_PLOAM_PASSWD
@@ -101,7 +101,7 @@ GPON_PLOAM_PASSWD=41414141414141414141
 
 ## Getting/Setting the ONT Vendor ID
 
-{% include alert.html content="this may need OMCI_OLT_MODE set to 3 to work" alert="Note" icon="svg-info" color="blue" %}
+{% include alert.html content="This may need the OMCI_OLT_MODE value to be set to 3 to work" alert="Note" icon="svg-info" color="blue" %}
 
 ```sh
 # flash get PON_VENDOR_ID  
@@ -110,7 +110,7 @@ PON_VENDOR_ID=ZTEG
 ```
 
 ## Getting/Settng the ONT Custom software version
-{% include alert.html content="this needs OMCI_OLT_MODE set to 3 and firmware 220530 modded by stich86" alert="Note" icon="svg-info" color="blue" %}
+{% include alert.html content="This needs the OMCI_OLT_MODE value to be set to 3 and firmware 220530 as modded by stich86" alert="Note" icon="svg-info" color="blue" %}
 
 ```sh
 # nv setenv sw_custom_version0 YOURFIRSTSWVER
@@ -118,7 +118,7 @@ PON_VENDOR_ID=ZTEG
 ```
 
 ## Getting/Setting a custom HW Version
-{% include alert.html content="this probably needs OMCI_OLT_MODE set to 3" alert="Note" icon="svg-info" color="blue" %}
+{% include alert.html content="This may need the OMCI_OLT_MODE value to be set to 3 to work" alert="Note" icon="svg-info" color="blue" %}
 
 
 ```sh
@@ -128,7 +128,7 @@ HW_HWVER=V2.0
 ```
 
 ## Getting/Setting a custom ONT Equipment ID
-{% include alert.html content="this probably needs OMCI_OLT_MODE set to 3" alert="Note" icon="svg-info" color="blue" %}
+{% include alert.html content="This may need the OMCI_OLT_MODE value to be set to 3 to work" alert="Note" icon="svg-info" color="blue" %}
 ```sh
 # flash get GPON_ONU_MODEL
 GPON_ONU_MODEL=DFP-34X-2C2
diff --git a/_ont/ont-technicolor-afm0002.md b/_ont/ont-technicolor-afm0002.md
index e540d1d..813b9de 100644
--- a/_ont/ont-technicolor-afm0002.md
+++ b/_ont/ont-technicolor-afm0002.md
@@ -37,7 +37,7 @@ Configuration: asc0=0 115200 8-N-1
 - AFM0002WND (IP address: 169.0.0.1)
 
 {% include alert.html content="The version used to obtain the info shown on this page is the AFM0002TIM" alert="Info"  icon="svg-info" color="blue" %}
-{% include alert.html content="The AFM0002FWB can be transformed into AFM0002TIM. The AFM0002FWB has an older software version." alert="Warning"  icon="svg-warning" color="red" %}
+{% include alert.html content="The AFM0002FWB can be transformed into AFM0002TIM. Usually AFM0002FWBs have older software." alert="Warning"  icon="svg-warning" color="red" %}
 
 
 # List of software versions
@@ -69,18 +69,18 @@ Configuration: asc0=0 115200 8-N-1
 
 This stick supports dual boot. 
 
-`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and the firmware of the second one
+`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and firmware of the second one
 
 # List of firmwares and files
 ## Useful files
 - `/var/config/lastgood.xml` - Contains the user portion of the configuration
-- `/var/config/lastgood-hs.xml` - Contains the "hardware" configuration (i.e. that _should_ not be changed)
+- `/var/config/lastgood-hs.xml` - Contains the "hardware" configuration (which _should not_ be changed)
 - `/tmp/omcilog` - OMCI messages logs (must be enabeled, see below)
 
 ## Useful binaries
-- `/etc/scripts/flash`  - Used to manipulate the config files in a samewhat safe manner
-- `xmlconfig` - Used to low-level manipulate the XML config files. Called by `flash`
-- `nv` - Used to manipulate the nvram storage, including persistent config entries via `nv setenv`/`nv getenv`
+- `/etc/scripts/flash`  - Used to manipulate the config files in a somewhat safe manner
+- `xmlconfig` - Used for low-level manipulation of the XML config files. Called by `flash`
+- `nv` - Used to manipulate nvram storage, including persistent config entries via `nv setenv`/`nv getenv`
 - `omcicli` - Used to interact with the running OMCI daemon
 - `omci_app` - The OMCI daemon
 - `diag` - Used to run low-level diagnostics commands on the stick
@@ -132,7 +132,7 @@ sw_version1=V1_7_8_210412
 
 # Low Level Modding
 
-{% include alert.html content="This section is based on `V1_7_8_210412` firmware version of the stick" alert="Info" icon="svg-info" color="blue" %}
+{% include alert.html content="This section is based on the `V1_7_8_210412` version of the stick's firmware " alert="Info" icon="svg-info" color="blue" %}
 
 
 ## Transfering files from/to the stick
@@ -161,14 +161,14 @@ From the PC to the stick
 
 So mtd4/5 if you are on image1, mtd6/7 if you are on image0.
 
-The follwing examples flashes a new rootfs to image1 and boots to it
+The following commands are used to flash a new rootfs to image1 and then boot to it
 ```sh
 # flash_eraseall /dev/mtd7
 # cat /tmp/rootfs.new > /dev/mtd7
 # nv setenv sw_commit=1
 # reboot
 ```
-## Adding support to configurable SW and HW versions, VENDOR ID and much more
+## Adding support to configurable SW and HW versions, Vendor ID and much more
 `/etc/scripts/flash` can be flashed in order to add support for some variables implemented in `omci_app` but removed from `xmlconfig`. The patch is below (change the values to suit your needs)
 ```patch
 --- squashfs-root/etc/scripts/flash     2021-09-28 10:38:52.000000000 +0200
@@ -222,7 +222,7 @@ For reference, the patch changes the follwing section of the omci_app:
 -00408cf0 24 05 00 0f     li         a1,0xe
 +00408cf0 24 05 00 0f     li         a1,0xf
 ```
-(It's inside the function referecing the string `OMCI_SW_VER1`)
+(It's inside the function referencing the string `OMCI_SW_VER1`)
 
 The original file md5sum is: `4aea2f72bacc11256b7e2c1583d2ad4f`
 The patched file md5sum is: `da20327c4c002e4c27f82f6ee63dbc1a`
@@ -234,8 +234,8 @@ reboot
 /bin/omcicli set logfile 1 ffffffff
 ```
 1. The binary log will be placed inside: `/tmp/omcilog`
-2. You can convert it into .pcap using [omcilog2pcap](https://github.com/ADeltaX/omcilog2pcap)
-3. You can then open it with Wireshark by installing the OMCI plugin from [wireshark](https://wiki.wireshark.org/Contrib.md)
+2. You can convert it into a .pcap file using [omcilog2pcap](https://github.com/ADeltaX/omcilog2pcap)
+3. You can then open it with Wireshark by installing the OMCI plugin from [Wireshark](https://wiki.wireshark.org/Contrib.md)
    
 If you want to log everything since the stick boots, you can create a custom rootfs. Place the last command inside `etc/runomci.sh` as the last line of the file
 
diff --git a/_ont/ont-technicolor-afm0003.md b/_ont/ont-technicolor-afm0003.md
index d2c5c2d..0fc34d0 100644
--- a/_ont/ont-technicolor-afm0003.md
+++ b/_ont/ont-technicolor-afm0003.md
@@ -57,18 +57,18 @@ Configuration: asc0=0 115200 8-N-1
 
 This stick supports dual boot. 
 
-`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and the firmware of the second one
+`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and firmware of the second one
 
 # List of firmwares and files
 ## Useful files
 - `/var/config/lastgood.xml` - Contains the user portion of the configuration
-- `/var/config/lastgood-hs.xml` - Contains the "hardware" configuration (i.e. that _should_ not be changed)
+- `/var/config/lastgood-hs.xml` - Contains the "hardware" configuration (which _should not_ be changed)
 - `/tmp/omcilog` - OMCI messages logs (must be enabeled, see below)
 
 ## Useful binaries
-- `/etc/scripts/flash`  - Used to manipulate the config files in a samewhat safe manner
-- `xmlconfig` - Used to low-level manipulate the XML config files. Called by `flash`
-- `nv` - Used to manipulate the nvram storage, including persistent config entries via `nv setenv`/`nv getenv`
+- `/etc/scripts/flash`  - Used to manipulate the config files in a somewhat safe manner
+- `xmlconfig` - Used for low-level manipulation of the XML config files. Called by `flash`
+- `nv` - Used to manipulate nvram storage, including persistent config entries via `nv setenv`/`nv getenv`
 - `omcicli` - Used to interact with the running OMCI daemon
 - `omci_app` - The OMCI daemon
 - `diag` - Used to run low-level diagnostics commands on the stick
diff --git a/_ont/ont-tplink-xz000-g3.md b/_ont/ont-tplink-xz000-g3.md
index b07659e..03b7ffd 100644
--- a/_ont/ont-tplink-xz000-g3.md
+++ b/_ont/ont-tplink-xz000-g3.md
@@ -29,7 +29,7 @@ layout: default
 
 # Known Bugs
 
-The ONT randomly crashes when PPPoE connection is established
+The ONT randomly crashes when PPPoE connection by a connected router is established.
 
-The GPON serial sometimes temporarily disappears after a crash preventing the ONT from reaching O5
+The GPON serial sometimes temporarily disappears after a crash, preventing the ONT from reaching the O5 operational status.
 
diff --git a/_ont/ont-zte-f6005.md b/_ont/ont-zte-f6005.md
index cc1b916..8d3aa82 100644
--- a/_ont/ont-zte-f6005.md
+++ b/_ont/ont-zte-f6005.md
@@ -36,7 +36,7 @@ parent: ZTE
 
 # Known Bugs
 
-Buffer size is suboptimal, because of this the ONT can't keep up working at full speed during uploads if the server is geographically, and so latency-wise, far. There are no known problems with multiple connections.
+Buffer size is suboptimal: because of this the ONT is unable to work at full speed during uploads if the server is geographically, and/or latency-wise, far. There are no known problems with multiple connections.
 
 # Miscellaneous Links
 
diff --git a/_ont/ont-zyxel-pmg3000-d20b.md b/_ont/ont-zyxel-pmg3000-d20b.md
index 26bce2b..2ee63fa 100644
--- a/_ont/ont-zyxel-pmg3000-d20b.md
+++ b/_ont/ont-zyxel-pmg3000-d20b.md
@@ -27,7 +27,7 @@ parent: Zyxel
 {% include image.html file="op151s.png" alt="Ziza OP151S" caption="Ziza OP151S" %}
 
 Once you access the stick via ssh you will be presented with a second tier login. The credentials to access the zyxel shell are: username: `twmanu` , password: `twmanu`.
-From the zyxel shell you can move to a standard linux shell via the `linuxshell` command
+From the Zyxel shell you can move to a standard Linux shell using the `linuxshell` command
 
 ## Firmware is interchangeable with:
 
@@ -57,13 +57,13 @@ This stick supports dual boot, as visible from the presence of `ImageA` and `Ima
 
 # List of firmwares and files
 ## Useful files
-- `/var/config/ont.sys` used to customize various settings on the stick. If you don't have it you can copy the stock one from /ont.sys
+- `/var/config/ont.sys` - Used to customize various settings on the stick. If you don't have it you can copy the stock one from /ont.sys
 
 # Useful Commands
-{% include alert.html content="all commands start from the twmanu shell." alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="All commands start from the twmanu shell." alert="Note"  icon="svg-info" color="blue" %}
 
 ## Changing the ONT's S/N
-{% include alert.html content="the S/N is stored in the ASCII format." alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="The S/N is stored in the ASCII format." alert="Note"  icon="svg-info" color="blue" %}
 ```sh
 manufactory
 set sn ALCLf0f0f0f0
@@ -73,7 +73,7 @@ set sn ALCLf0f0f0f0
 ```
 
 ## Changing the ONT's PLOAM password
-{% include alert.html content="the PLOAM is stored in the ASCII format." alert="Note"  icon="svg-info" color="blue" %}
+{% 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:
 ```sh
 hal
@@ -81,7 +81,7 @@ set password PLOAMPASS
 ```
 
 ## Changing the ONT's equipment ID
-{% include alert.html content="model number must be 20 no more than chars total." alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="Model number must not be more than 20 characters long in total." alert="Note"  icon="svg-info" color="blue" %}
 ```sh
 manufactory
 set equipment id MYEQUIPMENTID
@@ -103,21 +103,24 @@ The entries for the software version are:
 SW_VER0:0xabcdef
 SW_VER1:0xabcedf
 ```
-{% include alert.html content="it's better to enter the software version in hex format, all lowercase precedeed by 0x." alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="It's better to enter the software version in hex format, all lowercase precedeed by 0x." alert="Note"  icon="svg-info" color="blue" %}
 
 ## See link speed
-This SFP have HSGMII enabled by default, `link_status=5` HSGMII 2.5Gbit, `link_status=4` SGMII 1Gbit:
+This SFP has HSGMII enabled by default: `link_status=5` for HSGMII 2.5Gbit, `link_status=4` for SGMII 1Gbit:
 ```
 linuxshell
 onu lanpsg 0
 ```
 
-## Connection state
-To see the connection state use this command, `curr_state=5` O5 state, `curr_state=1` all states other than O5:
+## Checking connection state
+To see the connection state use the following command:
 ```
 linuxshell
 onu ploamsg
 ```
+
+`curr_state=5` for O5 state, `curr_state=1` for all other operational states.
+
 ## Querying a particular OMCI ME
 Query via OMCI ME Class Name
 ```sh
@@ -138,7 +141,7 @@ show me classid OmciClassId (e.g 7)
 The stick has a tricky image packing method, fortunately it has been reverse engineered. A script to help you create a custom rootfs can be found here: [https://github.com/nanomad/zyxel-pmg-3000-mod-kit](https://github.com/nanomad/zyxel-pmg-3000-mod-kit)
 
 ## Flashing a new rootfs
-{% include alert.html content="all commands start from the twmanu shell." alert="Note"  icon="svg-info" color="blue" %}
+{% include alert.html content="All commands start from the twmanu shell." alert="Note"  icon="svg-info" color="blue" %}
 
 - Transfer the new mtd on the stick via tftp
 ```
@@ -172,7 +175,7 @@ To restore the default combination you can try following [this method](https://g
 # Known Bugs
 - [Not working with Broadcom BCM57810S](https://github.com/xvzf/zyxel-gpon-sfp/issues/10)
 - Issue on IPv6 discovery. But we are not sure if is a edge case of a particular ISP or not
-- [Some stick have a custom password](https://github.com/xvzf/zyxel-gpon-sfp/issues/6)
+- [Some sticks have a custom password](https://github.com/xvzf/zyxel-gpon-sfp/issues/6)
 
 
 # Miscellaneous Links
diff --git a/_sfp_cage/broadcom-57810s.md b/_sfp_cage/broadcom-57810s.md
index f0c7bbc..4145dc8 100644
--- a/_sfp_cage/broadcom-57810s.md
+++ b/_sfp_cage/broadcom-57810s.md
@@ -17,13 +17,13 @@ layout: default
 | SGMII  | ✅                   |
 | Type   | PCI express SFP card |
 
-In order to be able to set 2.5G speed you will have to patch your kernel's bnx2x module. The easiest way to do so is via DKMS which rebuilds just that module:
+In order to be able to set 2.5G speed you will have to patch your kernel's bnx2x module. The easiest way to do so is via DKMS which rebuilds only that module:
 
 - [DKMS for Linux 6.0.y](https://github.com/darkbasic/bnx2x-2_5g-dkms/tree/6.0.y)
 
-It also adds a module option that can be set to disable SFP TX fault detection, otherwise you won't be able to access your mini ont SFP if you don't attach the fiber to it.
+It also adds a module option that can be set to disable SFP TX fault detection, otherwise you won't be able to access your SFP mini-ONT if it's not connected to the fiber cable.
 
-Unfortunately despite the patches you will still have to use UEFI eDiag to unlock 2.5G capabilities:
+Unfortunately, despite the patches, you will still have to use UEFI eDiag to unlock 2.5G capabilities:
 
 - [How-to enable 2.5G capability via UEFI eDiag](https://www.dslreports.com/forum/r32230041-Internet-Bypassing-the-HH3K-up-to-2-5Gbps-using-a-BCM57810S-NIC)
 
diff --git a/_tools/molex-ont.md b/_tools/molex-ont.md
index aed9e34..06d4b06 100644
--- a/_tools/molex-ont.md
+++ b/_tools/molex-ont.md
@@ -5,8 +5,8 @@ nav_order: 3
 layout: default
 ---
 
-In some sticks, such as those based on lantiq, the serial is exposed in the upper pins of the ONT, in order to read them there are 2 possibilities:
-- the use of an SFP molex ([farnell](https://it.farnell.com/en-IT/molex/74441-0001/connector-sfp-rcpt-20pos-smt/dp/2112385)) to which you solder 4 wires and remove the other pins, this makes the adapter compatible for a single serial combination
+In some sticks, such as those based on Lantiq chipsets, the serial is exposed in the upper pins of the ONT, in order to read them there are two possibilities:
+- the use of an SFP molex ([farnell](https://it.farnell.com/en-IT/molex/74441-0001/connector-sfp-rcpt-20pos-smt/dp/2112385)) to which you solder four wires and remove the other pins, this makes the adapter compatible for a single serial combination
 - the use of a board to which the SFP molex is soldered, exposing the main SFP pins
 
 {% include image.html file="ma5671a-root-1.jpg"  alt="Example of how the sfp-ttl adapter" caption="Example of how the sfp-ttl adapter" %}
diff --git a/_tools/ttl-uart-adapter.md b/_tools/ttl-uart-adapter.md
index fb9bf98..62bfe11 100644
--- a/_tools/ttl-uart-adapter.md
+++ b/_tools/ttl-uart-adapter.md
@@ -5,11 +5,11 @@ nav_order: 2
 layout: default
 ---
 
-A TTL UART adapter makes it possible to connect the stick's serial to a computer via a USB interface, and on the computer through serial emulation it is possible to send commands just like the serial ports of the 1990s
+A TTL UART adapter makes it possible to connect the stick's serial to a computer via a USB interface, which makes it easy to send commands on modern computers through serial emulation, just like the serial ports of the 1990s.
 
-Is widely used in the modding of SFPs, and in general of most embedded devices, since a serial port is always present in all of them and is also used to de-briking the devices.
+Is widely used in the modding of SFPs, and in general of most embedded devices, since a serial port is always present in all of them and is also used to de-brick devices.
 
-TTL adapters are widely found on amazon, the most recommended one being:
+TTL adapters can be easily found on Amazon, the most recommended one being:
 
 - DSD TECH USB to TTL Serial Adapter with FTDI FT232RL Chip [Amazon.com](https://www.amazon.com/dp/B07BBPX8B8) [Amazon.it](https://www.amazon.it/dp/B07BBPX8B8)