diff --git a/articles/traffic-manager/traffic-manager-monitoring.md b/articles/traffic-manager/traffic-manager-monitoring.md
index 3c4e019ea0cec..7f7238c82e5a6 100644
--- a/articles/traffic-manager/traffic-manager-monitoring.md
+++ b/articles/traffic-manager/traffic-manager-monitoring.md
@@ -197,11 +197,11 @@ See the following example:
 > - Endpoints that are configured to always serve traffic are billed for [basic health checks](https://azure.microsoft.com/pricing/details/traffic-manager/).
 
 > [!NOTE]
-> Azure Traffic Manager health probes are designed to monitor endpoints that are reachable by the Traffic Manager probing infrastructure. Traffic Manager isn't designed to probe endpoints that resolve to addresses within private, non-routable, or Microsoft-internal network spaces.
+> Azure Traffic Manager health probes are designed to monitor endpoints that are reachable by the Traffic Manager probing infrastructure. Traffic Manager isn't designed to probe endpoints that resolve to addresses within private network spaces.
 > 
-> Endpoints that resolve to addresses within these network spaces **must be configured as Always serve traffic endpoints**. Traffic Manager can't perform health validation for these endpoints and therefore can't provide health-based failover.
+> Endpoints that resolve to addresses within these network spaces **must be configured as Always Serve endpoints**. Traffic Manager can't perform health validation for these endpoints and therefore can't provide health-based failover.
 > 
-> To ensure consistent behavior, Traffic Manager enforces the **Always serve traffic** configuration for endpoints that resolve to addresses within unsupported network spaces.
+> To ensure consistent behavior, Traffic Manager enforces the **Always Serve** configuration for endpoints that resolve to addresses within unsupported network spaces.
 
 ## Firewall Setup for Health Checks