Use h3s and horizontal lines for better skimmability

Author: RebeccaTamachiro

src/content/docs/byoip/get-started.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { APIRequest, Tabs, TabItem } from "~/components";
+import { APIRequest, Tabs, TabItem, GlossaryDefinition } from "~/components";
 
 Work with your account team to make sure your contract covers everything you need to onboard your prefix. Cloudflare requires service-specific configurations, as well as some requirements common to all BYOIP customers.
 
@@ -34,9 +34,13 @@ Once your account configurations are in place, consider the sections below to le
 
 - If you are not familiar with how Cloudflare API works, refer to [Fundamentals](/fundamentals/api/). Make sure you have the necessary permissions and that you have your account ID.
 
+---
+
 ## 1. Set up your prefixes
 
-1. Use the [Add Prefix endpoint](/api/resources/addressing/subresources/prefixes/methods/create/) to create a prefix in the Cloudflare account that should own the BYOIP prefix.
+### Add your prefix
+
+Use the [Add Prefix endpoint](/api/resources/addressing/subresources/prefixes/methods/create/) to create a prefix in the Cloudflare account that should own the BYOIP prefix.
 
 ```bash
 curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/addressing/prefixes \
@@ -76,7 +80,10 @@ curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/addressing/prefix
 ```
 
 2. Take note of the `id` assigned to the prefix you added. It will be used in future steps.
-3. Validate prefix ownership using one of the following methods:
+
+### Validate prefix ownership
+
+Validate prefix ownership using one of the following methods:
 
 <Tabs> <TabItem label="Modify IRR record">
 
@@ -116,7 +123,7 @@ Once the ownership validation is successful, you can remove the token.
 
 When all validations pass - RPKI, IRR, and ownership - the `approved` field in your prefix will return `"V"`. This means you can proceed to create IP address service bindings[^1].
 
-3. (Optional) Use the [Prefix Details endpoint](/api/resources/addressing/subresources/prefixes/methods/get/) to check if any issues were found during validation. If so, proceed with the necessary changes and make a request to restart validation.
+If needed, you can use the [Prefix Details endpoint](/api/resources/addressing/subresources/prefixes/methods/get/) to check if any issues were found during validation. If so, proceed with the necessary changes and make a request to restart validation.
 <APIRequest path= "/accounts/{account_id}/addressing/prefixes/{prefix_id}" method="GET" />
 
    (WIP - Add response example (collapsable))
@@ -125,7 +132,9 @@ When all validations pass - RPKI, IRR, and ownership - the `approved` field in y
 
 (WIP - Clarify criteria for IRR check + further info like schedule and limits?)
 
-4. (Optional) You can allow other accounts to use part or all of your BYOIP prefix. Refer to [Prefix delegations](/byoip/concepts/prefix-delegations/) for details.
+### (Optional) Delegate your BYOIP prefixes
+
+You can allow other accounts to use part or all of your BYOIP prefix. Refer to [Prefix delegations](/byoip/concepts/prefix-delegations/) for details.
 
 <APIRequest
 path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/delegations"
@@ -140,7 +149,13 @@ json={{
 Although you can delegate IPs to other accounts, the IP address service bindings are still created and managed on the parent account - meaning the Cloudflare account where you added the prefix in step 1.
 :::
 
-## 2. Create a default service binding
+---
+
+## 2. Create service bindings
+
+In IP address management, service bindings map the traffic destined for a given IP address to the Cloudflare service that it should be routed through.
+
+### Default service binding
 
 When you onboard your IP prefixes to Cloudflare, there must be one service binding that spans across your entire prefix. Traffic destined for a given IP address will be routed to this service by default. You can also configure [additional service bindings](#optional-additional-bindings) as described in the next step.
 
@@ -169,10 +184,10 @@ For Magic Transit customers, the BGP prefix will be created in a `locked` state.
 
 ### (Optional) Additional bindings
 
-If you want to selectively route traffic on a per-IP address basis to CDN or Spectrum, you can create additional service bindings.
+If you want to selectively route traffic on a per-IP address basis to CDN or Spectrum, you can create additional service bindings. Magic Transit can only be used as default binding, spanning across your entire prefix.
 
 :::note
-The steps below only cover assigning specific IPs to additional services. For guidance that includes CDN or Spectrum setup steps, refer to [Service bindings](https://developers.cloudflare.com/byoip/service-bindings/).
+The steps below only cover assigning specific IPs to additional services. For guidance that includes CDN or Spectrum setup steps, refer to [Service bindings](/byoip/service-bindings/).
 :::
 
 1. Plan for what IP(s) will get the additional binding. Cloudflare **strongly** recommends implementing service bindings through an **aggregated** CIDR block, as it is more efficient than adding discrete bindings for non-contiguous CIDR blocks.
@@ -206,6 +221,8 @@ In the response body, the initial provisioning state should be `provisioning`.
 
 Once a service binding is created (or deleted), it will take **four to six hours** to propagate across Cloudflare's global network.
 
+---
+
 ## 3. Advertise the BGP prefix
 
 Once created, BGP prefixes are initially withdrawn. After all your configurations are in place - including address maps[^2] if you will use CDN service -, proceed to advertise the BGP route for your prefix.