Adjust formatting and add accepted RIRs list

Author: RebeccaTamachiro

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

@@ -13,26 +13,44 @@ Once your account configurations are in place, consider the sections below to le
 
 ## Before you begin
 
-* Verify that your [Internet Routing Registry (IRR)](/byoip/concepts/irr-entries/) records are up to date and contain:
+- Your prefix must be registered under one of the following Regional Internet Registries (RIRs):
 
-    * `route` or `route6` objects matching the exact prefixes you want to onboard
-    * `origin` matching the correct ASN you want to onboard
+		- ARIN
+		- RIPE
+		- APNIC
+		- AFRINIC
+		- LACNIC
+
+- Also verify that your [Internet Routing Registry (IRR)](/byoip/concepts/irr-entries/) records are  are up to date and contain:
+
+    - `route` or `route6` objects matching the exact prefixes you want to onboard
+    - `origin` matching the correct ASN you want to onboard
 
     :::note
     The process described on this page only supports using Cloudflare's ASN (AS13335). If you must announce the prefixes under your own ASN, contact your account team.
     :::
 
-* You must use Resource Public Key Infrastructure (RPKI) validation and make sure your ROAs are accurate. You can use [Cloudflare's RPKI Portal](https://rpki.cloudflare.com/?view=validator) and a second source such as [Routinator](https://rpki-validator.ripe.net/ui/) to double-check your prefixes.
+- You must use Resource Public Key Infrastructure (RPKI) validation and make sure your ROAs are accurate. You can use [Cloudflare's RPKI Portal](https://rpki.cloudflare.com/?view=validator) and a second source such as [Routinator](https://rpki-validator.ripe.net/ui/) to double-check your prefixes.
 
-* 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.
+- 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 codeblock as example)
+```bash
+curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/addressing/prefixes \
+-H 'Content-Type: application/json' \
+-H "X-Auth-Email: $CLOUDFLARE_EMAIL" \
+-H "X-Auth-Key: $CLOUDFLARE_API_KEY" \
+-X POST \
+-d '{"cidr": "162.159.211.0/24",
+      "asn": 13335,
+      "ownership_validation" : { "delegate_loa_creation": true }
+    }
+```
 
-```json title="Response" {11,12}
+```json title="Response" {15-19}
 
  "result": {
     "id": "72823e95d6c64d48a8111fec81179816",
@@ -48,13 +66,11 @@ Once your account configurations are in place, consider the sections below to le
     "advertised_modified_at": null,
     "loa_document_id": null,
     "asn": 13335,
+    "ownership_validation_token": "<OWNERSHIP_VALIDATION_TOKEN>",
+    "delegate_loa_creation" : true,
     "irr_validation_state": "pending",
-    "rpki_validation_state": "pending"
-    "prefix_ownership_validation": {
-      "state" : "pending",
-      "token": "<>",
-      "delegate_loa_creation" : true
-      }
+    "rpki_validation_state": "pending",
+    "ownership_validation_state": "pending",
   }
 
 ```
@@ -63,18 +79,18 @@ Once your account configurations are in place, consider the sections below to le
 
 <Tabs> <TabItem label="Modify IRR record">
 
-1. Copy the token returned by the API call.
+1. Copy the `ownership_validation_token` returned by the API call.
 2. On the IRR record of the prefix you are onboarding, add the following string in either a `description` or `remarks` field. Replace `<TOKEN>` by the actual token you copied in the previous step.
 
 ```
 cf-validation: <TOKEN>
 ```
 
-   :::note
+:::note
 
-   The exact steps to update your IRR record will depend on the registry you are using. Refer to [Internet Routing Registry (IRR)](/byoip/concepts/irr-entries/) for details.
+The exact steps to update your IRR record will depend on the registry you are using. Refer to [Internet Routing Registry (IRR)](/byoip/concepts/irr-entries/best-practices/) for details.
 
-   :::
+:::
 
 </TabItem> <TabItem label="Reverse DNS zone and TXT record">
 
@@ -93,10 +109,11 @@ cf-validation.<REVERSE_ZONE_ADDRESS> IN TXT <TOKEN>
 
 4. Update nameservers at your Regional Internet Registry (RIR).The exact steps to update your nameservers will depend on the registry you are using.
 
-Once the ownership validation is successful, and if the RPKI and IRR validations also pass, the `approved` field in your prefix will return "V". This means you can proceed to create IP address service bindings[^1].
-
 </TabItem> </Tabs>
 
+
+Once the ownership validation is successful, and if the RPKI and IRR validations also pass, 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.
 <APIRequest path= "/accounts/{account_id}/addressing/prefixes/{prefix_id}" method="GET" />