From 85f180d43a8fd9828ca68750e68ed1478c4b345f Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Sat, 7 Apr 2018 14:16:04 -0400 Subject: [PATCH] docs: consistently reference command instead of subcommand --- docs/deployment/application-management.md | 4 ++-- docs/deployment/methods/git.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/deployment/application-management.md b/docs/deployment/application-management.md index 00abed36a..7da5ffd7f 100644 --- a/docs/deployment/application-management.md +++ b/docs/deployment/application-management.md @@ -162,7 +162,7 @@ dokku apps:clone --skip-deploy node-js-app io-js-app > New as of 0.11.6 -If you wish to disable deploying for a period of time, this can be done via deploy locks. Normally, deploy locks exist only for the duration of a deploy so as to avoid deploys from colliding, but a deploy lock can be created by running the `apps:lock` subcommand. +If you wish to disable deploying for a period of time, this can be done via deploy locks. Normally, deploy locks exist only for the duration of a deploy so as to avoid deploys from colliding, but a deploy lock can be created by running the `apps:lock` command. ```shell @@ -177,7 +177,7 @@ dokku apps:lock node-js-app > New as of 0.11.6 -In some cases, it may be necessary to remove an existing deploy lock. This can be performed via the `apps:unlock` subcommand. +In some cases, it may be necessary to remove an existing deploy lock. This can be performed via the `apps:unlock` command. > Warning: Removing the deploy lock _will not_ stop in progress deploys. At this time, in progress deploys will need to be manually terminated by someone with server access. diff --git a/docs/deployment/methods/git.md b/docs/deployment/methods/git.md index 7e9d10721..106805c8c 100644 --- a/docs/deployment/methods/git.md +++ b/docs/deployment/methods/git.md @@ -14,7 +14,7 @@ GIT-based deployment has been the traditional method of deploying applications i ### Initializing an Application -When an application is created via `git push`, Dokku will create the proper `pre-receive` hook in order to execute the build pipeline. In certain cases - such as when fronting deploys with the [`git-http-backend`](https://git-scm.com/docs/git-http-backend) - this may not be correctly created. As an alternative, the `git:initialize` subcommand can be used to trigger this creation: +When an application is created via `git push`, Dokku will create the proper `pre-receive` hook in order to execute the build pipeline. In certain cases - such as when fronting deploys with the [`git-http-backend`](https://git-scm.com/docs/git-http-backend) - this may not be correctly created. As an alternative, the `git:initialize` command can be used to trigger this creation: ```shell # on the Dokku host @@ -38,7 +38,7 @@ By default, Dokku will deploy code pushed to the `master` branch. In order to qu git push dokku SOME_BRANCH_NAME:master ``` -In `0.12.0`, the correct way to change the deploy branch is to use the `git:set` Dokku subcommand. +In `0.12.0`, the correct way to change the deploy branch is to use the `git:set` Dokku command. ```shell # on the Dokku host @@ -59,7 +59,7 @@ Pushing multiple branches can also be supportec by creating a [receive-branch](/ Application deployments will include a special `GIT_REV` environment variable containing the current deployment sha being deployed. For rebuilds, this sha will remain the same. -To configure the name of the `GIT_REV` environment variable, run the `git:set` subcommand as follows: +To configure the name of the `GIT_REV` environment variable, run the `git:set` command as follows: ```shell # on the Dokku host