diff --git a/content/billing/concepts/product-billing/cloud-and-local-sandboxes.md b/content/billing/concepts/product-billing/cloud-and-local-sandboxes.md
index 1c6bfcf6841f..89214bb20071 100644
--- a/content/billing/concepts/product-billing/cloud-and-local-sandboxes.md
+++ b/content/billing/concepts/product-billing/cloud-and-local-sandboxes.md
@@ -61,7 +61,7 @@ You pay for cloud sandboxes using the payment method set up for your {% data var
 
 Cloud sandbox usage is billed to the account that owns the sandbox.
 
-You are prompted to select an owner for the session only if you are not currently in a Git repository. In this case, when you create a cloud sandbox session with `copilot ‑‑cloud`, you are prompted to select an owner—your own personal account is listed first, ahead of any organizations you belong to. You must choose either your personal account or one of the listed organizations, and all usage for that session is billed to the account you select.
+You are prompted to select an owner for the session only if you are not currently in a Git repository. In this case, when you create a cloud sandbox session with `copilot --cloud`, you are prompted to select an owner—your own personal account is listed first, ahead of any organizations you belong to. You must choose either your personal account or one of the listed organizations, and all usage for that session is billed to the account you select.
 
 If you are in a repository, the owner of the repository is billed and no owner selection is required.
 
diff --git a/content/copilot/concepts/security-governance-and-network-settings/about-cloud-and-local-sandboxes.md b/content/copilot/concepts/security-governance-and-network-settings/about-cloud-and-local-sandboxes.md
index 44526edaf44f..dc58984ecee0 100644
--- a/content/copilot/concepts/security-governance-and-network-settings/about-cloud-and-local-sandboxes.md
+++ b/content/copilot/concepts/security-governance-and-network-settings/about-cloud-and-local-sandboxes.md
@@ -137,7 +137,7 @@ Cloud sandboxing is built on Azure Container Apps Sandboxes, with {% data variab
 To start a cloud-backed session, run the following command:
 
 ```shell copy
-copilot ‑‑cloud ‑‑experimental
+copilot --cloud --experimental
 ```
 
 > [!NOTE]
@@ -145,7 +145,7 @@ copilot ‑‑cloud ‑‑experimental
 
 The `‑‑cloud` command line option launches an interactive {% data variables.copilot.copilot_cli_short %} session inside a cloud sandbox. You can prompt {% data variables.product.prodname_copilot_short %} to perform tasks, run shell commands, and iterate on code, the same way you would in a local session. The commands that {% data variables.product.prodname_copilot_short %} runs execute in the cloud environment, not on your local machine.
 
-Running `copilot ‑‑cloud` starts a single {% data variables.copilot.copilot_cli_short %} session in a cloud sandbox. It does not affect future {% data variables.product.prodname_copilot_short %} sessions. Each time you want to run a new session in a cloud sandbox, you must start the CLI with the `‑‑cloud` option.
+Running `copilot --cloud` starts a single {% data variables.copilot.copilot_cli_short %} session in a cloud sandbox. It does not affect future {% data variables.product.prodname_copilot_short %} sessions. Each time you want to run a new session in a cloud sandbox, you must start the CLI with the `‑‑cloud` option.
 
 > [!NOTE]
 > Cloud sandboxing is only available for interactive {% data variables.copilot.copilot_cli_short %} sessions. You can't run the CLI programmatically in a cloud sandbox—that is, you can't combine the `‑‑cloud` option with the `-p` or `-i` options.
diff --git a/content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md b/content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md
index 79e14de11c30..1234ffd32a49 100644
--- a/content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md
+++ b/content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md
@@ -315,7 +315,7 @@ For situations where you trust {% data variables.product.prodname_copilot_short
 
 You can use sandboxing to restrict what {% data variables.product.prodname_copilot_short %} can access. Local sandboxing does not run the CLI itself in a sandbox; instead, the commands and tools that {% data variables.copilot.copilot_cli_short %} runs on your behalf are restricted, limiting their access to your filesystem, network, and system capabilities. To enable local sandboxing, enter `/sandbox enable` inside a session.
 
-Alternatively, with cloud sandboxing, the entire {% data variables.copilot.copilot_cli_short %} session runs remotely in an isolated environment. To start a {% data variables.copilot.copilot_cli_short %} session in the cloud, run `copilot ‑‑cloud`. For more information, see [AUTOTITLE](/copilot/concepts/about-cloud-and-local-sandboxes).
+Alternatively, with cloud sandboxing, the entire {% data variables.copilot.copilot_cli_short %} session runs remotely in an isolated environment. To start a {% data variables.copilot.copilot_cli_short %} session in the cloud, run `copilot --cloud`. For more information, see [AUTOTITLE](/copilot/concepts/about-cloud-and-local-sandboxes).
 
 ### Toggle reasoning visibility