diff --git a/examples/bootstrap/README.md b/examples/bootstrap/README.md index ee0ccc9d18..75ec17ff8c 100644 --- a/examples/bootstrap/README.md +++ b/examples/bootstrap/README.md @@ -14,7 +14,7 @@ $ yarn $ yarn start ``` -This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. +This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ### Build diff --git a/examples/facebook/README.md b/examples/facebook/README.md index 0ac05cf153..6abf019db9 100644 --- a/examples/facebook/README.md +++ b/examples/facebook/README.md @@ -14,7 +14,7 @@ $ yarn $ yarn start ``` -This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. +This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ### Build diff --git a/packages/docusaurus-init/templates/bootstrap/README.md b/packages/docusaurus-init/templates/bootstrap/README.md index a9bf77a27c..55d0c3ef41 100644 --- a/packages/docusaurus-init/templates/bootstrap/README.md +++ b/packages/docusaurus-init/templates/bootstrap/README.md @@ -14,7 +14,7 @@ $ yarn $ yarn start ``` -This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. +This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ### Build diff --git a/packages/docusaurus-init/templates/classic/README.md b/packages/docusaurus-init/templates/classic/README.md index 2ecfcfd620..231a499c0d 100644 --- a/packages/docusaurus-init/templates/classic/README.md +++ b/packages/docusaurus-init/templates/classic/README.md @@ -14,7 +14,7 @@ yarn install yarn start ``` -This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. +This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ## Build diff --git a/packages/docusaurus-init/templates/facebook/README.md b/packages/docusaurus-init/templates/facebook/README.md index ed4a0de3a6..1b65ca0890 100644 --- a/packages/docusaurus-init/templates/facebook/README.md +++ b/packages/docusaurus-init/templates/facebook/README.md @@ -14,7 +14,7 @@ $ yarn $ yarn start ``` -This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. +This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ### Build diff --git a/website-1.x/docs/getting-started-publishing.md b/website-1.x/docs/getting-started-publishing.md index 8771afff7f..6fbfbfbdd4 100644 --- a/website-1.x/docs/getting-started-publishing.md +++ b/website-1.x/docs/getting-started-publishing.md @@ -255,7 +255,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t 1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already. 1. Create an organization and within the organization create a project and connect your repository from GitHub. 1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with repository scope. -1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at yout repository root. +1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root. ```yaml # azure-pipelines.yml diff --git a/website-1.x/versioned_docs/version-1.14.5/getting-started-publishing.md b/website-1.x/versioned_docs/version-1.14.5/getting-started-publishing.md index ae9cbe7c61..78ac5601fc 100644 --- a/website-1.x/versioned_docs/version-1.14.5/getting-started-publishing.md +++ b/website-1.x/versioned_docs/version-1.14.5/getting-started-publishing.md @@ -256,7 +256,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t 1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already. 1. Create an organization and within the organization create a project and connect your repository from GitHub. 1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with repository scope. -1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at yout repository root. +1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root. ```yaml # azure-pipelines.yml diff --git a/website-1.x/versioned_docs/version-1.14.7/getting-started-publishing.md b/website-1.x/versioned_docs/version-1.14.7/getting-started-publishing.md index 28c93a295a..7294933acf 100644 --- a/website-1.x/versioned_docs/version-1.14.7/getting-started-publishing.md +++ b/website-1.x/versioned_docs/version-1.14.7/getting-started-publishing.md @@ -256,7 +256,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t 1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already. 1. Create an organization and within the organization create a project and connect your repository from GitHub. 1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with repository scope. -1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at yout repository root. +1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root. ```yaml # azure-pipelines.yml diff --git a/website/versioned_docs/version-2.0.0-alpha.71/deployment.mdx b/website/versioned_docs/version-2.0.0-alpha.71/deployment.mdx index b93d11f539..8dfa04032f 100644 --- a/website/versioned_docs/version-2.0.0-alpha.71/deployment.mdx +++ b/website/versioned_docs/version-2.0.0-alpha.71/deployment.mdx @@ -94,7 +94,7 @@ Optional parameters, also set as environment variables: | `CURRENT_BRANCH` | The branch that contains the latest docs changes that will be deployed. Usually, the branch will be `master`, but it could be any branch (default or otherwise) except for `gh-pages`. If nothing is set for this variable, then the current branch will be used. | | `GIT_PASS` | Password (or token) of the `git` user (specified by `GIT_USER`). For example, to facilitate non-interactive deployment (e.g. continuous deployment) | -GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment veriable: +GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment variable: | Name | Description | | ------------- | ----------------------------------------------- | @@ -242,7 +242,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t 1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already. 1. Create an organization and within the organization create a project and connect your repository from GitHub. 1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with the `repo` scope. -1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at yout repository root. +1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root. ```yaml title="azure-pipelines.yml" trigger: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx b/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx index b93d11f539..8dfa04032f 100644 --- a/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx +++ b/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx @@ -94,7 +94,7 @@ Optional parameters, also set as environment variables: | `CURRENT_BRANCH` | The branch that contains the latest docs changes that will be deployed. Usually, the branch will be `master`, but it could be any branch (default or otherwise) except for `gh-pages`. If nothing is set for this variable, then the current branch will be used. | | `GIT_PASS` | Password (or token) of the `git` user (specified by `GIT_USER`). For example, to facilitate non-interactive deployment (e.g. continuous deployment) | -GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment veriable: +GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment variable: | Name | Description | | ------------- | ----------------------------------------------- | @@ -242,7 +242,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t 1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already. 1. Create an organization and within the organization create a project and connect your repository from GitHub. 1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with the `repo` scope. -1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at yout repository root. +1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root. ```yaml title="azure-pipelines.yml" trigger: