Update instances of Now to Vercel where applicable (#13760)

This pull request renames various instances of `now` to `vercel` etc. in order to match content that's being updated on the Vercel platform.

docs/advanced-features/multi-zones.md

@@ -27,7 +27,7 @@ There are no special zones related APIs. You only need to do following:
 
 You can merge zones using any HTTP proxy.
 
-For [Vercel](https://vercel.com/now), you can use a single `now.json` to deploy both apps. It allows you to define routing routes for multiple apps like below:
+For [Vercel](https://vercel.com/), you can use a single `vercel.json` to deploy both apps. It allows you to define routing routes for multiple apps like below:
 
 ```json
 {

docs/upgrading.md

@@ -10,9 +10,9 @@ description: Learn how to upgrade Next.js.
 
 #### Production Deployment on Vercel
 
-If you previously configured `routes` in your `now.json` file for dynamic routes, these rules can be removed when leveraging Next.js 9's new [Dynamic Routing feature](https://nextjs.org/docs/routing/dynamic-routes).
+If you previously configured `routes` in your `vercel.json` file for dynamic routes, these rules can be removed when leveraging Next.js 9's new [Dynamic Routing feature](https://nextjs.org/docs/routing/dynamic-routes).
 
-Next.js 9's dynamic routes are **automatically configured on [Now](https://vercel.com/now)** and do not require any `now.json` customization.
+Next.js 9's dynamic routes are **automatically configured on [Vercel](https://vercel.com/)** and do not require any `vercel.json` customization.
 
 You can read more about [Dynamic Routing here](https://nextjs.org/docs/routing/dynamic-routes).
 

errors/head-build-id.md

@@ -6,5 +6,5 @@ The deployment was generated incorrectly or the server was overloaded at the tim
 
 #### Possible Ways to Fix It
 
-Please make sure you are using the latest version of the `@now/next` builder in your `now.json`.
+Please make sure you are using the latest version of the `@vercel/next` builder in your `vercel.json`.
 If this error persists, please file a bug report.

examples/auth0/README.md

@@ -48,7 +48,7 @@ POST_LOGOUT_REDIRECT_URI=http://localhost:3000/
 
 ### Hosting on Vercel
 
-When deploying this example to Vercel you'll want to update the `now.json` configuration file.
+When deploying this example to Vercel you'll want to update the `vercel.json` configuration file.
 
 ```json
 {

examples/with-iron-session/lib/session.js

@@ -3,13 +3,13 @@ import { withIronSession } from 'next-iron-session'
 
 export default function withSession(handler) {
   return withIronSession(handler, {
-    // The password in this example is in plain text (inside `now.json`) for ease of deployment and understanding.
+    // The password in this example is in plain text (inside `vercel.json`) for ease of deployment and understanding.
     // ⚠️ Do not reuse the same password, create a different password for you and store it in a secret management system
     // Example for Vercel: https://vercel.com/docs/v2/serverless-functions/env-and-secrets
     password: process.env.SECRET_COOKIE_PASSWORD,
     cookieName: 'next.js/examples/with-iron-session',
     cookieOptions: {
-      // the next line allows to use the session in non-https environements like
+      // the next line allows to use the session in non-https environments like
       // Next.js dev mode (http://localhost:3000)
       secure: process.env.NODE_ENV === 'production' ? true : false,
     },

examples/with-now-env/README.md

@@ -31,12 +31,12 @@ npm install
 yarn
 ```
 
-Start the development server with [now](https://vercel.com/now) ([download](https://vercel.com/download)):
+Start the development server with [Vercel](https://vercel.com/) ([download](https://vercel.com/download)):
 
 ```bash
-now dev
+vercel dev
 ```
 
 Deploy it to the cloud with [Vercel](https://vercel.com/import?filter=next.js&utm_source=github&utm_medium=readme&utm_campaign=next-example) ([Documentation](https://nextjs.org/docs/deployment)).
 
-Keep in mind that in order to deploy the app to Vercel the env [secrets](https://vercel.com/docs/getting-started/secrets) defined in `now.json` should be listed in your account.
+Keep in mind that in order to deploy the app to Vercel the env [secrets](https://vercel.com/docs/getting-started/secrets) defined in `verel.json` should be listed in your account.

examples/with-zones/README.md

@@ -4,7 +4,7 @@ With Next.js you can use multiple apps as a single app using it's [multi-zones f
 
 - All pages should be unique across zones. For example, the `home` app should not have a `pages/blog/index.js` page.
 - The `blog` app sets `assetPrefix` so that generated JS bundles are within the `/blog` subfolder.
-  - To also support the plain `next dev` scenario, `assetPrefix` is set dynamically based on the `BUILDING_FOR_NOW` environment variable, see [`now.json`](now.json) and [`blog/next.config.js`](blog/next.config.js).
+  - To also support the plain `next dev` scenario, `assetPrefix` is set dynamically based on the `BUILDING_FOR_NOW` environment variable, see [`vercel.json`](vercel.json) and [`blog/next.config.js`](blog/next.config.js).
   - Images and other `/static` assets have to be prefixed manually, e.g., `` <img src={`${process.env.ASSET_PREFIX}/static/image.png`} /> ``, see [`blog/pages/blog/index.js`](blog/pages/blog/index.js).
 
 ## Deploy your own