fix links

Author: penalosa

src/content/docs/workers/miniflare/core/compatibility.mdx

@@ -3,7 +3,7 @@ order: 8
 title: "📅 Compatibility Dates"
 ---
 
-- [Compatibility Dates Reference](/workers/platform/compatibility-dates)
+- [Compatibility Dates Reference](/workers/configuration/compatibility-dates)
 
 ## Compatibility Dates
 

src/content/docs/workers/miniflare/core/fetch.mdx

@@ -3,9 +3,7 @@ order: 0
 title: "📨 Fetch Events"
 ---
 
-- [`FetchEvent` Reference](/workers/runtime-apis/fetch-event)
-- [`FetchEvent` Lifecycle](/workers/learning/fetch-event-lifecycle)
-- [`addEventListener` Reference](/workers/runtime-apis/add-event-listener)
+- [`FetchEvent` Reference](/workers/runtime-apis/handlers/fetch/)
 
 ## HTTP Requests
 
@@ -15,9 +13,7 @@ Whenever an HTTP request is made, a `Request` object is dispatched to your worke
 Miniflare will log the method, path, status, and the time it took to respond.
 
 If the Worker throws an error whilst generating a response, an error page
-containing the stack trace is returned instead. You can use
-[🗺 Source Maps](/developing/source-maps) to make these point to your source
-files.
+containing the stack trace is returned instead.
 
 ## Dispatching Events
 

src/content/docs/workers/miniflare/core/modules.md

@@ -3,7 +3,7 @@ order: 3
 title: "📚 Modules"
 ---
 
-- [Modules Reference](/workers/cli-wrangler/configuration#modules)
+- [Modules Reference](/workers/reference/migrate-to-module-workers/)
 
 ## Enabling Modules
 

src/content/docs/workers/miniflare/core/queues.md

@@ -36,7 +36,7 @@ const mf = new Miniflare({
 
 ## Manipulating Outside Workers
 
-For testing, it can be valuable to interact with Queues outside a Worker. You can do this by using the [`workers` option](/core/multiple-workers) to run multiple Workers in the same instance:
+For testing, it can be valuable to interact with Queues outside a Worker. You can do this by using the `workers` option to run multiple Workers in the same instance:
 
 ```js
 const mf = new Miniflare({

src/content/docs/workers/miniflare/core/scheduled.md

@@ -3,8 +3,7 @@ order: 1
 title: "⏰ Scheduled Events"
 ---
 
-- [`ScheduledEvent` Reference](/workers/runtime-apis/scheduled-event)
-- [`addEventListener` Reference](/workers/runtime-apis/add-event-listener)
+- [`ScheduledEvent` Reference](/workers/runtime-apis/handlers/scheduled/)
 
 ## Cron Triggers
 

src/content/docs/workers/miniflare/core/standards.md

@@ -9,7 +9,6 @@ title: "🕸 Web Standards"
 - [Request Reference](/workers/runtime-apis/request)
 - [Response Reference](/workers/runtime-apis/response)
 - [Streams Reference](/workers/runtime-apis/streams)
-- [Using Streams](/workers/learning/using-streams)
 - [Web Crypto Reference](/workers/runtime-apis/web-crypto)
 
 ## Mocking Outbound `fetch` Requests

src/content/docs/workers/miniflare/core/web-sockets.md

@@ -4,7 +4,7 @@ title: "✉️ WebSockets"
 ---
 
 - [WebSockets Reference](/workers/runtime-apis/websockets)
-- [Using WebSockets](/workers/learning/using-websockets)
+- [Using WebSockets](/workers/examples/websockets/)
 
 ## Server
 

src/content/docs/workers/miniflare/developing/debugger.md

@@ -63,5 +63,5 @@ debugging.
 ## DevTools
 
 Breakpoints can also be added via the Workers DevTools. For more information,
-[read the guide](/workers/observability/local-development-and-testing/#devtools)
+[read the guide](/workers/observability/dev-tools)
 in the Cloudflare Workers docs.

src/content/docs/workers/miniflare/get-started.mdx

@@ -3,7 +3,7 @@ order: 1
 title: Get Started
 ---
 
-The Miniflare API allows you to dispatch events to workers without making actual HTTP requests, simulate connections between Workers, and interact with local emulations of storage products like [KV](/storage/kv), [R2](/storage/r2), and [Durable Objects](/storage/durable-objects). This makes it great for writing tests, or other advanced use cases where you need finer-grained control.
+The Miniflare API allows you to dispatch events to workers without making actual HTTP requests, simulate connections between Workers, and interact with local emulations of storage products like [KV](/workers/miniflare/storage/kv), [R2](/workers/miniflare/storage/r2), and [Durable Objects](/workers/miniflare/storage/durable-objects). This makes it great for writing tests, or other advanced use cases where you need finer-grained control.
 
 ## Installation
 
@@ -47,7 +47,7 @@ console.log(await res.text()); // Hello Miniflare!
 await mf.dispose();
 ```
 
-The [rest of these docs](/core/fetch) go into more detail on configuring
+The [rest of these docs](/workers/miniflare/core/fetch) go into more detail on configuring
 specific features.
 
 ### String and File Scripts
@@ -162,7 +162,7 @@ const queueResult = await worker.queue("needy", [
 console.log(queueResult); // { outcome: "ok", retryAll: true, ackAll: false, explicitRetries: [], explicitAcks: []}
 ```
 
-See [📨 Fetch Events](/core/fetch) and [⏰ Scheduled Events](/core/scheduled)
+See [📨 Fetch Events](/workers/miniflare/core/fetch) and [⏰ Scheduled Events](/workers/miniflare/core/scheduled)
 for more details.
 
 ### HTTP Server

src/content/docs/workers/miniflare/migrations/from-v2.mdx

@@ -198,12 +198,12 @@ open-source `workerd` runtime. See the [Getting Started guide for the new API do
     [`workerd`](https://github.com/cloudflare/workerd) server listening on the
     configured `host` and `port`, so these methods are redundant.
 - `dispatchScheduled()/startScheduled()`
-  - The functionality of `dispatchScheduled` can now be done via `getWorker()`. For more information read the [scheduled events documentation](/core/scheduled#dispatching-events).
+  - The functionality of `dispatchScheduled` can now be done via `getWorker()`. For more information read the [scheduled events documentation](/workers/miniflare/core/scheduled#dispatching-events).
 - `dispatchQueue()`
   - Use the `queue()` method on
-    [service bindings](/workers/platform/bindings/about-service-bindings/)
+    [service bindings](/workers/runtime-apis/bindings/service-bindings)
     or
-    [queue producer bindings](/queues/platform/configuration/#producer)
+    [queue producer bindings](/queues/configuration/configure-queues/#producer)
     instead.
 - `getGlobalScope()/getBindings()/getModuleExports()`
   - These methods returned objects from inside the Workers sandbox. Since