[MT] Language improvements (#27010)

* refined description

* refined text

* refined text

* refined text

* refined text

* title

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* refined text

* Apply suggestions from code review

Co-authored-by: Pedro Sousa <[email protected]>

---------

Co-authored-by: Pedro Sousa <[email protected]>

Author: marciocloudflare

src/content/docs/magic-transit/analytics/index.mdx

@@ -4,8 +4,7 @@ pcx_content_type: how-to
 sidebar:
   order: 9
 head: []
-description: Use Magic Transit's different analytic options for an overview of
-  the performance of your sites, or to troubleshoot potential issues.
+description: Use Magic Transit analytics to monitor network performance and troubleshoot potential issues.
 
 ---
 

src/content/docs/magic-transit/analytics/query-bandwidth.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Querying Magic Transit tunnel bandwidth analytics with GraphQL
+title: Query Magic Transit tunnel bandwidth analytics with GraphQL
 sidebar:
   order: 5
 

src/content/docs/magic-transit/analytics/query-tunnel-health.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Querying Magic Transit tunnel health check results with GraphQL
+title: Query Magic Transit tunnel health check results with GraphQL
 sidebar:
   order: 6
 

src/content/docs/magic-transit/how-to/advertise-prefixes.mdx

@@ -11,18 +11,18 @@ import { APIRequest, Details, GlossaryTooltip, Render, Tabs, TabItem, DashButton
 
 You can bring your own public IPs to Cloudflare to use with Magic Transit. This process requires two steps:
 
-1. Add IP <GlossaryTooltip term="prefix">prefixes</GlossaryTooltip> for each IP address block that you bring to Cloudflare. The IP prefix includes the permission (<GlossaryTooltip term="letter of agency">Letter of Agency or LOA</GlossaryTooltip>) that allows Cloudflare to announce the network or its subnets. The IP prefix is also where you define your optional [Autonomous System Number (ASN)](https://www.cloudflare.com/learning/network-layer/what-is-an-autonomous-system/) to be included in Cloudflare's advertised AS path.
-2. Define additional BGP prefixes, which control the announcement of the prefix from Cloudflare. By default there is always one BGP prefix that is identical to the IP prefix. You can optionally configure additional, more-specific BGP prefixes (subnets of the IP prefix), up to a maximum prefix length of `/24`.
+1. Add IP <GlossaryTooltip term="prefix">prefixes</GlossaryTooltip> for each IP address block that you bring to Cloudflare. The IP prefix includes the permission (<GlossaryTooltip term="letter of agency">Letter of Agency or LOA</GlossaryTooltip>) that allows Cloudflare to announce the network or its subnets. You can also define your optional [Autonomous System Number (ASN)](https://www.cloudflare.com/learning/network-layer/what-is-an-autonomous-system/) to be included in Cloudflare's advertised AS path.
+2. Define additional BGP prefixes, which control the announcement of the prefix from Cloudflare. By default, there is always one BGP prefix that is identical to the IP prefix. You can optionally configure additional, more-specific BGP prefixes (subnets of the IP prefix), up to a maximum prefix length of `/24`.
 
 ### IP prefixes
 
 Cloudflare measures the Magic Transit prefix count based on the number of BGP prefixes a customer defines. Each prefix is billed separately, even if they overlap. For example, both a `/16` and any `/24` within it are counted individually. Onboarding a larger aggregate prefix does not automatically include its smaller subnets for announcement or billing purposes.
 
-While there is no billing limit on the accepted prefix sizes, technically only prefixes up to `/24` are accepted for onboarding, as longer ones (like `/25`, `/26`) are not globally routable.
+There is no billing limit on the accepted prefix sizes. However, only prefixes up to `/24` are accepted for onboarding because longer prefixes (like `/25`, `/26`) are not globally routable.
 
 Provide all IP prefixes you plan to onboard, along with the ASNs from which they will be advertised. When specifying prefixes, observe these guidelines:
 
-- Prefixes must support at least 256 hosts (`/24` in classless inter-domain [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) CIDR notation). Refer to [Use a Cloudflare IP](/magic-transit/cloudflare-ips/) if you do not meet the `/24` prefix length requirement.
+- Prefixes must support at least 256 hosts (`/24` in CIDR ([Classless Inter-Domain Routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/)) notation). If you do not meet the `/24` prefix length requirement, refer to [Use a Cloudflare IP](/magic-transit/cloudflare-ips/).
 - Internet Routing Registry entries and Letters of Agency (LOA) must match the prefixes and originating prefixes you submit to Cloudflare.
 - When using contiguous prefixes, specify aggregate prefixes where possible.
 - When using Route Origin Authorizations (ROAs) to sign routes for [resource public key infrastructure (RPKI)](https://tools.ietf.org/html/rfc8210), the prefix and originating ASN must match the onboarding submission.
@@ -88,8 +88,8 @@ Create a [POST request](/api/resources/addressing/subresources/prefixes/subresou
 
 		<DashButton url="/?to=/:account/magic-transit/configuration" />
 
-		2. From the **IP Prefixes** tab, select the prefix you want to modify > **Edit**.
-		3. From the dropdown menu **Status**, choose whether the status of your IP is **Advertised** or **Withdrawn**.
+		2. From the **IP Prefixes** tab, select the prefix to modify > **Edit**.
+		3. From the **Status** drop-down menu, choose **Advertised** or **Withdrawn**.
 		4. (Optional) Edit the description for your prefix.
 		5. Select **Edit IP Prefix** to save your changes.
   </TabItem>
@@ -133,7 +133,7 @@ json={{
 }}
 />
 
-AS prepending helps you gracefully transition traffic between network providers. By adding prepends to Cloudflare's advertisement, you make the route through Cloudflare less preferred for some Internet network providers. This allows you to simultaneously advertise the same prefix from an alternate provider with a shorter, more desirable `AS_PATH`. Advertising from both providers at once can provide a smoother traffic migration and minimize packet loss during a change of provider.
+AS prepending helps you gracefully transition traffic between network providers. By adding prepends to Cloudflare's advertisement, you make the route through Cloudflare less preferred for some Internet network providers. This allows you to simultaneously advertise the same prefix from an alternate provider with a shorter, more desirable `AS_PATH`. Advertising from both providers at once provides a smoother traffic migration and minimizes packet loss during a change of provider.
 
 The `"asn_prepend_count"` parameter accepts values from `0` to `3`. A higher value makes the route less preferred.  This parameter can also be changed using BGP — refer to [Use communities to set AS prepends on an anycast prefix](#use-communities-to-set-as-prepends-on-an-anycast-prefix).
 
@@ -145,7 +145,7 @@ When you use AS prepending to migrate traffic away from Magic Transit, the typic
 - **Final state**: External networks now receive two advertisements: the prepended route through Cloudflare and the non-prepended route through your new provider. The external network will select a path based on its BGP policy rules.
 
 :::caution
-BGP has different mechanisms to control route priorities which are set by the peered network, not by Cloudflare. As such, this is a best effort feature. Cloudflare cannot guarantee that peers will honor AS prepends on Cloudflare's transit and peering connections.
+BGP has different mechanisms to control route priorities which are set by the peered network, not by Cloudflare. As such, this is a best-effort feature. Cloudflare cannot guarantee that peers will honor AS prepends on Cloudflare's transit and peering connections.
 :::
 
 :::caution

src/content/docs/magic-transit/how-to/configure-routes.mdx

@@ -4,7 +4,7 @@ title: Configure routes
 sidebar:
   order: 2
 head: []
-description: Magic Transit uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through Direct CNI you also have access to BGP peering. Learn how to configure routing.
+description: Magic Transit uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through Direct CNI, you also have access to BGP peering.
 
 ---
 

src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx

@@ -4,9 +4,7 @@ title: Configure tunnel endpoints
 sidebar:
   order: 1
 head: []
-description: Cloudflare recommends two tunnels for each ISP and network location
-  router combination, one per Cloudflare endpoint. Learn how to configure IPsec
-  or GRE tunnels.
+description: Cloudflare recommends two tunnels for each ISP and network location router combination, one per Cloudflare endpoint. Learn how to configure IPsec or GRE tunnels.
 ---
 
 import { Render } from "~/components";
@@ -30,4 +28,4 @@ import { Render } from "~/components";
 
 ## Next steps
 
-Now that you have set up your tunnel endpoints, you need to configure routes to route your traffic through Cloudflare. Refer to [Configure routes](/magic-transit/how-to/configure-routes/) to learn more about static routing and BGP peering (only available through Direct CNI connection).
+Now that you have set up your tunnel endpoints, configure routes to direct your traffic through Cloudflare. Refer to [Configure routes](/magic-transit/how-to/configure-routes/) to learn more about static routing and BGP peering (only available through Direct CNI connection).

src/content/docs/magic-transit/how-to/enable-magic-roles.mdx

@@ -2,8 +2,7 @@
 pcx_content_type: how-to
 title: Enable Magic user roles
 head: []
-description: You can determine which users have, or do not have, configuration
-  edit access for Magic products.
+description: You can determine which users have, or do not have, configuration edit access for Magic products.
 ---
 
 import { Render } from "~/components"

src/content/docs/magic-transit/how-to/ipv6.mdx

@@ -25,18 +25,18 @@ Cloudflare transports IPv6 traffic over an IPv6-over-IPv4 GRE tunnel. Here is ho
 
 ## Current known limitations
 
-- The IPv6 beta is not available for accounts with CNI links configured.
-- MTU is 1420 bytes for egress traffic (does not impact Direct Server Return).
+- The IPv6 beta is not available for accounts with CNI (Cloudflare Network Interconnect) links configured.
+- MTU (Maximum Transmission Unit) is 1,420 bytes for egress traffic (does not impact Direct Server Return).
 - Magic Firewall supports two matching fields for IPv6 traffic: source IP address and destination IP address.
 - Cloudflare supports the advertisement of IPv6 prefixes ranging from `/48` to `/32`.
 - Limited to IPv4-based [tunnel health checks](/magic-transit/reference/tunnel-health-checks/) only.
 - Supports only IPv4-based endpoint health checks.
 
 ## How to configure IPv6
 
-Since IPv6 works over an existing IPv4 tunnel you will need to choose either an existing IPv4 GRE tunnel or create a new one to test IPv6. All settings that apply to the IPv4 GRE tunnel apply to the IPv6 tunnel as well, except for any MSS clamping you might need to configure — refer to [MSS clamping recommendations](#mss-clamping-recommendations) below for more information.
+Since IPv6 works over an existing IPv4 tunnel, you need to choose either an existing IPv4 GRE tunnel or create a new one to test IPv6. All settings that apply to the IPv4 GRE tunnel apply to the IPv6 tunnel as well, except for any MSS clamping you might need to configure — refer to [MSS clamping recommendations](#mss-clamping-recommendations) below for more information.
 
-To test and set up IPv6 in the Cloudflare dashboard there is only one new field you need to fill out when creating a new IPv4 GRE tunnel or editing an existing one: **IPv6 Interface address**. This is where you enter the Cloudflare-assigned IPv6 address for the Cloudflare side of the tunnel. Each tunnel is assigned a `/127` subnet from your allocated `/96` range. You will configure one address on the Cloudflare side and the other address on your router.
+To test and set up IPv6 in the Cloudflare dashboard, complete one new field when creating a new IPv4 GRE tunnel or editing an existing one: **IPv6 Interface address**. Enter the Cloudflare-assigned IPv6 address for the Cloudflare side of the tunnel. Each tunnel is assigned a `/127` subnet from your allocated `/96` range. You configure one address on the Cloudflare side and the other address on your router.
 
 :::caution
 Cloudflare allocates a `/96` IPv6 prefix for each account. The first two addresses in this range are reserved for Cloudflare. The remaining addresses are available for customer GRE tunnels, starting from `:2`, with two IPv6 addresses assigned per tunnel.
@@ -66,4 +66,4 @@ After the first two reserved addresses, you can continue allocating `/127` subne
 
 ### MSS clamping recommendations
 
-Customers using Magic Transit ingress-only traffic (DSR) should apply a TCP MSS clamp with a maximum of 1,416 bytes to their edge router's transit ports to account for the larger IPv6 header.
+If you use Magic Transit ingress-only traffic (DSR), apply a TCP MSS (Maximum Segment Size) clamp with a maximum of 1,416 bytes to your edge router's transit ports to account for the larger IPv6 header.