[MT] Clarified language around BGP prefix advertisement (#20675)

* clarified language

* clarified language for bgp

* added optional to title

* deleted outdated image

* clarified bgp peering

* refined text

Author: marciocloudflare

src/assets/images/magic-transit/bgp-diagram.png

@@ -30,7 +30,7 @@ List all prefixes and the [autonomous systems (ASNs)](https://www.cloudflare.com
 
 ## Cloudflare ASN vs. your own ASN
 
-When customers supply their own ASN, Cloudflare prepends the main Cloudflare ASN (AS13335) to the BGP `AS_PATH`. For example, if the customer ASN is AS64496, anyone directly peering with Cloudflare sees the path as `13335 64496`.
+As a part of your onboarding process, you need to decide the ASN Cloudflare will use to announce your prefixes. If you supply your own ASN, Cloudflare prepends the main Cloudflare ASN (AS13335) to the BGP `AS_PATH`. For example, if your ASN is `AS64496`, anyone directly peering with Cloudflare sees the path as `13335 64496`.
 
 If you do not have an ASN or do not want to bring your ASN to Cloudflare, you can use the Cloudflare Customer ASN (AS13335).
 
@@ -69,14 +69,12 @@ You can only delete a prefix with an **Unapproved** status. To delete prefixes w
 1. From the **IP Prefixes** tab, locate the prefix you want to modify and select **Delete**.
 2. Confirm your choice from the modal by selecting **Delete**.
 
-## Border Gateway Protocol (BGP) control for advertisements
+## Border Gateway Protocol (BGP) control for advertisements (optional)
 
-Use BGP to control the advertisement status of your prefix - advertised or withdrawn - from Cloudflare's global network for on-demand deployment scenarios. BGP Control works by establishing BGP sessions to Cloudflare's globally distributed Route Reflectors, which will initiate propagation of your prefix advertisement across Cloudflare's global network.
+Optionally, you can use BGP to control the advertisement status of your prefix — advertised or withdrawn — from Cloudflare's global network for on-demand deployment scenarios. BGP Control works by establishing BGP sessions to Cloudflare's globally distributed Route Reflectors, which will initiate propagation of your prefix advertisement across Cloudflare's global network.
 
 Prefixes can be advertised from Cloudflare's network in a supported on-demand method such as BGP Control, or dynamically via the UI, API, or [Magic Network Monitoring](/magic-transit/magic-network-monitoring/). During the onboarding of your on-demand prefixes, please specify whether you want BGP-controlled advertisement or dynamic advertisement (via dashboard/API/Magic Network Monitoring).
 
-![BGP diagram for Magic Transit](~/assets/images/magic-transit/bgp-diagram.png)
-
 To begin using BGP control, contact your account team with the following information:
 
 - BGP endpoint IP addresses
@@ -91,7 +89,7 @@ When you withdraw a prefix using BGP, you must ensure the prefix is withdrawn ac
 
 ### BGP peering
 
-If you use Direct CNI as a way to on-ramp your network traffic to Magic Transit, refer to [BGP peering](/magic-transit/how-to/bgp-peering/) to learn how to configure BGP peering.
+If you use Direct CNI as a way to on-ramp your network traffic to Magic Transit, refer to [BGP peering](/magic-transit/how-to/bgp-peering/) to learn how to use BGP to handle traffic routing between Cloudflare and your network. Note that this is a different option to using BGP as a means to control the advertisement status of your prefix.
 
 
 ### Regional settings