Received bad advice for shell commands ...

Author: Adambean

README.md

@@ -374,22 +374,28 @@ gitlab_rails['ldap_servers'] = {
 
 Once you've configured this tool you can run it from a CLI using:
 
-$ php bin/console ldap:sync -d
+```console
+php bin/console ldap:sync -d
+```
 
 Depending on your system's PHP installation you may need to use `php-cli` instead of `php`. (This typically only occurs on WHM/cPanel based servers configured to host PHP via the fast process manager, PHP-FPM.)
 
 **The `-d` option is important for your first run.** This enables "dry run" mode, meaning no changes will be persisted to your Gitlab instances. After running this tool you should evaluate the changes that will be made based on the output, then run it again without the `-d` option to persist the changes.
 
 If you'd like to see more verbose output you can add up to 3 `-v` switches, for example:
 
-$ php bin/console ldap:sync -v
-$ php bin/console ldap:sync -vv
-$ php bin/console ldap:sync -vvv
+```console
+php bin/console ldap:sync -v
+php bin/console ldap:sync -vv
+php bin/console ldap:sync -vvv
+```
 
 If you'd like to only sync with a single Gitlab instance you can specify the name of it as per your configuration as an argument, for example:
 
-$ php bin/console ldap:sync athena
-$ php bin/console ldap:sync demeter
+```console
+php bin/console ldap:sync athena
+php bin/console ldap:sync demeter
+```
 
 ## Built With