6 files changed, 68 insertions, 68 deletions

diff --git a/_gpon/g_984_series.md b/_gpon/g_984_series.md
index 81f24ef..df8e9e1 100644
--- a/_gpon/g_984_series.md
+++ b/_gpon/g_984_series.md
@@ -19,7 +19,7 @@ The information on this page is taken from the GPON standard and information fro
 
 # General Concepts[^zyxel]
 
-- Bit Rate: 1.2 Gbps Upstream; 2.4 Gbps Downstream.
+- Bitrate: 1.2 Gbps Upstream; 2.4 Gbps Downstream.
 - Physical Reach: Max physical distance between OLT and ONT.
 - Differential Fiber Distance: Distance between closest and farthest ONT from OLT (max = 20km)
 
@@ -35,7 +35,7 @@ The information on this page is taken from the GPON standard and information fro
 | **1.24416**            | **2.48832**              |
 | 2.48832                | 2.48832                  |
 
-1.24416 Gbps up, 2.48832 Gbps down is the mainstream speed combination supported at current time.
+1.24416 Gbps up, 2.48832 Gbps down is the most supported speed combination at current time.
 
 # GPON Terminology
 
@@ -46,7 +46,7 @@ The information on this page is taken from the GPON standard and information fro
     * 0 .. 253 Assignable
     * 254 Reserved
     * 255 Broadcast/unassigned
-* OLT assigns to an ONU during the ONU's activation using the PLOAM channel.
+* The OLT assigns an id to any ONU during the ONU's activation using the PLOAM channel.
 * ONU-ID is unique across the PON and remains valid until the ONU is powered off, deactivated by the OLT or moves itself into an inactive state.
 
 ## Allocation Identifier (Alloc-ID)[^zyxel]
@@ -61,9 +61,9 @@ The information on this page is taken from the GPON standard and information fro
 A Transmission Container (T-CONT) is an ONU object representing a group of logical connections that appear as a single entity for the purpose of upstream bandwidth assignment on the PON.
 * Bandwidth assignment and QoS control are performed in every T-CONT by fixed and dynamic methods.
 * There are 5 types of T-CONT Traffic Descriptors:
-    * Type 1: fixed bandwidth type.
-    * Type 2 and Type 3: guaranteed bandwidth types.  
-    * Type 4: best-effort type.
+    * Type 1: fixed bandwidth;
+    * Type 2 and Type 3: guaranteed bandwidth;  
+    * Type 4: best-effort;
     * Type 5: mixed type, involving all bandwidth types and bearing all services
 
 | Type 1    | Type 2    | Type 3    | Type 4 | Type 5           |
@@ -74,9 +74,9 @@ A Transmission Container (T-CONT) is an ONU object representing a group of logic
 
 * For TR-156 and TR-167, each T-CONT represents a traffic class
 * Each ONU is assigned at least one Alloc-ID which is equal to that ONU's ONU-ID and may be assigned additional Alloc-IDs per the OLT's discretion.
-    * Typically have 4 T-CONTs, supporting 4 traffic classes, plus one T-CONT for OMCI
-* Default Alloc-ID is used to carry the upstream PLOAM and OMCC traffic and may carry user data traffic.
-* OLT schedules upstream traffic across all ONUs according to the priority and weight assigned to each T-CONT, and their buffer occupancy. Other bandwidth assignment mechanisms are available, for example fixed bandwidth, assured bandwidth, and nonassured bandwidth[^broadbandforum].
+    * Typically have 4 T-CONTs, supporting 4 traffic classes, plus an extra one for OMCI
+* The default Alloc-ID is used to carry the upstream PLOAM and OMCC traffic and may carry user data traffic.
+* The OLT schedules upstream traffic across all ONUs according to the priority and weight assigned to each T-CONT, and their buffer occupancy. Other bandwidth assignment mechanisms are available, for example fixed bandwidth, assured bandwidth, and nonassured bandwidth[^broadbandforum].
 
 
 ## Dynamic Bandwidth Allocation (DBA)
@@ -84,7 +84,7 @@ A Transmission Container (T-CONT) is an ONU object representing a group of logic
 {% include image.html file="quick-start/pon_dba.jpg" alt="PON DBA Abstraction" caption="PON DBA Abstraction" %}
 
 
-Dynamic Bandwidth Allocation (DBA) is a technique by which traffic bandwidth in a shared telecommunications medium can be allocated on demand and fairly between different users of that bandwidth. And it is performed on the upstream traffic[^zyxel].
+Dynamic Bandwidth Allocation (DBA) is a technique by which traffic bandwidth in a shared telecommunications medium can be allocated on demand and fairly between different users of that bandwidth. It is performed on the upstream traffic[^zyxel].
 
 With DBA, the OLT assesses the bandwidth needs of the ONUs in real time and allocates upstream PON capacity accordingly[^broadbandforum].
 
@@ -110,10 +110,10 @@ Payload - User data
 
 ### GPON Encapsulation
 
-GPON use two layers of encapsulation:
+GPON uses two layers of encapsulation:
 
 1. TDM and Ethernet frames are wrapped into GTC Encapsulation Method (GEM) frames, which have a GFP-like format (derived from Generic Frame Procedure ITU G.7401). 
-The main purpose of the GEM frame is to provide a frame-oriented service, as an alternative to ATM, in order to efficiently accommodate Ethernet and TDM frames. With GEM, all traffic is mapped across the GPON network using a variant of SONET/SDH GFP. GEM supports a native transport of voice, video, and data without an added ATM or IP encapsulation layer[^medium],[^fs].
+The main purpose of the GEM frame is to provide a frame-oriented service, as an alternative to ATM, in order to efficiently accommodate Ethernet and TDM frames. With GEM, all traffic is mapped across the GPON network using a variant of SONET/SDH GFP. GEM natively supports transportation of voice, video, and data without an added ATM or IP encapsulation layer[^medium],[^fs].
 2. ATM and GEM frames are both encapsulated into GTC frames that are finally transported over the PON[^medium],[^fs].
 
 ITU-T G.984 defines GEM as the only data transport scheme for GPON. Bandwidth allocation in GPON grants individual transmission opportunities to the ONU's traffic-bearing entities on the timescale of a single GTC frame[^zyxel].
@@ -144,32 +144,32 @@ PCBd consists of the GTC header and BWmap:
 
 {% include image.html file="quick-start/downstream-multiplexing.png" alt="Downstream multiplexing (shaded GEM port indicates multicast)" caption="Downstream multiplexing (shaded GEM port indicates multicast)" %}
 
-1. OLT sends Ethernet frames from Uplink ports to the GPON service processing module based on configured rules to the PON ports.
-2. GPON service processing module then encapsulates the Ethernet frames into GEM port data packets for downstream transmission. 
+1. The OLT sends Ethernet frames from Uplink ports to the GPON service processing module based on configured rules to the PON ports.
+2. The GPON service processing module then encapsulates the Ethernet frames into GEM port data packets for downstream transmission. 
 3. GPON transmission convergence (GTC) frames that contain GEM PDUs are broadcast to all ONT/ONUs connected to the GPON port.
-4. ONT/ONU filters the received data based on the GEM port ID contained in the GEM PDU header and retains the data only significant to the GEM ports on this ONT/ONU.
-5. ONT decapsulates the data and sends the Ethernet frames to the end users via service ports.
+4. The ONT/ONU filters the received data based on the GEM port ID contained in the GEM PDU header and only retains data significant to the GEM ports on this ONT/ONU.
+5. The ONT decapsulates the data and sends the Ethernet frames to the end users via service ports.
 
 ### Upstream[^zyxel],[^broadbandforum],[^cisco]
 
 {% include image.html file="quick-start/gpon-upstream.jpg" alt="GPON Upstream" caption="GPON Upstream" %}
 
-In the Upstream the GEM traffic is carried over one or more T-CONTs. The OLT receives the transmission associated with the T-CONT and the frames are forwarded to the GEM TC adapter and then the GEM client.
+In the Upstream channel, GEM traffic is carried over one or more T-CONTs. The OLT receives the transmission associated with the T-CONT and the frames are forwarded to the GEM TC adapter and then the GEM client.
 
 - Use Time Division Multiple Access (TDMA) for upstream data transmission w/o AES encryption.
     * Distance between the OLT and ONT/ONU is measured (Ranging):
-        * OLT starts the process on an ONU when the ONU first registers with the OLT and obtains round trip delay (RTD) of the ONU. Based on the RTD, the other key components are identified:
+        * The OLT starts the process on an ONU when the ONU first registers with the OLT and obtains round trip delay (RTD) of the ONU. Based on the RTD, other key components are identified:
         * Calculation of the physical reach of that specific ONU, as this OLT requires a proper equalization delay (EqD) for each ONU based on physical reach.
-        * RTC and EqD synchronize data frames sent by all ONUs
+        * RTC and EqD synchronize data frames sent by all ONUs.
     * Time slots are allocated based on distance. In order to prevent data conflict (collisions), the OLT must be able to precisely measure the distance between itself and each ONU to provide a proper time slot to facilitate data upstream. This allows the ONUs to send data at specified time slots, to prevent issues upstream. This process is achieved through a technique called ranging. 
-    * ONT/ONU sends traffic upstream based on granted time slot.
+    * The ONT/ONU sends traffic upstream based on the granted time slot.
 - Dynamic Bandwidth Allocation (DBA) enables the OLT to monitor in real-time, congestion, bandwidth usage, and configuration.
 - Traffic multiplexing is distributed.
-- The OLT grants the upstream bandwidth allocation.
+- The OLT grants upstream bandwidth allocation.
 - The ONU traffic-bearing entities are identified by their Allocations IDs.
-- The alloc-IDs are multiplexed in time as specified by the bandwidth-map (given by the OLT in the downstream frame).
-- Within the bandwidth allocation, the ONU uses the GEM Port-IF as key to identify upstream GEM frames.
-- Each upstream frame contains the content carried by one or more T-CONT/T-CONTs.
+- Alloc-IDs are multiplexed in time as specified by the bandwidth-map (provided by the OLT in the downstream frame).
+- Within its bandwidth allocation, the ONU uses the GEM Port-IF as key to identify upstream GEM frames.
+- Each upstream frame contains the content carried by one or more T-CONTs.
 - All ONUs connected to a GPON port share the upstream bandwidth.
 - All ONUs send their data upstream at their own time slots based on bandwidth map (BWmap) requirements. 
 - Each ONU reports the status of data to be sent to the OLT by use of upstream frames. OLT uses DBA to allocate upstream time slots to ONUs and sends updates in each frame.
@@ -178,7 +178,7 @@ In the Upstream the GEM traffic is carried over one or more T-CONTs. The OLT rec
 
 {% include image.html file="quick-start/upstream-multiplexing.png" alt="Upstream multiplexing" caption="Upstream multiplexing" %}
 
-1. ONT/ONU send Ethernet frames to GEM ports based on configured rules that map service ports and GEM ports.
+1. ONT/ONUs send Ethernet frames to GEM ports based on configured rules that map service ports and GEM ports.
 2. GEM ports encapsulate the Ethernet frames into GEM PDUs and add these PDUs to T-CONT queues based on rules that map GEM ports and T-CONT queues.
 3. T-CONT queues use time slots based on DBA, then transmit upstream GEM PDUs to the OLT.
 4. OLT decapsulates the GEM PDU, the original Ethernet frame is now seen.
@@ -228,7 +228,7 @@ Resolves Ethernet frames and directly maps the data of Ethernet frames into the
    * Establish and release connections with the ONT.
    * Manage the UNIs on the ONT.
    * Request configuration information and performance statistics.
-   * Autonomously alert of events, such as a link failure.
+   * Autonomously alert events, such as a link failure.
 - Key Points:
    * Protocol runs over a GEM connection between the OLT and ONT.
    * GEM connection is established while the ONT initializes.
@@ -236,40 +236,40 @@ Resolves Ethernet frames and directly maps the data of Ethernet frames into the
 
 ### Management Information Base (MIB) and Management entities (ME's)[^arsat]
 
-A way of MIB (Management Information Base) formed by Management Entities (ME's) is used to fully describe the ONU configuration, status and several other actions
+MIBs (Management Information Base) formed by Management Entities (MEs) are used to fully describe the ONU configuration, status and several other actions.
 
-OMCI constitute the protocol in order to support the set of actions performed over ONU to create; delete and other set of actions on those ME's
+OMCI constitutes the protocol which supports the set of actions performed over an ONU to create, delete and more on those MEs
 
 - A Managed Entity (ME) is composed of attributes, actions and notifications defining its characteristics.
 - Managed Entity (ME Class Value)
     - Purpose of the entity
-    - Autonomously instantiated by ONU or explicitly created by OLT
+    - Autonomously instantiated by the ONU or explicitly created by the OLT
     - Relationship(s) with other managed entities
 - Attributes: Attribute Definition
-    - ME id: This attribute provides a unique number for each instance of this managed entity.
-    - List of attributes. Attribute Number within ME Determined by the Order in Which Attributes are Listed
+    - ME id: provides a unique number for each instance of this managed entity.
+    - List of attributes: Attribute Number within ME determined by the order in which attributes are listed
 - Actions: operations that may be performed on the entity (Create/Get/Set/Test, etc.)
 - Notifications (Alarm, AVC, TCA, Test Result)
-- There can be multiple instances of a Managed Entity. Each instance has the same attributes, actions and notifications even though the values of the attributes may be different from each other.
+- There can be multiple instances of any Managed Entity: each instance has the same attributes, actions and notifications even though the values of the attributes may be different from one another.
 
 ### VEIP and PPTP[^huaweiveip],[^cdatatec]
 
-According to the application, ONU can be divided into six types, namely SFU (Single Family Unit) ONU, HGU (Home Gateway Unit) ONU, MDU (Multi-Dwelling Unit) ONU, SBU (Single Business Unit) ONU, MTU (Multi-Tenant Unit) ONU and CBU (Cellular Backhaul Unit) ONU. However, only SFU (Single Family Unit) ONU and HGU (Home Gateway Unit) ONU are used by the end-users in practical application.
+According to the application, ONU can be divided into six types, namely SFU (Single Family Unit) ONU, HGU (Home Gateway Unit) ONU, MDU (Multi-Dwelling Unit) ONU, SBU (Single Business Unit) ONU, MTU (Multi-Tenant Unit) ONU and CBU (Cellular Backhaul Unit) ONU. However, only SFU (Single Family Unit) ONU and HGU (Home Gateway Unit) ONU are used by the end-users in practical applications.
 
-HGU ONU takes the Virtual Ethernet interface point (VEIP). Virtual Ethernet interface point (VEIP) as an OMCI administrative domain and a non-OMCI administrative domai (like TR-069). At the switchover point of the data plane, the ME can be managed only through the OMCI and is visible to the non-OMCI management domain, but not manageable. Similarly, all UNI-side modules under the VEIP are invisible to and cannot be managed by the OMCI. They are visible and manageable only to the non-OMCI management domain. In addition, each ONU should have only one VEIP.
+HGU ONU takes the Virtual Ethernet Interface Point (VEIP) as an OMCI administrative domain and a non-OMCI administrative domain (like TR-069). At the switchover point of the data plane, the ME can be managed only through the OMCI and is visible to the non-OMCI management domain, but not manageable. Similarly, all UNI-side modules under the VEIP are invisible to and cannot be managed by the OMCI. They are visible and manageable only to the non-OMCI management domain. In addition, each ONU should have only one VEIP.
 
-When the ONU uploads the MIB, the ONU reports only the mandatory MEs and supported optional MEs. It does not report the MEs related to LOID authentication, performance monitoring, and T-CONT MEs of the OMCC channel.
+When the ONU uploads MIBs, the ONU reports only the mandatory MEs and supported optional MEs. It does not report the MEs related to LOID authentication, performance monitoring and T-CONT MEs of the OMCC channel.
 
-The ONU should be used according to the device type and report either VEIP or PPTP during MIB upload. The SFU only uses and reports PPTP. VEIP should not be used. HGUs can only use and report VEIPs. PPTP should not be used. The OLT determines the ONU type based on the ONU Type attribute in ME:ONU Capability. Only one VEIP is allowed in each HGU. ONU will report VEIP or PPTP (Physical Path Termination Point) when MIB is uploaded according to the type of the device, while HGU can only use and report VEIP rather than PPTP. OLT will judge the type of ONU devices according to the attribution of ONU type in ONU capability.
+The ONU should be used according to the device type and report either VEIP or PPTP during MIB upload. The SFU only uses and reports PPTP. VEIP should not be used. HGUs can only use and report VEIPs. PPTP should not be used. The OLT determines the ONU type based on the ONU Type attribute in ME:ONU Capability. Only one VEIP is allowed in each HGU. ONUs will report VEIP or PPTP (Physical Path Termination Point) when MIB is uploaded according to the type of the device, while HGUs can only use and report VEIP rather than PPTP. The OLT will judge the type of each ONU device according to the ONU type attribute in ONU capability.
 
 {% include image.html file="quick-start/veip.jpg" alt="Service Process of HGU ONU" caption="Service Process of HGU ONU" %}
 
 
-SFU ONU only supports the OMCI management domain. PPTP is what SFU uses and reports, while VEIP is not available. The processing mode of OMCI configured data flow is different from that of RG flow. For OMCI data flow, there is a one-to-one mapping between the GEM port on the WAN side and the UNI port on the LAN side. All data packets can pass through without MAC address learning or forwarding. Wireless interfaces are not allowed in OMCI.
+SFU ONUs only support the OMCI management domain. PPTP is what SFU uses and reports, while VEIP is not available. The processing mode of OMCI configured data flow is different from that of RG flow. For OMCI data flow, there is a one-to-one mapping between the GEM port on the WAN side and the UNI port on the LAN side. All data packets can pass through without MAC address learning or forwarding. Wireless interfaces are not allowed in OMCI.
 
-SFU ONU is designed for a single family unit with broadband access terminal function without a more complex home gateway function from the perspective of application and ONU capacity. SFU ONU, mainly used in FTTH scenarios, has 1 or 4 Ethernet interfaces and is available for Ethernet / IP services, optional VoIP services (built-in IAD), or CATV services.
+SFU ONUs are designed for a single family unit with broadband access terminal function without a more complex home gateway function from the perspective of application and ONU capacity. SFU ONUs, mainly used in FTTH scenarios, typically have 1 or 4 Ethernet interfaces and are available for Ethernet / IP services, optional VoIP services (built-in IAD), or CATV services.
 
-SFU ONU works under the bridging mode (layer 2 of ISO model), supports multiple VLAN functions, and its Ethernet port can be configured and managed by OLT through OMCI / OAM. Combined with a home gateway, SFU ONU is good at providing strong service capability.
+SFU ONUs work under bridging mode (layer 2 of ISO model), support multiple VLAN functions, and their Ethernet port can be configured and managed by the OLT through OMCI / OAM. Combined with a home gateway, SFU ONUs are good at providing strong service capability.
 
 <hr>
 
diff --git a/_gpon/gpon-auth.md b/_gpon/gpon-auth.md
index 5da0ee7..52a2dbd 100644
--- a/_gpon/gpon-auth.md
+++ b/_gpon/gpon-auth.md
@@ -8,17 +8,17 @@ layout: default
 The information on this page is taken from the GPON standard and information from the major vendors of GPON equipment, each individual item containing a verifiable citation in the standard. Feel free to cite this page as: `{{ page.title }}, Hack GPON. Available at: https://hack-gpon.org{{ page.url }}`.
 
 # ONU activation state: `Ox`[^huawei],[^standardgpon]
-The process for an ONU to go online unconfigured involves five states:
+The process for an unconfigured ONU to go online involves five states:
 
 - **`O1` Initial:** the OLT sends a message to the ONU to start the ONU, and the ONU enters the standby state;
-- **`O2` Standby:** After receiving the message, the ONU extracts the delimiter value, power level, and pre-allocated compensation delay from the message, and adjusts its configurations accordingly to support subsequent information exchange.
-- **`O3` Serial number:** The OLT sends a serial number (SN) request to the ONU. The ONU sends its SN to the OLT. After receiving the SN of the ONU, the OLT allocates a temporary ONU ID to the ONU.
-- **`O4` Ranging:** The OLT sends a ranging request to the ONU. After receiving the ranging request from the OLT, the ONU responds with a message carrying its SN and ONU ID. The OLT calculates the compensation delay and sends it to the ONU in a message. After receiving the message, the ONU sets the compensation delay accordingly.
+- **`O2` Standby:** After receiving the message, the ONU extracts the delimiter value, power level, and pre-allocated compensation delay from the message, and adjusts its configurations accordingly, to support subsequent information exchanges.
+- **`O3` Serial number:** The OLT sends a serial number (SN) request to the ONU. The ONU sends its SN to the OLT. After receiving the ONU's SN, the OLT allocates a temporary ONU-ID to the ONU.
+- **`O4` Ranging:** The OLT sends a ranging request to the ONU. After receiving the ranging request from the OLT, the ONU responds with a message carrying its SN and ONU-ID. The OLT calculates the compensation delay and sends it to the ONU in a message. After receiving the message, the ONU sets the compensation delay accordingly.
 - **`O5` Operation:** The OLT sends a password request to the ONU. The ONU returns a password to the OLT. 
 - **`O6` Intermittent LODS state.**
 - **`O7` Emergency Stop state.**
 
-The password is not configured on the OLT. If the automatic discovery function is enabled on the PON port of the OLT, the OLT reports an ONU auto-discovery alarm to the CLI or NMS. The ONU goes online normally only after being confirmed.
+The password is not configured on the OLT: if the automatic discovery function is enabled on the OLT's PON port, the OLT reports an ONU auto-discovery alarm to the CLI or NMS. The ONU goes online normally only after being confirmed.
 
 ```mermaid
 graph TD
@@ -40,7 +40,7 @@ graph TD
 
 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`, 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.
+This 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.
 
 This is most likely to reduce logs from misconfigured ONTs and to be able to send updates automatically to ONTs.
 
diff --git a/_gpon/mib.md b/_gpon/mib.md
index 56e5d67..2161308 100644
--- a/_gpon/mib.md
+++ b/_gpon/mib.md
@@ -5,20 +5,20 @@ nav_order: 3
 layout: default
 ---
 
-The OMCI standard is defined in a way that suppliers can offer modular and incremental functionality to meet different levels of customer needs.
+The OMCI standard is defined in a way such that suppliers can offer modular and incremental functionality to meet different levels of customer needs.
 
-The standards [^G_988] and [^G_984_4] define the protocol needed to handle all the features of the PON specifications ([^G_984_1], [^G_987], [^G_9807_1], ...), as well as a number of services and functionalities.
+The [^G_988] and [^G_984_4] standards define the protocol needed to handle all the features of the PON specifications ([^G_984_1], [^G_987], [^G_9807_1], ...), as well as a number of services and functionalities.
 The standard was born with B-PON, then modified with G-PON and separated with XGS-PON. OMCI supports interoperability, yet it allows for optional components and future extensions.
 
 A protocol-independent MIB (Management Information Base) describes the exchange of information across OMCI [^G_988] and [^G_984_4]. This protocol is defined in terms of MEs. MEs are abstract representations of resources and services in an ONU. Only a small subset of the list of MEs is mandatory.
 
-The existence of other MEs depends on the architecture and feature set supported by the vendor [^G_988] and [^G_984_4]. Major ISPs and vendors have created their own extensions for MIBs [^att_open_omci], [^verizon_open_omci].
+The existence of other MEs depends on the architecture and feature set supported by the vendor's [^G_988] and [^G_984_4]. Major ISPs and vendors have created their own extensions for MIBs [^att_open_omci], [^verizon_open_omci].
 
-Each MEs consists of an entry ID and zero, one or more instances. Each instance has its own ID, usually starting at 0, but this is not always the case. Every instance has one or more attributes, each characterised by and ID, size and content.
+Each ME consists of an entry ID and zero, one or more instances. Each instance has its own ID, usually starting at 0, but this is not always the case. Every instance has one or more attributes, each characterised by ID, size and content.
 
-The various MEs are often interrelated. Clause 8.2 of [^G_988] and [^G_984_4] shows the relationship graphs between the various MEs.
+Various MEs are often interrelated. Clause 8.2 of [^G_988] and [^G_984_4] shows the relationship graphs between the various MEs.
 Clause 9 of [^G_988] and [^G_984_4] describes how the various MEs are created. There are formally 2 modes: a managed entity which is auto-instantiated by the ONT or a managed entity which is instantiated on explicit request by the OLT.
-In each of the 2 cases the various MEs can be: (R), (W). Only for ME auto-instantiated by the ONT there is also (R, W) while only for ME auto-instantiated by the OLT there are also (R, Set-by-create), (W, Set-by-create), or (R, W, Set-by-create).
+In each of the 2 cases the various MEs can be: (R), (W). Only for MEs auto-instantiated by the ONT there is also (R, W) while only for MEs auto-instantiated by the OLT there are also (R, Set-by-create), (W, Set-by-create), or (R, W, Set-by-create).
 
 | Mode                  | Description [^G_984_4]                                                                                                                                                                                                                                                                                                                                                    |
 | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/_gpon/ont.md b/_gpon/ont.md
index 84bb558..2e6e0f5 100644
--- a/_gpon/ont.md
+++ b/_gpon/ont.md
@@ -15,7 +15,7 @@ Currently, there are only a few main GPON chipset vendors:
         - RTL9601B  
         - RTL9601CI (HSGMII)
         - RTL9601D (HSGMII)
-    * RTL9602/RTL9603 series (for router with integrated PON)
+    * RTL9602/RTL9603 series (for routers with integrated PON)
     * Cortina QWCS8032E
 - Lantiq:
     * PEB98035 (HSGMII)
diff --git a/_gpon/pptp_veip.md b/_gpon/pptp_veip.md
index ad78ce0..f904abb 100644
--- a/_gpon/pptp_veip.md
+++ b/_gpon/pptp_veip.md
@@ -5,14 +5,14 @@ nav_order: 3
 layout: default
 ---
 
-ONTs are the terminating elements of the PON network, and play, like the ONT an essential role in the PON architecture. The ONT converts the optical media into an electrical interface and takes care of authenticating, monitoring, processing as well as managing all matters related to the GPON tree. Often these devices are installed directly in the home[^hsgp_hg_sfu].
+ONTs are the terminating elements of every PON network and play an essential role in the PON architecture. The ONT converts the optical media into an electrical interface and takes care of authenticating, monitoring, processing as well as managing all matters related to the GPON tree. Often these devices are installed directly in users' homes[^hsgp_hg_sfu].
 
 Three layers can be identified in the ONT: core layer, service layer and public layer.
 - The core layer provides multiplexing and the optical interface;
 - the service layer refers mainly to the user port;
 - the public layer provides power and maintenance management[^hsgp_hg_sfu].
 
-The ONT can connect to various terminal devices, such as set-top boxes, wireless routers, TVs, etc., and performs photoelectric conversion, maintenance and monitoring functions. According to the application, ONT can be divided into six types, namely[^hsgp_hg_sfu]:
+ONTs can connect to various terminal devices, such as set-top boxes, wireless routers, TVs, etc., and perform photoelectric conversion, maintenance and monitoring functions. According to the application, ONTs can be divided into six types, namely[^hsgp_hg_sfu]:
 - SFU (Single Family Unit) ONT
 - HGU (Home Gateway Unit) ONT 
 - MDU (Multi-Dwelling Unit) ONT 
@@ -20,23 +20,23 @@ The ONT can connect to various terminal devices, such as set-top boxes, wireless
 - MTU (Multi-Tenant Unit) ONT
 - CBU (Cellular Backhaul Unit) ONT
 
-However, only SFU (Single Family Unit) ONT and HGU (Home Gateway Unit) ONT are used by the end-users in practical application.
+However, only SFU ONTs and HGU ONTs are used by end-users in practical application.
 
-HGU ONT, is a home gateway with an uplink interface of the PON, is designed for the single home unit. HGU ONT integrates the functions of ONT and RG to realize more complex control and management and provide Ethernet / IP service, VoIP service, routing mode (firewall and NAT), and optional CATV service. HGU ONT has an Ethernet interface and POTS interface, WLAN interface, USB interface, CATV RF interface are also available. The HGU is a Layer III device[^hsgp_hg_sfu].
+HGU ONTs are a home gateway with a PON uplink interface; they're designed for use in single home units. HGU ONTs integrate the functions of ONTs and RGs to realize more complex control and management and also provide Ethernet / IP, VoIP, optional CATV services and routing mode (firewall and NAT). Usually HGU ONTs have Ethernet interfaces, but POTS, WLAN, USB and CATV RF interfaces are also available. The HGU is a Layer III device[^hsgp_hg_sfu].
 
-The ONT SFU type can be understood as a simple Layer II device, like an L2 switch or media converter, have a single port and are exclusively optical-electric converters. That simply transparently transports traffic from the PON to the eth port(s) of the customer ONT. No routing or VoIP functionality is assumed for the SFU type. For SFU, a simple service configuration from the OLT station is used. The cost of SFU device is cheaper, because additional services (routing, telephony, TV) are not implemented.
+The ONT SFU type can be understood as a simple Layer II device, like an L2 switch or media converter. It usually has a single Ethernet port and it is exclusively an optical-electric converter. It simply and transparently transports traffic from the PON interface to the Ethernet port(s) of the customer's ONT. No routing or VoIP functionality is assumed for this SFU type. For SFUs, a simple service configuration from the OLT station is used. SFU devices are usually cheaper, because additional services (routing, telephony, TV) are not implemented.
 
-Within the GPON OMCI standards we can find two types of interfaces, and they are relatively VEIP and PPTP. This virtual interface are the boundaries between the GPON/OMCI part and the non-GPON/Ethernet part[^G_984_4],[^G_988],[^hsgp_hg_sfu].
+Within the GPON OMCI standards we can find two types of interfaces: VEIP and PPTP. These virtual interfaces are the boundary between the GPON/OMCI part and the non-GPON/Ethernet part[^G_984_4],[^G_988],[^hsgp_hg_sfu].
 
-ONT will report VEIP or PPTP (Physical Path Termination Point) when MIB 11 oe 329 is uploaded according to the type of the device. Only one VEIP is allowed in a HGU and VEIP is not available for SFU devices. OLT determines the ONT type based on the ONT Type attribute in ME Capability.
+ONTs will report VEIP or PPTP (Physical Path Termination Point) when MIB 11 or 329 is uploaded according to the type of the device. Only one VEIP is allowed in a HGU and VEIP is not available for SFU devices. OLTs determine the ONT type based on the ONT Type attribute in ME Capability.
 
 # Physical Path Termination Point (PPTP/Ethernet UNI - MIB 11)
 
-PPTP/EthUni, on the other hand, is designed for transparent L2 bridges, potentially N each with its own VLAN. OLT is responsible to provision of VLAN and LAN Port[^nanomad_fc],[^anime_rtl960x].
+PPTP/EthUni, on the other hand, is designed for transparent L2 bridging, potentially each with its own VLAN. The OLT is responsible of the provisioning of VLANs and LAN Ports[^nanomad_fc],[^anime_rtl960x].
 
-The SFU type ONT device is configured and controlled completely remotely from the OLT via the OMCI management interface. Generally these devices do not require special configurations and therefore access to the web interface of the client ONT device is not required, although it is possible to update the software. To configure the switching of the required VLANs, the Ethernet port profiles of the client ONT are created at the OLT. Most of user-side configurations must be made in the devices connected to the SFU.
+The SFU type ONT device is configured and controlled completely remotely by the OLT via the OMCI management interface. Generally these devices do not require special configurations and therefore access to the web interface of the client ONT device is not required, although it is possible to update the software. To configure the switching of the required VLANs, the Ethernet port profiles of the client ONT are created at the OLT. Most user-side configurations must be made in the devices connected to the SFU.
 
-For OMCI data flow, there is a mutually unambiguous mapping between the GEM port on the OLT side with the UNI Ethernet port on the terminal side of the ONT. All data packets can pass through without learning or forwarding the MAC address. The SFU ONT supports multiple VLAN function through bridge mode.
+For OMCI data flow, there is a mutually unambiguous mapping between the GEM port on the OLT side with the UNI Ethernet port on the terminal side of the ONT. All data packets can pass through without learning or forwarding the MAC address. SFU ONTs support multiple VLANs through bridge mode.
 
 ```mermaid
 flowchart LR
@@ -80,13 +80,13 @@ ExtVlan --> PPTP
 ```
 Source [^cablefax_future], [^G_988]
 
-# Virtual Ethernet interface point (VEIP - MIB 329)
+# Virtual Ethernet Interface Point (VEIP - MIB 329)
 
-VEIP is a service profile designed to terminate the connection directly on the CPE, providing N services (voice, data, video) each with its own characteristics. Allows multiple Ethernet services to be carried over a single PON link. VEIP virtualises all interfaces of the ONU.
+VEIP is a service profile designed to terminate the connection directly on the CPE, providing various services (voice, data, video) each with its own characteristics. It allows multiple Ethernet services to be carried over a single PON link. VEIP virtualises all interfaces of the ONU.
 
-Similarly, all UNI-side modules within a VEIP are invisible to and cannot be managed by the OMCI or the user. They are only visible and manageable to a management domain other than OMCI. In addition, each ONT must have only one VEIP.
+Similarly, all UNI-side modules within a VEIP are invisible to and cannot be managed by OMCI or the user. They are only visible and manageable to a management domain other than OMCI. In addition, each ONT must have only one VEIP.
 
-In some countries, it is also used to allow quick switches between ISPs, ISP A is assigned Ethernet port 1 of the HGU, ISP B is assigned Ethernet port 2 of the HGU, and so on[^nanomad_fc],[^anime_rtl960x],[^huawei_veip].
+In some countries, it is also used to allow quick switches between ISPs: ISP A is assigned to Ethernet port 1 of the HGU, ISP B is assigned to Ethernet port 2 of the HGU, and so on[^nanomad_fc],[^anime_rtl960x],[^huawei_veip].
 
 
 ```mermaid
diff --git a/_gpon/vendor.md b/_gpon/vendor.md
index f1064e0..b8db0da 100644
--- a/_gpon/vendor.md
+++ b/_gpon/vendor.md
@@ -5,7 +5,7 @@ nav_order: 4
 layout: default
 ---
 
-> 4 ASCII character
+> 4 ASCII characters
 
 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`.
 
@@ -42,4 +42,4 @@ Here is a list of the most popular Vendor IDs:
 | `ZTEG` | `5a544547` | ZTE                  |
 | `ZYWN` | `5a59574e` | Zyxel                |
 
-{% include alert.html content="You can also help us with the content of this site, on each page you will find a button to edit on GitHub." alert="Tip"  icon="svg-info" color="green" %}
+{% include alert.html content="You can also help us with adding content to this site, you can find a button to edit on GitHub on each page." alert="Tip"  icon="svg-info" color="green" %}