change staging to preview (#1430)

Author: Matthew Sweeney

components/references-mdx/now-cli/commands/inspect.mdx

@@ -9,7 +9,7 @@ export const meta = {
 
 ## Inspect
 
-The `now inspect` command is used to retrieve information about a deployment referenced either by its unique deployment URL, staging URL, or production domain.
+The `now inspect` command is used to retrieve information about a deployment referenced either by its unique deployment URL or production domain.
 
 ### Basic Usage
 

components/references-mdx/now-cli/commands/remove.mdx

@@ -58,7 +58,7 @@ These are options that only apply to the `now remove` command, therefore, more i
 
 #### Safe
 
-The `--safe` option, shorthand `-s`, can be used to skip the removal of deployments with an active staging or production domain when a project is provided as the parameter.
+The `--safe` option, shorthand `-s`, can be used to skip the removal of deployments with an active preview URL or production domain when a project is provided as the parameter.
 
 ##### Usage Example
 

lib/data/guides.json

@@ -16,7 +16,7 @@
     "url": "/guides/deploying-a-mongodb-powered-api-with-node-and-now",
     "image": "undefined/guides/deploying-a-mongodb-powered-api-with-node-and-now/card.png",
     "editUrl": "pages/guides/deploying-a-mongodb-powered-api-with-node-and-now.mdx",
-    "lastEdited": "2019-10-14T12:32:29.000Z"
+    "lastEdited": "2019-11-01T15:20:23.000Z"
   },
   {
     "title": "Create an Angular App That Builds and Deploys with ZEIT Now",
@@ -252,7 +252,7 @@
     "authors": ["timothy", "grovesjoseph"],
     "url": "/guides/deploying-react-with-now-cra",
     "editUrl": "pages/guides/deploying-react-with-now-cra.mdx",
-    "lastEdited": "2019-10-02T14:07:07.000Z"
+    "lastEdited": "2019-11-01T15:20:23.000Z"
   },
   {
     "title": "Deploying Sanity Studio with ZEIT Now",
@@ -315,12 +315,12 @@
   },
   {
     "title": "Automatic Deployments with Now for GitLab",
-    "description": "Setup ZEIT Now for GitLab and get automatic deployments and staging URLs for each push.",
+    "description": "Setup ZEIT Now for GitLab and get automatic deployments and preview URLs for each push.",
     "published": "2019-04-01T09:03:14.819Z",
     "authors": ["arunoda", "timothy"],
     "url": "/guides/getting-started-with-now-for-gitlab",
     "editUrl": "pages/guides/getting-started-with-now-for-gitlab.mdx",
-    "lastEdited": "2019-10-02T14:07:07.000Z"
+    "lastEdited": "2019-11-01T15:20:23.000Z"
   },
   {
     "title": "Handling Node.js Request Bodies with ZEIT Now",

pages/docs/v2/advanced/now-for-github.mdx

@@ -10,10 +10,10 @@ export const meta = {
   description:
     'Deploy each change in your GitHub repositories with ZEIT Now to share and test with your colleagues. Instant share-able links to your work with each push. Automatically make your changes available from production domains.',
   editUrl: 'pages/docs/v2/advanced/now-for-github.mdx',
-  lastEdited: '2019-10-10T22:31:41.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
-The Now for GitHub integration automatically deploys your GitHub projects with [ZEIT Now](/now), providing staging URLs and automatic production domain updates.
+The Now for GitHub integration automatically deploys your GitHub projects with [ZEIT Now](/now), providing preview URLs and automatic production domain updates.
 
 The Now for GitHub integration features:
 
@@ -79,9 +79,9 @@ If production domains are set from the project domains dashboard, pushes and mer
 
 If you decide to revert a commit that has already updated a product domain, the previous commit's deployment will automatically be made available at the production domain instantly; providing you with instant rollbacks.
 
-### Staging URLs for the Latest Changes for Each Pull Request
+### Preview URLs for the Latest Changes for Each Pull Request
 
-The latest push to any pull request will automatically be made available at a unique staging URL based on the project name, branch, and team or username. These URLs will be given through a comment on each pull request.
+The latest push to any pull request will automatically be made available at a unique preview URL based on the project name, branch, and team or username. These URLs will be given through a comment on each pull request.
 
 ### Deployment Authorizations for Forks
 
@@ -93,7 +93,7 @@ This behavior protects you and your project from a leak of sensitive information
 
 Now for GitHub uses the deployment API to bring you an extended user interface both in GitHub, when showing deployments, and Slack, if you have notifications setup using the [Slack GitHub app](https://slack.github.com).
 
-You will see all of your deployments, production or staging, from within GitHub in its own page. See the page for this very documentation: <https://github.com/zeit/docs/deployments>
+You will see all of your deployments, production or preview, from within GitHub in its own page. See the page for this very documentation: <https://github.com/zeit/docs/deployments>
 
 Due to using GitHub's Deployments API, you will also be able to integrate with other services through [GitHub's checks](https://help.github.com/en/articles/about-status-checks). Now for GitHub will provide the deployment URL to the checks that require it, for example; to a testing suite such as [Ghost Inspector](https://ghostinspector.com/docs/integration/github/).
 

pages/docs/v2/advanced/now-for-gitlab.mdx

@@ -9,10 +9,10 @@ export const meta = {
   description:
     'Deploy each change in your GitLab projects with ZEIT Now to share and test with your colleagues. Instant share-able links to your work with each push. Automatically make your changes available from production domains.',
   editUrl: 'pages/docs/v2/advanced/now-for-gitlab.mdx',
-  lastEdited: '2019-10-30T09:43:23.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
-The Now for GitLab integration automatically deploys your GitLab projects with [ZEIT Now](/now), providing staging URLs and automatic production domain updates.
+The Now for GitLab integration automatically deploys your GitLab projects with [ZEIT Now](/now), providing preview URLs and automatic production domain updates.
 
 Now for GitLab provides:
 
@@ -86,16 +86,16 @@ If production domains are set from the project domains dashboard, pushes and mer
 
 If you decide to revert a commit that has already updated a product domain, the previous commit's deployment will automatically be made available at the production domain instantly; providing you with instant rollbacks.
 
-### Staging URLs for Each Merge Request
+### preview URLs for Each Merge Request
 
-The latest push to any pull request will automatically be made available at a unique staging URL based on the project name, branch, and team or username. These URLs will be given through a comment on each merge request.
+The latest push to any pull request will automatically be made available at a unique preview URL based on the project name, branch, and team or username. These URLs will be given through a comment on each merge request.
 
 <Image
   src={`${process.env.ASSETS}/guides/getting-started-with-now-for-gitlab/merge-request-alias.png`}
   width={2080/2.5}
   height={1392/2.5}
 />
-<Caption style={{marginTop: '-40px'}}>A staging URL created from a merge request.</Caption>
+<Caption style={{marginTop: '-40px'}}>A preview URL created from a merge request.</Caption>
 
 ## Included Environment Variables
 

pages/docs/v2/git-integration.mdx

@@ -6,7 +6,7 @@ export const meta = {
   description:
     'How to use the ZEIT Now Git Integrations for automatic deployments from your repository.',
   editUrl: 'pages/docs/v2/git-integration.mdx',
-  lastEdited: '2019-10-09T13:03:54.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 ZEIT Now provides integrations for your [GitHub](https://github.com) and [GitLab](https://gitlab.com) projects, allowing for **automatic deployments on every branch push** and merge to the default branch.
@@ -17,7 +17,7 @@ In addition, the Now Git integrations provide the following benefits:
 - Production domains updated for the most recent changes from the master branch
 - Instant rollbacks when reverting changes assigned to a production domain
 
-The easiest way to use a Git integration is to think of your **master branch as production**. Every time a pull request is made to the master branch, Now will **create a unique deployment**, allowing you to **view the changes in a staging environment before merging**.
+The easiest way to use a Git integration is to think of your **master branch as production**. Every time a pull request is made to the master branch, Now will **create a unique deployment**, allowing you to **view the changes in a preview environment before merging**.
 
 ## Installation
 

pages/docs/v2/introduction.mdx

@@ -8,7 +8,7 @@ export const meta = {
   description:
     'An introduction to the ZEIT Now platform and how to get started deploying any kind of application.',
   editUrl: 'pages/docs/v2/introduction.mdx',
-  lastEdited: '2019-10-09T12:52:23.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 ZEIT Now is a cloud platform for **static sites** and **Serverless Functions**. It enables developers to host websites and web services that **deploy instantly**, **scale automatically**, and requires **no supervision**, all with **no configuration**.
@@ -55,12 +55,9 @@ When your Next.js app is created, all you have to do is move into the directory
 />
 <Caption>Deploying your new Next.js project with Now CLI.</Caption>
 
-Once deployed, you will get a unique URL to reference the current version of your project, and a staging URL that is assigned on each deployment to share the latest changes under the same address.
+Once deployed, you will get a preview URL that is assigned on each deployment to share the latest changes under the same address.
 
-These URLs look like the following:
-
-- Unique Deployment URL: <https://my-next-project-6bnjtkazh.now.sh/>
-- Staging URL: <https://my-next-project.now-examples.now.sh/>
+The preview URL will look like the following: <https://my-next-project.now-examples.now.sh/>
 
 ## Related
 

pages/docs/v2/network/frequently-asked-questions.mdx

@@ -5,7 +5,7 @@ export const meta = {
   description:
     'A list of common questions and answers related to the ZEIT Network.',
   editUrl: 'pages/docs/v2/network/frequently-asked-questions.mdx',
-  lastEdited: '2019-10-09T12:52:23.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 ### What are the CDN defaults?
@@ -25,8 +25,8 @@ export const meta = {
 
 ### How do I purge the CDN cache?
 
-- You can create a new deployment to invalidate the cache for your staging and production deployments.
-- Content will remain cached for staging URLs until it expires.
+- You can create a new deployment to invalidate the cache for your preview and production deployments.
+- Content will remain cached for preview URLs until it expires.
 
 ### What are the limits of the CDN cache?
 

pages/docs/v2/network/headers.mdx

@@ -6,7 +6,7 @@ export const meta = {
   title: 'Headers',
   description: 'The list of headers included with deployments with ZEIT Now.',
   editUrl: 'pages/docs/v2/network/headers.mdx',
-  lastEdited: '2019-10-30T09:43:23.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 [HTTP headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers) can be found in both the HTTP Request and HTTP Response.
@@ -17,7 +17,7 @@ The following headers are sent to each ZEIT Now deployment and can be used to pr
 
 ### `host`
 
-This header represents the domain name as it was accessed by the client. If the deployment has been assigned to a staging or production domain and the client visits the domain URL, it contains the custom domain instead of the underlying deployment URL.
+This header represents the domain name as it was accessed by the client. If the deployment has been assigned to a preview URL or production domain and the client visits the domain URL, it contains the custom domain instead of the underlying deployment URL.
 
 ### `x-now-id`
 
@@ -37,7 +37,7 @@ The public `ip address` of the client that made the request.
 
 ### `x-now-deployment-url`
 
-This header represents the unique deployment, not the staging or production domain. For example, `test-5uyfnapzg.now.sh`.
+This header represents the unique deployment, not the preview URL or production domain. For example, `test-5uyfnapzg.now.sh`.
 
 ### `x-now-trace`
 

pages/docs/v2/platform/deployments.mdx

@@ -10,7 +10,7 @@ export const meta = {
   title: 'Deployments',
   description: 'Understanding and making deployments with ZEIT Now.',
   editUrl: 'pages/docs/v2/platform/deployments.mdx',
-  lastEdited: '2019-10-30T09:43:23.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 A deployment is the result of building your [Project](/docs/v2/platform/projects/) and making it available through a live URL.
@@ -23,29 +23,29 @@ There are multiple ways to make deployments with ZEIT Now; these include via a [
 
 When making deployments, the [Project](/docs/v2/platform/projects/) will be uploaded and transformed into a production-ready output through the use of a [Build Step](/docs/v2/build-step).
 
-Once the build step has completed successfully, a new, [immutable](https://en.wikipedia.org/wiki/Immutable_object) deployment will be made available at the [staging domain](/docs/v2/platform/deployments/#staging).
+Once the build step has completed successfully, a new, [immutable](https://en.wikipedia.org/wiki/Immutable_object) deployment will be made available at the [preview URL](/docs/v2/platform/deployments/#preview).
 
 ### Git Integration
 
 You can make deployments with Git by using either the [Now for GitHub](/docs/v2/advanced/now-for-github/) or [Now for GitLab](/docs/v2/advanced/now-for-gitlab/) integrations.
 
-When using these integrations, every push to a branch will provide you with a [staging deployment](/docs/v2/platform/deployments/#staging) to view your changes.
+When using these integrations, every push to a branch will provide you with a [preview deployment](/docs/v2/platform/deployments/#preview) to view your changes.
 
 When merging to the default branch (commonly `master`), a [production deployment](/docs/v2/platform/deployments/#production) will be made.
 
 ### Now CLI
 
 By using [Now CLI](/download), you can deploy [Projects](/docs/v2/platform/projects/) with **a single command** from your terminal.
 
-To make a [staging deployment](/docs/v2/platform/deployments/#staging), use the `now` command:
+To make a [preview deployment](/docs/v2/platform/deployments/#preview), use the `now` command:
 
 <Snippet dark text="now" />
-<Caption>Making a staging deployment with the <InlineCode>now</InlineCode> command.</Caption>
+<Caption>Making a preview deployment with the <InlineCode>now</InlineCode> command.</Caption>
 
 <Note>
   The first deployment for a <strong>Project</strong> is always both a{' '}
-  <GenericLink href="/docs/v2/platform/deployments/#staging">
-    staging
+  <GenericLink href="/docs/v2/platform/deployments/#preview">
+    preview
   </GenericLink>{' '}
   and{' '}
   <GenericLink href="/docs/v2/platform/deployments/#production">
@@ -54,7 +54,7 @@ To make a [staging deployment](/docs/v2/platform/deployments/#staging), use the
   deployment.
 </Note>
 
-To make a [production deployment](/docs/v2/platform/deployments/#staging), use the `now --prod` command:
+To make a [production deployment](/docs/v2/platform/deployments/#preview), use the `now --prod` command:
 
 <Snippet dark text="now --prod" />
 <Caption>Making a production deployment with the <InlineCode>now</InlineCode> command.</Caption>
@@ -83,15 +83,15 @@ You can find more information about the Now API in the [API Reference](/docs/api
 
 ## Deployment Types
 
-There are two types of deployment on the ZEIT Now platform: **staging** and **production**.
+There are two types of deployment on the ZEIT Now platform: **preview** and **production**.
 
-### Staging
+### Preview
 
-**Staging deployments** are the default for all deployments. Each time you push to a branch or make a deployment using the `now` command, this is a **staging deployment**.
+**Preview deployments** are the default for all deployments. Each time you push to a branch or make a deployment using the `now` command, this is a **preview deployment**.
 
-By making a **staging deployment**, the **staging domain** will be updated to reflect that of the latest deployment made.
+By making a **preview deployment**, the **preview URL** will be updated to reflect that of the latest deployment made.
 
-The **staging domain** is provided either by the deployment output from Now CLI or on a pull or merge request when using a git integration and contains the name of the user or team to which the [Project](/docs/v2/platform/projects/) belongs.
+The **preview URL** is provided either by the deployment output from Now CLI or on a pull or merge request when using a git integration and contains the name of the user or team to which the [Project](/docs/v2/platform/projects/) belongs.
 
 ### Production
 

pages/docs/v2/serverless-functions/edge-caching.mdx

@@ -8,7 +8,7 @@ export const meta = {
   description:
     'Learn how Serverless Function responses are cached with ZEIT Now and how you can define the cache behavior.',
   editUrl: 'pages/docs/v2/serverless-functions/edge-caching.mdx',
-  lastEdited: '2019-10-30T09:43:23.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 The ZEIT Smart CDN is active for all deployments and domains on your account and caches your content at [the edge](/docs/v2/network/regions-and-providers/) to serve data to your users as fast as possible.
@@ -84,7 +84,7 @@ When the CDN receives a request with `Pragma: no-cache` (such as when the browse
 
 ## Cache Invalidation and Purging
 
-Every time you deploy with [a custom domain](/docs/v2/custom-domains#deploying-with-your-domain) (production or staging custom domain), the cache for that domain is purged. This means that users will never see content from a previous deployment on your custom domain and there is no need to invalidate it manually when deploying.
+Every time you deploy with [a custom domain](/docs/v2/custom-domains#deploying-with-your-domain), the cache for that domain is purged. This means that users will never see content from a previous deployment on your custom domain and there is no need to invalidate it manually when deploying.
 
 export default ({ children }) => <Doc meta={meta}>{children}</Doc>
 

pages/guides/deploying-a-mongodb-powered-api-with-node-and-now.mdx

@@ -17,7 +17,7 @@ export const meta = {
     process.env.ASSETS
   }/guides/deploying-a-mongodb-powered-api-with-node-and-now/card.png`,
   editUrl: 'pages/guides/deploying-a-mongodb-powered-api-with-node-and-now.mdx',
-  lastEdited: '2019-10-14T12:32:29.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 In this guide, we will walk you through creating and [deploying](/docs/v2/deployments/basics/) a [Node.js](https://nodejs.org/) API powered by [MongoDB](https://www.mongodb.com/), on [ZEIT Now](/now).
@@ -233,8 +233,6 @@ Using the default port, you can find your new API endpoint at <http://localhost:
 
 The next and final step is to deploy your app with a single command.
 
-With Now, you can deploy your app to [different environments](/docs/v2/custom-domains#deploying-with-your-domain), depending on what stage your app is at; either staging or production.
-
 To deploy your MongoDB API, use the following [Now CLI](/download) command from your terminal:
 
 <Snippet dark text="now" />

pages/guides/deploying-react-with-now-cra.mdx

@@ -12,7 +12,7 @@ export const meta = {
   authors: ['timothy', 'grovesjoseph'],
   url: '/guides/deploying-react-with-now-cra',
   editUrl: 'pages/guides/deploying-react-with-now-cra.mdx',
-  lastEdited: '2019-10-02T14:07:07.000Z'
+  lastEdited: '2019-11-01T15:20:23.000Z'
 }
 
 [React](https://reactjs.org/) is a popular open-source JavaScript framework, maintained by Facebook, for easily creating interactive [single-page apps](https://en.wikipedia.org/wiki/Single-page_application) (SPAs).
@@ -42,8 +42,6 @@ With your React application set up, it is ready to deploy with [Now](/docs/v2).
 
 If you have not yet installed Now, you can do so by [installing Now CLI](/download).
 
-With Now, you can deploy your app to [different environments](/docs/v2/custom-domains#deploying-with-your-domain), depending on what stage your app is at; either staging or production.
-
 To deploy your React project, use the following [Now CLI](/download) command from your terminal:
 
 <Snippet dark text="now" />