Merge pull request #249743 from JonathanSaraco/jsaraco/removeMapsRequirement

Remove MAPS technical requirement from walkthroughs

Author: prmerger-automator[bot]

articles/internet-peering/walkthrough-communications-services-partner.md

@@ -28,8 +28,7 @@ To establish direct interconnect for Peering Service Voice Services, follow thes
 
 -	The Peer MUST provide its own Autonomous System Number (ASN), which MUST be public.
 -	The Peer MUST have redundant Interconnect (PNI) at each interconnect location to ensure local redundancy.
--	The Peer MUST supply and advertise their own publicly routable IPv4 address space used by Peer's endpoints (for example, SBC). 
--	The Peer MUST supply detail of what class of traffic and endpoints are housed in each advertised subnet.
+-	The Peer MUST supply and advertise their own publicly routable IPv4 address space used by Peer's endpoints (for example, SBC).
 -	The Peer MUST run BGP over Bidirectional Forwarding Detection (BFD) to facilitate subsecond route convergence.
 -	The Peer MUST NOT terminate the peering on a device running a stateful firewall.
 -	The Peer CANNOT have two local connections configured on the same router, as diversity is required

articles/internet-peering/walkthrough-exchange-route-server-partner.md

@@ -26,8 +26,7 @@ To establish a Peering Service Exchange with Route Server peering, follow these
 
 -	The Peer MUST provide its own Autonomous System Number (ASN), which MUST be public.
 -	The Peer MUST have redundant Interconnect (PNI) at each interconnect location to ensure local redundancy.
--	The Peer MUST supply and advertise their own publicly routable IPv4 address space used by Peer's endpoints (for example, SBC). 
--	The Peer MUST supply detail of what class of traffic and endpoints are housed in each advertised subnet.
+-	The Peer MUST supply and advertise their own publicly routable IPv4 address space used by Peer's endpoints (for example, SBC).
 -	The Peer MUST NOT terminate the peering on a device running a stateful firewall.
 -	The Peer CANNOT have two local connections configured on the same router, as diversity is required
 -   The Peer CANNOT apply rate limiting to their connection

articles/internet-peering/walkthrough-peering-service-all.md

@@ -26,8 +26,7 @@ To establish direct interconnect for Peering Service, follow these requirements:
 
 -	The Peer MUST provide its own Autonomous System Number (ASN), which MUST be public.
 -	The Peer MUST have redundant Interconnect (PNI) at each interconnect location to ensure local redundancy.
--	The Peer MUST supply and advertise their own publicly routable IPv4 address space used by Peer's endpoints. 
--	The Peer MUST supply detail of what class of traffic and endpoints are housed in each advertised subnet.
+-	The Peer MUST supply and advertise their own publicly routable IPv4 address space used by Peer's endpoints.
 -	The Peer MUST NOT terminate the peering on a device running a stateful firewall.
 -	The Peer CANNOT have two local connections configured on the same router, as diversity is required.
 -   The Peer CANNOT apply rate limiting to their connection.