Replace other variables

Author: maxvp

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx

@@ -187,14 +187,15 @@ To rotate a tunnel token:
 
 1. Refresh the token on Cloudflare:
 
-   <Tabs syncKey="dashPlusAPI">
+      <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
+
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
-2. Select a `cloudflared` tunnel and select **Edit**.
-3. Select **Refresh token**.
-4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
+1. Select a `cloudflared` tunnel and select **Edit**.
+1. Select **Refresh token**.
+1. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
 
-   </TabItem>
+      </TabItem>
 <TabItem label="API">
 
    1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
@@ -211,7 +212,7 @@ To rotate a tunnel token:
 
       ```sh
       curl --request PATCH \
-      https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/cfd_tunnel/{tunnel_id} \
+      https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/cfd_tunnel/$TUNNEL_ID \
       --header 'Content-Type: application/json' \
       --header "Authorization: Bearer <API_TOKEN>" \
       --data '{
@@ -245,34 +246,34 @@ To rotate a tunnel token:
 
    3. Copy the `token` value shown in the output.
 
-   </TabItem>
+      </TabItem>
 </Tabs>
 
    After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
 
-2. On half of your `cloudflared` replicas, update `cloudflared` to use the new token. For example, on a Linux host:
+1. On half of your `cloudflared` replicas, update `cloudflared` to use the new token. For example, on a Linux host:
 
    ```sh
    sudo cloudflared service install <TOKEN>
    ```
 
-3. Restart `cloudflared`:
+1. Restart `cloudflared`:
 
    ```sh
    sudo systemctl restart cloudflared.service
    ```
 
-4. Confirm that the service started correctly:
+1. Confirm that the service started correctly:
 
    ```sh
    sudo systemctl status cloudflared
    ```
 
    While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
 
-5. Wait 10 minutes for traffic to route through the new connectors.
+1. Wait 10 minutes for traffic to route through the new connectors.
 
-6. Repeat steps 2, 3, and 4 for the second half of the replicas.
+1. Repeat steps 2, 3, and 4 for the second half of the replicas.
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
@@ -285,7 +286,7 @@ If your tunnel token is compromised, we recommend taking the following steps:
 
    ```sh
    curl --request DELETE \
-   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/cfd_tunnel/{tunnel_id}/connections \
+   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/cfd_tunnel/$TUNNEL_ID/connections \
    --header "Authorization: Bearer <API_TOKEN>"
    ```
 

src/content/docs/cloudflare-one/identity/idp-integration/entra-id.mdx

@@ -278,7 +278,7 @@ You can require users to re-enter their credentials into Entra ID whenever they
 2. [Update the Entra ID identity provider](/api/resources/zero_trust/subresources/identity_providers/methods/update/) using a `PUT` request. In the request body, include all existing configurations and set the `prompt` parameter to either `login` or `select_account`. For example,
    ```sh {17}
    curl --request PUT \
-   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/identity_providers/{identity_provider_id} \
+   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/identity_providers/$IDENTITY_PROVIDER_ID \
    --header "Authorization: Bearer <API_TOKEN>" \
    --header "Content-Type: application/json" \
    --data '{

src/content/docs/cloudflare-one/policies/access/policy-management.mdx

@@ -82,8 +82,8 @@ You can use the API to convert a legacy policy into a reusable policy. To conver
 
 ```bash
 curl --request PUT \
-https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/apps/{app_id}/policies/{policy_id}/make_reusable \
+https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/apps/$APP_ID/policies/$POLICY_ID/make_reusable \
 --header "Authorization: Bearer <API_TOKEN>"
 ```
 
-The policy is now removed from the applications endpoint (`/access/apps/{app_id}/policies`) and managed using the [reusable policies endpoints](/api/resources/zero_trust/subresources/access/subresources/policies/)(`/access/policies/{policy_id}`).
+The policy is now removed from the applications endpoint (`/access/apps/$APP_ID/policies`) and managed using the [reusable policies endpoints](/api/resources/zero_trust/subresources/access/subresources/policies/)(`/access/policies/$POLICY_ID`).

src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx

@@ -90,7 +90,7 @@ After creating your virtual networks, route your private network CIDRs over each
 
    ```bash
    curl --request PATCH \
-   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/routes/{route_id} \
+   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/routes/$ROUTE_ID \
    --header "Authorization: Bearer <API_TOKEN>" \
    --header "Content-Type: application/json" \
    --data '{
@@ -106,7 +106,7 @@ After creating your virtual networks, route your private network CIDRs over each
 
    ```bash
    curl --request PATCH \
-   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/routes/{route_id} \
+   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/routes/$ROUTE_ID \
    --header "Authorization: Bearer <API_TOKEN>" \
    --header "Content-Type: application/json" \
    --data '{