diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx
index 7893a2d2198ee0a..acad403fad61eb2 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx
@@ -32,7 +32,7 @@ To enroll your device using the terminal:
 3. Enroll into Cloudflare Zero Trust using your organization's <GlossaryTooltip term="team name">team name</GlossaryTooltip>:
 
    ```sh
-   warp-cli teams-enroll <your-team-name>
+   warp-cli registration new <your-team-name>
    ```
 
 4. In the browser window that opens, complete the authentication steps required by your organization.
@@ -44,7 +44,7 @@ To enroll your device using the terminal:
 6. Verify the registration in the terminal:
 
    ```sh
-   warp-cli account
+   warp-cli registration show
    ```
 
 <Details header="Troubleshoot missing registration">
@@ -52,15 +52,15 @@ To enroll your device using the terminal:
 The registration process may take a few minutes to complete. If the registration continues to be missing, then manually copy the authentication token from the browser to the WARP client:
 
 1. On the success page, right-click and select **View Page Source**.
-2. Find the HTML metadata tag that contains the token. For example, `<meta http-equiv="refresh" content"=0;url=com.cloudflare.warp://acmecorp.cloudflareaccess.com/auth?token=yeooilknmasdlfnlnsadfojDSFJndf_kjnasdf..." />`
+2. Find the HTML metadata tag that contains the token. For example, `<meta http-equiv="refresh" content"=0;url=com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=yeooilknmasdlfnlnsadfojDSFJndf_kjnasdf..." />`
 3. Copy the URL field: `com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=<your-token>`
 4. In the terminal, run the following command using the URL obtained in the previous step.
 
    ```sh
-   warp-cli teams-enroll-token com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=<your-token>
+   warp-cli registration token "com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=<your-token>"
    ```
 
-If you get an API error, then the token has expired. Generate a new one by refreshing the web page and quickly grab the new token from the page source.
+If you get a `401` error, then the token has expired. Generate a new one by refreshing the web page and quickly grab the new token from the page source.
 
 </Details>
 
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector.mdx
index 4f14f851976f4b1..d35efa48171386d 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector.mdx
@@ -126,7 +126,7 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
     3. Verify the registration:
 
     ```sh
-    warp-cli account
+    warp-cli registration show
     ```
 
     ```sh output
@@ -148,7 +148,7 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
       ```
     - Clear an old registration and trigger WARP to re-register:
       ```sh
-      sudo warp-cli delete
+      sudo warp-cli registration delete
       ```
     - Review your [WARP daemon logs](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/) for information about why the registration is failing.
 
@@ -162,7 +162,6 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
 
     ```sh output
     Status update: Connected
-    Success
     ```
 
     <Details header="Troubleshoot connection">