Updated typos in limits

Author: maheshwarip

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

@@ -22,7 +22,7 @@ import { Render, WranglerConfig } from "~/components"
 | Per-queue backlog size <sup>4</sup>           									| 25GB                                                          |
 | Concurrent consumer invocations               									| 250 <sup>push-based only</sup>                                |
 | Consumer duration (wall clock time) 														| 15 minutes <sup>5</sup>                                       |
-| [Active Consumer CPU time]((/workers/platform/limits/#cpu-time))| 30 seconds (default). Configurable to 5 minutes of active CPU time |
+| [Active Consumer CPU time]((/workers/platform/limits/#cpu-time))| 30 seconds (default). [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) 							|
 | `visibilityTimeout` (pull-based queues)       									| 12 hours                                                      |
 | `delaySeconds` (when sending or retrying)     									| 12 hours                                                      |
 | Requests to the Queues API (incl. pulls/acks) 									| [1200 requests / 5 mins](/fundamentals/api/reference/limits/) |
@@ -41,10 +41,10 @@ import { Render, WranglerConfig } from "~/components"
 
 <Render file="limits_increase" product="workers" />
 
-### Increasing Queue Consumer CPU limits
-Queue consumers are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#worker-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O, which don't count towards your CPU time or Workflows compute consumption.
+### Increasing Queue Consumer Worker CPU Limits
+[Queue consumer Workers](/queues/reference/how-queues-works/#consumers) are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#worker-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O.
 
-By default, the maximum CPU time per Workflow invocation is set to 30 seconds, but can be increased for all invocations associated with a Queue consumer by setting `limits.cpu_ms` in your Wrangler configuration:
+By default, the maximum CPU time per consumer Worker invocation is set to 30 seconds, but can be increased by setting `limits.cpu_ms` in your Wrangler configuration:
 
 <WranglerConfig>