Apply suggestions from code review

Co-authored-by: Brendan Irvine-Broque <[email protected]>
Co-authored-by: ToriLindsay <[email protected]>

Author: 3 people

src/content/docs/workers/platform/limits.mdx

@@ -272,7 +272,7 @@ You can measure your Worker's startup time by deploying it to Cloudflare using [
 
 If you are having trouble staying under this limit, consider [profiling using DevTools](/workers/observability/dev-tools/) locally to learn how to optimize your code.
 
-When a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation, This can be imported into Chrome DevTools or opened directly in VSCode. Refer to [`wrangler check startup`](/workers/wrangler/commands/#startup) for more details.
+When you attempt to deploy a Worker using the [Wrangler CLI](/workers/wrangler/), but your deployment is rejected because your Worker exceeds the [maximum startup time](workers/platform/limits/#worker-startup-time), Wrangler will automatically generate a CPU profile that you can import into Chrome DevTools or open directly in VSCode. You can use this to learn what code in your Worker uses large amounts of CPU time at startup. Refer to [`wrangler check startup`](/workers/wrangler/commands/#startup) for more details.
 
 <Render file="limits_increase" />
 

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

@@ -1978,7 +1978,7 @@ wrangler telemetry status
 
 Generate a CPU profile of your Worker's startup phase.
 
-This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.
+After you run `wrangler check startup`, you can import the profile into Chrome DevTools or open it directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.
 
 ```sh
 wrangler check startup
@@ -1987,6 +1987,6 @@ wrangler check startup
 - `--deploy-args` <Type text="string" /> <MetaInfo text="optional" />
   - To customise the way `wrangler check startup` builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with `wrangler deploy`. For instance, if you deploy your Worker with `wrangler deploy --no-bundle`, you should use `wrangler check startup --deploy-args="--no-bundle"` to profile the startup phase.
 - `--worker-bundle` <Type text="string" /> <MetaInfo text="optional" />
-  - If you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as [the API expects](/api/resources/workers/subresources/scripts/methods/update/)
+  - If you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialized multipart upload, with the exact same format as [the API expects](/api/resources/workers/subresources/scripts/methods/update/)
 
 <Render file="wrangler-commands/global-flags" product="workers" />