[solr] branch branch_9x updated: Update cloud-script.adoc (#1796)

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

epugh pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/branch_9x by this push:
     new 6b9fda8258d Update cloud-script.adoc (#1796)
6b9fda8258d is described below

commit 6b9fda8258d8c9c4396ab52e3bf8144f66222d76
Author: mariemat <ma...@gmail.com>
AuthorDate: Tue Jul 25 23:56:22 2023 +0200

    Update cloud-script.adoc (#1796)
    
    emphasize the command to execute
---
 dev-docs/cloud-script.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-docs/cloud-script.adoc b/dev-docs/cloud-script.adoc
index 9ca87deb1b2..e3449c7b3de 100644
--- a/dev-docs/cloud-script.adoc
+++ b/dev-docs/cloud-script.adoc
@@ -18,7 +18,7 @@ Typical usage of the script is:
 1. Copy the script to a location outside the `./solr/` working copy such as `<GIT_CHECKOUT>/../solr-testing`. Trying to use it from within the working copy will leave you fighting version control to avoid checking in files.
 2. Edit the script to provide a proper back reference to your working copy for `DEFAULT_VCS_WORKSPACE` (the default is `../code/solr`)
 3. Start a local zookeeper instance. This zookeeper must be running on localhost, but the port can be adjusted with a `-z` option passed to the script.  `docker run -p 2181:2181 zookeeper` is one option to start up a local Zookeeper.
-4. run ./cloud.sh new -r
+4. run `./cloud.sh new -r`
 
 The command in the final step will: