Apply suggestions from code review

Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>

Author: mikenomitch

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

@@ -23,15 +23,15 @@ In this guide, we will build and push a container image alongside your Worker co
 
 ### Deploy without Docker
 
-If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass `--containers-rollout=none` to the deploy command:
+If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass [`--containers-rollout=none`](/workers/wrangler/commands/#deploy) to the deploy command:
 
 <PackageManagers
 	type="exec"
 	pkg="wrangler"
 	args="deploy --containers-rollout=none"
 />
 
-This skips the container image build and push steps, deploying your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option.
+This skips the container image build and push steps and deploys your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option.
 
 ## Deploy your first Container
 

src/content/docs/sandbox/configuration/wrangler.mdx

@@ -54,15 +54,15 @@ The minimal configuration shown above includes all required settings. For detail
 
 ## Deploy without Docker
 
-If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass `--containers-rollout=none` to the deploy command:
+If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass [`--containers-rollout=none`](/workers/wrangler/commands/#deploy) to the deploy command:
 
 <PackageManagers
 	type="exec"
 	pkg="wrangler"
 	args="deploy --containers-rollout=none"
 />
 
-This skips the container image build and push steps, deploying your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option.
+This skips the container image build and push steps and deploys your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option.
 
 ## Troubleshooting
 

src/content/docs/workers/wrangler/commands.mdx

@@ -340,7 +340,7 @@ None of the options for this command are required. Also, many can be set in your
   - Specify the [rollout strategy](/containers/faq#how-do-container-updates-and-rollouts-work) for [Containers](/containers) associated with the Worker.
   - `gradual` (default) — Rolls out to 10% then 100% of instances.
   - `immediate` — Rolls out to 100% of container instances in one step, overriding any configuration in `rollout_step_percentage`. Note that `rollout_active_grace_period`, if configured, still applies.
-  - `none` — Skips building and pushing a new container image. Use this when you do not have Docker running locally but still want to deploy Worker code changes. The deployment uses the existing container image from a previous deploy.
+  - `none` — Skips building and pushing a new container image. Use this when you do not have Docker running locally but still want to deploy Worker code changes. The deployment uses the existing container image from a previous deployment.
 - `--strict` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
   - Turns on strict mode for the deployment command, meaning that the command will be more defensive and prevent deployments which could introduce potential issues. In particular, this mode prevents deployments if the deployment would potentially override remote settings in non-interactive environments.
 - `--tag` <Type text="string" /> <MetaInfo text="optional" />