Merge pull request #212 from boucadair/boucadair-patch-1

consistent use of capacity planning/management

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

@@ -199,7 +199,7 @@ The 5G control plane uses the Single Network Slice Selection Assistance Informat
 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). 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}}.
+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 planning/management. More details are provided in Sections {{<sec-over-rea-model}}, {{<sec-qos-map}}, {{<transport-plane-mapping-models}}, and {{<sec-capacity-planning}}.
 
 This realization model uses a single Network Resource Partition (NRP) ({{Section 7.1 of !RFC9543}}). The applicability to multiple NRPs is out of scope.
 
@@ -563,7 +563,7 @@ TN slice mapping policies can be enforced by an operator (e.g., provided to a TN
 
    *  Capacity planning/management for efficient usage of provider network resources:
 
-      The role of capacity management is to ensure the provider network
+      The role of capacity planning/management is to ensure the provider network
       capacity can be utilized without causing any bottlenecks.  The
       methods used here can range from careful network planning, to
       ensure a more or less equal traffic distribution (i.e., equal cost load