From 6a9583b17665069e27bf13df56b799b61aadacfa Mon Sep 17 00:00:00 2001
From: Stanislas Leduc <stanislas.leduc@fullsix.com>
Date: Mon, 12 Feb 2018 21:07:30 +0100
Subject: [PATCH 1/3] Change help run command be more explicit

---
 plugins/00_dokku-standard/commands | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugins/00_dokku-standard/commands b/plugins/00_dokku-standard/commands
index 5e7a4b939..fd1d9908e 100755
--- a/plugins/00_dokku-standard/commands
+++ b/plugins/00_dokku-standard/commands
@@ -9,7 +9,7 @@ case "$1" in
       declare desc="return standard plugin help content"
       cat<<help_content
     ls , Pretty listing of deployed applications and containers
-    run <app> <cmd>, Run a command in the environment of an application
+    run <app> <cmd>, Run a command in the container based on application image
     trace [on/off], Enable dokku tracing
     url <app>, Show the first URL for an application (compatibility)
     urls <app>, Show all URLs for an application

From e7f8aeff8a9442a0ba4dde45fd3f795ee1cb6f91 Mon Sep 17 00:00:00 2001
From: Jose Diaz-Gonzalez <email@josediazgonzalez.com>
Date: Tue, 13 Feb 2018 01:35:08 -0500
Subject: [PATCH 2/3] docs: clarify help output for run subcommand

[ci skip]
---
 docs/deployment/one-off-processes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/deployment/one-off-processes.md b/docs/deployment/one-off-processes.md
index 3210a6f7c..bc52a9ced 100644
--- a/docs/deployment/one-off-processes.md
+++ b/docs/deployment/one-off-processes.md
@@ -5,7 +5,7 @@ Sometimes you need to either inspect running containers or run a one-off command
 ## Run a command in an app environment
 
 ```
-run <app> <cmd>                                # Run a command in the environment of an application
+run <app> <cmd>                                # Run a command in a new container using the current application image
 ```
 
 The `run` command can be used to run a one-off process for a specific command. This will start a new container and run the desired command within that container. Note that this container will be stay around even after command completes. The container will be the same container as was used to start the currently deployed application.

From ff14323fdc6d42acad03eca5cee24e8b130a0606 Mon Sep 17 00:00:00 2001
From: Jose Diaz-Gonzalez <email@josediazgonzalez.com>
Date: Tue, 13 Feb 2018 01:35:43 -0500
Subject: [PATCH 3/3] fix: clarify docs on run subcommand

[ci skip]
---
 plugins/00_dokku-standard/commands | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugins/00_dokku-standard/commands b/plugins/00_dokku-standard/commands
index fd1d9908e..fc68f680f 100755
--- a/plugins/00_dokku-standard/commands
+++ b/plugins/00_dokku-standard/commands
@@ -9,7 +9,7 @@ case "$1" in
       declare desc="return standard plugin help content"
       cat<<help_content
     ls , Pretty listing of deployed applications and containers
-    run <app> <cmd>, Run a command in the container based on application image
+    run <app> <cmd>, Run a command in a new container using the current application image
     trace [on/off], Enable dokku tracing
     url <app>, Show the first URL for an application (compatibility)
     urls <app>, Show all URLs for an application