Merge pull request #287959 from halkazwini/ps-connection

Peering Service | Maintenance | Freshness: Peering Service connection

Author: prmerger-automator[bot]

articles/peering-service/connection.md

@@ -5,35 +5,35 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-peering-service
 ms.topic: concept-article
-ms.date: 07/23/2023
+ms.date: 10/07/2024
 ---
 
 # Peering Service connection
 
 A connection typically refers to a logical information set, identifying a Peering Service. It's defined by specifying the following attributes:
 
-- Logical Name
+- Logical name
 - Connectivity partner
 - Connectivity partner Primary service location
 - Connectivity partner Backup service location
 - IP prefixes
 
-Customer can establish a single connection or multiple connections as per the requirement. A connection is also used as a unit of telemetry collection. For instance, to opt for telemetry alerts, customer must define the connection that will be monitored.
+Customer can establish a single connection or multiple connections as per the requirement. A connection is also used as a unit of telemetry collection. For instance, to opt for telemetry alerts, you must define the connection that you want to monitor.
 
 > [!NOTE]
 > When you sign up for Peering Service, we analyze your Windows and Microsoft 365 telemetry in order to provide you with latency measurements for your selected prefixes.
 > For more information about connection telemetry, see [Access Peering Service connection telemetry](connection-telemetry.md).
 
 ## How to create a peering service connection?
 
-**Scenario** - Let's say a branch office is spread across different geographic locations as shown in the figure. Here, the customer is required to provide a logical name, Service Provider (SP) name, customer's physical location, and IP prefixes that are (owned by the customer or allocated by the Service Provider) associated with a single connection.  The primary and backup service locations with partner help defining the preferred service location for customer. This process must be repeated to create Peering Service for other locations.
+**Scenario** - Let's say a branch office is spread across different geographic locations as shown in the figure. Here, the customer is required to provide a logical name, Service Provider (SP) name, customer's physical location, and IP prefixes that are (owned by the customer or allocated by the Service Provider) associated with a single connection. The primary and backup service locations with partner help defining the preferred service location for customer. This process must be repeated to create Peering Service for other locations.
 
 :::image type="content" source="./media/connection/peering-service-connections.png" alt-text="Diagram shows geo redundant connections.":::
 
 > [!NOTE]
 > State level-filtration is considered for the customer's physical location when the connection is geo-located in the United States.
 
-## Next steps
+## Related content
 
 - To learn how to register Peering Service connection, see [Create Peering Service using the Azure portal](azure-portal.md).
 - To learn about Peering Service connection telemetry, see [Access Peering Service connection telemetry](connection-telemetry.md).