Merge pull request #210 from boucadair/handoff-clarification

handoff clarification

draft-ietf-teas-5g-ns-ip-mpls.md

@@ -204,7 +204,7 @@ The realization approach described in this document is typically triggered by Ne
 
 The 5G control plane uses the Single Network Slice Selection Assistance Information (S-NSSAI) for slice
 identification {{TS-23.501}}. Because S-NSSAIs are not visible to the transport domain, 5G domains can expose the 5G slices to the transport
-domain by mapping to explicit data plane identifiers (e.g., Layer 2, Layer 3, or Layer 4). The realization of the mapping between customer sites and provider networks is refered to as the "hand-off". {{sec-handoff-domains}} lists a set of such hand-off methods.
+domain by mapping to explicit data plane identifiers (e.g., Layer 2, Layer 3, or Layer 4). Passing information between customer sites and provider networks is referred to as the "hand-off". {{sec-handoff-domains}} lists a set of hand-off methods for slice mapping purposes.
 
 The realization model described in this document uses a set of building blocks commonly used in service provider networks. Concretely, the model uses (1) Layer 2 Virtual Private Network (L2VPN) {{?RFC4664}} and/or Layer 3 Virtual Private Network (L3VPN) {{?RFC4364}} service instances for logical separation, (2) fine-grained resource control at the Provider Edges (PEs), (3) coarse-grained resource control within the provider network, and (4) capacity management. More details are provided in Sections {{<sec-over-rea-model}}, {{<sec-qos-map}}, {{<transport-plane-mapping-models}}, and {{<sec-capacity-planning}}.
 
@@ -592,7 +592,7 @@ This document does not describe in detail how to manage an L2VPN or L3VPN, as th
    identification. The S-NSSAI is not visible to the transport domain.
    So instead, 5G network functions can expose the 5G slices to the transport
    domain by mapping to explicit Layer 2 or Layer 3 identifiers, such as VLAN-IDs, IP
-   addresses, or Differentiated Services Code Point (DSCP) values. These section lists few hand-off methods for slice mapping
+   addresses, or Differentiated Services Code Point (DSCP) values. The following sections list few hand-off methods for slice mapping
    between customer sites and provider networks.
 
    More details about the mapping between 3GPP and RFC 9543 Network Slices is provided in {{?I-D.ietf-teas-5g-network-slice-application}}.