docs: remove docs files and update links from repo docs to netlify docs

README.md

@@ -56,7 +56,7 @@ Next.js Middleware works out of the box on Netlify. By default, middleware runs
 support for running Middleware at the origin, set the environment variable `NEXT_DISABLE_NETLIFY_EDGE` to `true`. Be
 aware that this will result in slower performance, as all pages that match middleware must use SSR.
 
-For more details on Next.js Middleware with Netlify, see the [middleware docs](https://github.com/netlify/next-runtime/blob/main/docs/middleware.md).
+For more details on Next.js Middleware with Netlify, see the [middleware docs](https://docs.netlify.com/integrations/frameworks/next-js/middleware/).
 
 ### Limitations
 
@@ -74,7 +74,7 @@ If you are using Nx, then you will need to point `publish` to the folder inside
 ## Incremental Static Regeneration (ISR)
 
 The Next.js Runtime fully supports ISR on Netlify. For more details see
-[the ISR docs](https://github.com/netlify/next-runtime/blob/main/docs/isr.md).
+[the ISR docs](https://docs.netlify.com/integrations/frameworks/next-js/incremental-static-regeneration/).
 
 Note that Netlify has a minimum TTL of 60 seconds for revalidation.
 
@@ -144,7 +144,7 @@ Runtime will now use the default `server` target. If you previously set the targ
 remove it.
 
 If you currently use redirects or rewrites on your site, see
-[the Rewrites and Redirects guide](https://github.com/netlify/next-runtime/blob/main/docs/redirects-rewrites.md) for
+[the Rewrites and Redirects guide](https://docs.netlify.com/integrations/frameworks/next-js/redirects-and-rewrites/) for
 information on changes to how they are handled in this version. In particular, note that `_redirects` and `_headers`
 files must be placed in `public`, not in the root of the site.
 

docs/release-notes/v4.md

@@ -6,10 +6,10 @@ stability.
 ## What's new
 
 - Full support for
-  [incremental static regeneration (ISR)](https://github.com/netlify/next-runtime/blob/main/docs/isr.md).
+  [incremental static regeneration (ISR)](https://docs.netlify.com/integrations/frameworks/next-js/incremental-static-regeneration/).
 - Full support for
-  [Next.js rewrites, redirects and headers](https://github.com/netlify/next-runtime/blob/main/docs/redirects-rewrites.md).
-- Beta support for [Next.js 12 Middleware](https://github.com/netlify/next-runtime/blob/main/docs/middleware.md)
+  [Next.js rewrites, redirects and headers](https://docs.netlify.com/integrations/frameworks/next-js/redirects-and-rewrites/).
+- Beta support for [Next.js 12 Middleware](https://docs.netlify.com/integrations/frameworks/next-js/middleware/)
 - Faster builds and deploys. Instead of generating one function per route, there are just three functions per site and a
   much smaller list of rewrites.
 - Full support for Netlify's new [persistent On-Demand Builders](https://ntl.fyi/odb). Return `fallback: "blocking"`
@@ -41,10 +41,10 @@ If you previously set these values, they're no longer needed and can be removed:
 - `external_node_modules` in `netlify.toml`
 
 If you currently use redirects or rewrites on your site, see
-[the Rewrites and Redirects guide](https://github.com/netlify/next-runtime/blob/main/docs/redirects-rewrites.md) for
+[the Rewrites and Redirects guide](https://docs.netlify.com/integrations/frameworks/next-js/redirects-and-rewrites/) for
 information on changes to how they are handled in this version. If you currently have `_redirects` or `_headers` files
 in the root of your site, these will need to be moved into "public".
 
 If you want to use Next.js 12's beta Middleware feature, this will mostly work as expected but please
-[read the docs on some caveats and workarounds](https://github.com/netlify/next-runtime/blob/main/docs/middleware.md)
+[read the docs on some caveats and workarounds](https://docs.netlify.com/integrations/frameworks/next-js/middleware/)
 that are currently needed.