From 557cf144db0a7678cf761a9a54a138b8df8125cf Mon Sep 17 00:00:00 2001
From: Mattias Reichel <mattias.reichel@gmail.com>
Date: Wed, 6 Dec 2023 13:39:28 +0100
Subject: [PATCH] Update the command line usage reference (#878)

---
 src/en/ref/Command Line.adoc | 28 ++++++----------------------
 1 file changed, 6 insertions(+), 22 deletions(-)

diff --git a/src/en/ref/Command Line.adoc b/src/en/ref/Command Line.adoc
index a624355432..9d3772b8da 100644
--- a/src/en/ref/Command Line.adoc	
+++ b/src/en/ref/Command Line.adoc	
@@ -2,39 +2,23 @@
 === Command Line Usage
 
 
-Grails incorporates the powerful build system http://gradle.org[Gradle].
+Grails incorporates a CLI and also uses the powerful build system https://gradle.org[Gradle].
 
 The basic usage scenario is:
 
-[source,groovy]
+[source,console]
 ----
-grails <<environment>>* <<command name>>
+grails <<command name>> <<options>>*
 ----
 
-Grails searches in the following directories for Gant scripts to execute:
+When running Gradle tasks you can specify the environment that the command executes in with an optional grails.env parameter, either with one of the built-in environment names:
 
-* `USER_HOME/.grails/scripts`
-* `PROJECT_HOME/src/main/scripts/`
-* `PROJECT_HOME/plugins/*/scripts`
-* `GRAILS_HOME/scripts`
-
-If multiple matches are found Grails will give you a choice of which one to execute.
-
-You can specify the environment that the command executes in with an optional grails.env parameter, either with one of the built-in environment names:
-
-[source,groovy]
+[source,console]
 ----
 ./gradlew bootRun -Dgrails.env=dev
 ./gradlew bootRun -Dgrails.env=test
 ./gradlew bootRun -Dgrails.env=prod
-
-----
-
-Or using a -D argument if the name is not one of the three standard names:
-
-[source,groovy]
-----
-grails -Dgrails.env=uat run-app
+./gradlew bootRun -Dgrails.env=custom
 ----
 
 Refer to the user guide section on link:{guidePath}/commandLine.html[The Command Line] for more information.