fixes broken links

Author: korinne

src/content/docs/workers/local-development/wrangler.mdx

@@ -114,7 +114,7 @@ API_ACCOUNT_ID="local_example_user"
 Since `.dev.vars` is loaded only when running `wrangler dev`, these values do not affect your production environment. Make sure to add `.dev.vars` to your `.gitignore` so you don’t accidentally commit sensitive credentials to version control.
 :::
 
-To learn about setting up environment variables for other non-local environments (such as staging or production), look into [Wrangler Environments](/wrangler/environments/#staging-and-production-environments).
+To learn about setting up environment variables for other non-local environments (such as staging or production), look into [Wrangler Environments](/workers/wrangler/environments/#staging-and-production-environments).
 
 ## Working with remote data
 

src/content/partials/workers/bindings_per_env.mdx

@@ -4,7 +4,7 @@
 
 ## Supported bindings in local and remote dev
 
-- **Local Development:** Includes [`wrangler dev`](/workers/wrangler/commands/#dev) (without the `--remote` flag) and the [Cloudflare Vite plugin](/local-development/vite/). This mode simulates the Cloudflare Workers environment locally.
+- **Local Development:** Includes [`wrangler dev`](/workers/wrangler/commands/#dev) (without the `--remote` flag) and the [Cloudflare Vite plugin](/workers/local-development/vite/). This mode simulates the Cloudflare Workers environment locally.
 
 - **Remote Development:** Uses [`wrangler dev --remote`](/workers/wrangler/commands/#dev)), deploying your code to Cloudflare’s infrastructure during development. This ensures all bindings and resources match production conditions. There is no Vite plugin equivalent for testing remote resources.