From 67d1b266fe0e192f43da9a1b9d6e968fe2450305 Mon Sep 17 00:00:00 2001 From: Scott Goci Date: Thu, 19 Jan 2023 10:02:45 -0500 Subject: [PATCH] docs: rename _rewrites to _redirects as _rewrites does not seem to be used --- docs/redirects-rewrites.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/redirects-rewrites.md b/docs/redirects-rewrites.md index b52574112c..ee7de3ac72 100644 --- a/docs/redirects-rewrites.md +++ b/docs/redirects-rewrites.md @@ -50,9 +50,9 @@ so there are some considerations in deciding which one to use with your site. only applies to rewrites, not redirects. - If you need Next.js-specific features such as regex path or header matching, you must use Next.js rewrites. -### Using `_rewrites` and `_headers` files +### Using `_redirects` and `_headers` files -If you are using `_rewrites` or `_headers` files rather than a `netlify.toml` file, bear in mind that these files must +If you are using `_redirects` or `_headers` files rather than a `netlify.toml` file, bear in mind that these files must be in the published directory of your site, not the root of the repo. To do this, put them in `public` and they will be moved into `.next` at build time. Do not put them directly into `.next`, because it is emptied at build time. Any -`_rewrites` or `_headers` files in the root of the repo will not be found when deployed. +`_redirects` or `_headers` files in the root of the repo will not be found when deployed.