[Workers] update validation errors

* startup debugging notes are duplicated on limits page, just link there
* add memory exceeded err

Author: taylorlee

src/content/docs/workers/observability/errors.mdx

@@ -209,13 +209,11 @@ Specific error cases include but are not limited to:
 
 #### Script startup exceeded CPU time limit
 
-This means that you are doing work in the top-level scope of your Worker that takes [more than the startup time limit (400ms)](/workers/platform/limits/#worker-startup-time) of CPU time.
+This means that running the top-level scope of your Worker took [more than the startup time limit (1s)](/workers/platform/limits/#worker-startup-time) of CPU time.
 
-This is usually a sign of a bug and/or large performance problem with your code or a dependency you rely on. It's not typical to use more than 400ms of CPU time when your app starts. The more time your Worker's code spends parsing and executing top-level scope, the slower your Worker will be when you deploy a code change or a new [isolate](/workers/reference/how-workers-works/) is created.
+#### Script startup exceeded memory limit
 
-This error is most commonly caused by attempting to perform expernsive initialization work directly in top level (global) scope, rather than either at build time or when your Worker's handler is invoked. For example, attempting to initialize an app by generating or consuming a large schema.
-
-To analyze what is consuming so much CPU time, you should open Chrome DevTools for your Worker and look at the Profiling and/or Performance panels to understand where time is being spent. Is there something glaring that consumes tons of CPU time, especially the first time you make a request to your Worker?
+This means that running the top-level scope of your Worker consumed [more than the memory limit (128 MB)](/workers/platform/limits/#memory) of memory.
 
 ## Runtime errors
 

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

@@ -343,6 +343,8 @@ If you are having trouble staying under this limit, consider [profiling using De
 
 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, 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.
 
+Exceeding this limit is most commonly caused by attempting to perform expensive initialization work directly in top level (global) scope, rather than either at build time or when your Worker's handler is invoked. For example, attempting to initialize an app by generating or consuming a large schema.
+
 <Render file="limits_increase" product="workers" />
 
 ---