term: review usage around "next" word

.gitignore

@@ -57,7 +57,7 @@ typings/
 # dotenv environment variables file
 .env
 
-# next.js build output
+# Next.js build output
 .idea
 .next/
 *.log

public/static/docs/get-started/connect-code-and-data.md

@@ -124,7 +124,7 @@ wdir: .
 > [pipeline](/doc/get-started/pipeline), or in other words, instructions on how
 > to build a ML model (data file) from previous data files (or directories).
 
-We would recommend to read a few next chapters first, before switching to other
+We would recommend to read a few more chapters first, before switching to other
 documents. Hopefully, `dvc run` and `dvc repro` will make more sense after a few
 more Get Started chapters. You can always refer to the `dvc run` and `dvc repro`
 documentation to learn the specific details about how they behave and all of

public/static/docs/tutorials/pipelines.md

@@ -205,7 +205,7 @@ but made specifically to handle large data files.
 
 </details>
 
-Next stage: let's convert XML into TSV to make feature extraction easier:
+Let's convert XML into TSV to make feature extraction easier:
 
 ```dvc
 $ dvc run -d code/xml_to_tsv.py -d data/Posts.xml -o data/Posts.tsv \

public/static/docs/user-guide/contributing/core.md

@@ -289,7 +289,7 @@ Tests currently only work on Linux. First you need to set up passwordless ssh
 access to localhost:
 
 ```dvc
-# Only run next line if you don't yet have keys
+# Only run the next line if you don't yet have keys
 $ ssh-keygen -t rsa -P ""
 $ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
 ```

server.js

@@ -118,7 +118,7 @@ app.prepare().then(() => {
       // Fire up docs engine!
       app.render(req, res, '/doc', query)
     } else {
-      // Regular Next handler
+      // Regular Next.js handler
       handle(req, res, parsedUrl)
     }
   }).listen(port, err => {