feedback

vercel · Dec 14, 2023 · 6d2fa38 · 6d2fa38
1 parent 9494f3d
commit 6d2fa38
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...02-app/01-building-your-application/07-configuring/03-environment-variables.mdx b/...02-app/01-building-your-application/07-configuring/03-environment-variables.mdx
@@ -183,7 +183,7 @@ If you've configured [Development Environment Variables](https://vercel.com/docs
 vercel env pull .env.local
 ```
 
-> **Good to know**: When deploying your Next.js application to [Vercel](https://vercel.com), your environment variables in `.env*` files will not be made available to Edge Runtime, unless their name are prefixed with `NEXT_PUBLIC_`. We strongly recommend managing your environment variables in [Project Settings](https://vercel.com/docs/projects/environment-variables?utm_medium=docs&utm_source=next-site&utm_campaign=next-website) instead.
+> **Good to know**: When deploying your Next.js application to [Vercel](https://vercel.com), your environment variables in `.env*` files will not be made available to Edge Runtime, unless their name are prefixed with `NEXT_PUBLIC_`. We strongly recommend managing your environment variables in [Project Settings](https://vercel.com/docs/projects/environment-variables?utm_medium=docs&utm_source=next-site&utm_campaign=next-website) instead, from where all environment variables are available.
 
 ## Test Environment Variables