From 51a7988923b0d3744cdedb6a9abcb6766b8355b4 Mon Sep 17 00:00:00 2001 From: Forresst Date: Wed, 31 Mar 2021 15:51:13 +0200 Subject: [PATCH] docs(v2): fix typo deployment.mdx (#4539) --- website/docs/deployment.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/deployment.mdx b/website/docs/deployment.mdx index 2ca292dd47..3c163d3c9b 100644 --- a/website/docs/deployment.mdx +++ b/website/docs/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: