Merge ~mthaddon/charm-grafana/+git/grafana-charm:indent-code-readme into ~prometheus-charmers/charm-grafana:master

[Tom Haddon]

Correct indentation of README.md for display on jaas.ai

Correct indentation of README.md for display on jaas.ai.

Compare https://jaas.ai/u/mthaddon/grafana with https://jaas.ai/grafana to see the difference.

[🤖 Canonical IS Merge Bot (canonical-is-mergebot)]

This merge proposal is being monitored by mergebot. Change the status to Approved to merge.

[Benjamin Allot (ballot)]

+1

review: Approve

[🤖 Canonical IS Merge Bot (canonical-is-mergebot)]

Change successfully merged at revision 4992811f9cfc11c801e7e450e51d13be91954188

diff --git a/README.md b/README.md
index 8591ce1..bd6e7b8 100644
--- a/README.md
+++ b/README.md
@@ -12,24 +12,24 @@ Above will automatically configure prometheus as grafana datasource
 If admin password is not set using configuration option it is autogenerated.
 
 To retrieve autogenerated password run:
-    $ juju run-action --wait grafana/0 get-admin-password
+
+    juju run-action --wait grafana/0 get-admin-password
 
 #Actions
 
 This charm supports importing dashboards, simply run:
 
- $ juju run-action --wait grafana/0 import-dashboard dashboard="$(base64 mydashboard.json)"
+    juju run-action --wait grafana/0 import-dashboard dashboard="$(base64 mydashboard.json)"
 
 where mydashboard.json is a json file:
 
- { "dashboard": { exported-json-dashboard },
-   "overwrite": true }
+    { "dashboard": { exported-json-dashboard }, "overwrite": true }
 
 If you don't want to overwrite the dashboard, set overwrite to false.
 
 There is also an action to create an API key, run:
 
- $ juju run-action --wait grafana/0 create-api-key keyname=<name> keyrole=<role>
+    juju run-action --wait grafana/0 create-api-key keyname=<name> keyrole=<role>
 
 where the keyrole is one of Viewer, Editor, Read Only Editor or Admin.
 
@@ -40,11 +40,11 @@ organisation.
 
 You can retrieve the admin password, via:
 
- $ juju run-action --wait grafana/0 get-admin-password
+    juju run-action --wait grafana/0 get-admin-password
 
 You can create a user:
 
- $ juju run-action -w grafana/0 create-user name="John Citizen" \
+    juju run-action -w grafana/0 create-user name="John Citizen" \
         email="[e-mail]" login="john" password="redacted" \
         role="Viewer"
 
@@ -53,7 +53,7 @@ This will create the user in the default organisation.
 
 To reset a user's password:
 
- $ juju run-action --wait grafana/0 set-user-password \
+    juju run-action --wait grafana/0 set-user-password \
         login=john new-password=citizen2
 
 This again assumes the user is in the default organisation, if it
@@ -61,12 +61,12 @@ isn't it won't find the user.
 
 If you need to change the user's role, run:
 
- $ juju run-action --wait grafana/0 change-user-role login="john" \
+    juju run-action --wait grafana/0 change-user-role login="john" \
         new-role="Admin"
 
 To delete a user, you simply run:
 
- $ juju run-action --wait grafana/0 delete-user login=john
+    juju run-action --wait grafana/0 delete-user login=john
 
 
 #Auth proxy
@@ -74,7 +74,7 @@ To delete a user, you simply run:
 If deployed behind a reverse proxy, you can configure Grafana to let
 it handle authentication by enabled auth-proxy.
 
- $ juju config grafana auth-proxy=true
+    juju config grafana auth-proxy=true
 
 Check grafana [documentation](https://grafana.com/docs/auth/auth-proxy/#auth-proxy-authentication)
 on how to configure apache as the reverse proxy.
@@ -84,7 +84,7 @@ To change the default permissions of a user, use the change-user-role
 action passing the openID identifier or the email if the user updated it 
 as the "login":
 
- $ juju run-action --wait grafana/0 change-user-role \
+    juju run-action --wait grafana/0 change-user-role \
         login="[e-mail]" new-role="Admin"
 
 If not all URL paths are behind the reverse proxy auth,