Change:
A few document nits… Section 2, 1st and 2nd Sentences “in satellite system” should be “in a satellite system”. Not clear what “lays” means here. “multi-gateway satellites network” should be “multi-gateway satellite network”. (Most of the uses cases have nothing to do with multi-gateway, though.) Section 3, 2nd Sentence Delete the duplicate “where”. Section 6, 2nd Sentence “that the some scenarios” should be “that some scenarios”.
Thanks for having identified the NITS. Closed by PR

Discussion:
2. <del> This section describes the components in satellite system that lays on SATCOM systems dedicated to broadband Internet access that follows </del> <ins> This section describes the components in a satellite system based on SATCOM systems dedicated to broadband Internet access that follows </ins> the DVB standards.  A high-level description of a multi-gateway <del> satellites network is provided.  There are multiple SATCOM systems, </del> <ins> satellite network is provided.  There are multiple SATCOM systems, </ins> such as those dedicated to broadcasting TV or to IoT applications: depending on the purpose of the SATCOM system, ground segments are specific.  In this context, the increase of the available capacity

RFC8406: End-to-End Coding (E2E), Network Coding (NC), Intra-Flow Coding (IntraF), Inter-Flow Coding (InterF), Single-Path Coding (SPC) and Multi-Path Coding (MPC).  This document refers to coding as both <del> End-to-End Coding and Network Coding, to cover cases where where recoding operation at intermediate nodes are or not.  From the UDP/IP </del> <ins> End-to-End Coding and Network Coding, to cover cases where recoding operation at intermediate nodes are or not.  From the UDP/IP </ins> packetization to the channel coding, link layer coding is required so that the physical-layer knows what coding scheme to use.  Following the taxonomy document RFC8406, channel and link codings are gathered

techniques at a wider scale in satellite telecommunications systems. Even though this document focuses on satellite systems, it is worth <del> pointing out that the some scenarios proposed may be relevant to other wireless telecommunication systems.  As one example, the generic architecture proposed in fig:sat_gateway may be mapped to cellular networks as follows: the 'network function' block gather some of the functions of the Evolved Packet Core subsystem, while the 'access gateway' and 'physical gateway' blocks gather the same type of functions as the Universal Mobile Terrestrial Radio Access Network.  This mapping extends the opportunities identified in this draft since they may be also relevant for cellular networks. </del> <ins> pointing out that some scenarios proposed may be relevant to other wireless telecommunication systems.  As one example, the generic architecture proposed in fig:sat_gateway may be mapped to cellular networks as follows: the 'network function' block gather some of the functions of the Evolved Packet Core subsystem, while the 'access gateway' and 'physical gateway' blocks gather the same type of functions as the Universal Mobile Terrestrial Radio Access Network. This mapping extends the opportunities identified in this draft since they may be also relevant for cellular networks. </ins> 7.