From b75dc20a7d1812b5319915073d6aa81f20f9aef3 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Fri, 9 Jul 2021 23:13:21 -0400 Subject: [PATCH] docs: more cleanup --- docs/deployment/application-management.md | 1 - docs/development/plugin-creation.md | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/deployment/application-management.md b/docs/deployment/application-management.md index 66b96c5b6..31c933f3e 100644 --- a/docs/deployment/application-management.md +++ b/docs/deployment/application-management.md @@ -223,7 +223,6 @@ dokku apps:unlock node-js-app In some cases, you may wish to inspect the state of an app lock. To do so, you can issue an `apps:lock` command. This will exit non-zero if there is no app lock in place. - ```shell dokku apps:locked node-js-app ``` diff --git a/docs/development/plugin-creation.md b/docs/development/plugin-creation.md index 94f636567..6cbd9b627 100644 --- a/docs/development/plugin-creation.md +++ b/docs/development/plugin-creation.md @@ -120,7 +120,7 @@ See the sample plugin below for an example. ### Namespace commands -All commands *should* be namespaced. In cases where a core plugin is overriden, the plugin _may_ utilize the a namespace in use by the core, but generally this should be avoided to reduce confusion as to where the command is implemented. +All commands _should_ be namespaced. In cases where a core plugin is overriden, the plugin _may_ utilize the a namespace in use by the core, but generally this should be avoided to reduce confusion as to where the command is implemented. ### Implement a proper catch-all command