diff --git a/tools/cli.mdx b/tools/cli.mdx
index f73cc0a8b..280a0bd8d 100644
--- a/tools/cli.mdx
+++ b/tools/cli.mdx
@@ -272,8 +272,6 @@ Then use the same commands as any self-hosted instance (`powersync status`, `pow
 | `powersync stop --confirm=yes` | [Cloud] Stop instance (restart with deploy) |
 | `powersync compact` | [Cloud] Trigger [bucket compacting](/maintenance-ops/compacting-buckets) on demand |
 
-The CLI prints the instance it is about to act on before `powersync deploy`, `powersync stop`, `powersync destroy`, and `powersync compact` make any change, and at the start of `powersync status`. For a Cloud instance, the line shows the instance name with the instance, project, and organization IDs. For a self-hosted instance, it shows the API URL. Check this line before you confirm a destructive command.
-
 Run `powersync --help` or `powersync <command> --help` for flags. Full [command reference](https://github.com/powersync-ja/powersync-cli/blob/main/cli/README.md#commands) in the CLI repo.
 
 ## Deploying From CI (e.g. GitHub Actions)
@@ -282,7 +280,7 @@ You can automate Sync Config (and full config) deployments using the CLI in CI.
 
 **Secrets:** Set `PS_ADMIN_TOKEN` to your PowerSync personal access token. If the workflow does not use a linked directory, also set `INSTANCE_ID`. For self-hosted, `API_URL` can specify the PowerSync API base URL.
 
-The job log records the target instance line, so you can see which instance a run changed. For pull request checks, run `powersync deploy --dry-run` to validate the config and preview the changes without deploying.
+The job log shows which instance the run changed. For pull request checks, run `powersync deploy --dry-run` to validate the config and preview the changes without deploying.
 
 <Card title="GitHub Actions Demo" icon="github" horizontal href="https://github.com/powersync-community/github-actions-demo">
   Example: deploy Sync Config on push to main