Docs: Fixed lazy numbering in all documentation files (#27975)

54df058b · DECarreras · GitHub · c3f277a6 · 54df058b · 54df058b
Commit 54df058b authored Oct 01, 2020 by DECarreras Committed by GitHub Oct 01, 2020
33 changed files
--- a/contribute/templates/doc-concept-template.md
+++ b/contribute/templates/doc-concept-template.md
@@ -30,12 +30,12 @@ Concept topics or sections explain *what* and *why*. They do not explain *how*. 
 Continuing the example in the previous section, here is a sample Grafana workflow. 
 1. Install Grafana. <link to task for installing Grafana>
-2. Set up data sources. <link to data sources concept topic, which links to data source task topics>
+1. Set up data sources. <link to data sources concept topic, which links to data source task topics>
-3. Create panels. <link to panel concept topic, which links to tasks>
+1. Create panels. <link to panel concept topic, which links to tasks>
-4. Create dashboards.  <link to panel concept topic, which links to tasks>
+1. Create dashboards.  <link to panel concept topic, which links to tasks>
-5. Enter queries. <link to query editor concept topic>
+1. Enter queries. <link to query editor concept topic>
-6. Add users. <link to user management concept topic, which links to tasks>
+1. Add users. <link to user management concept topic, which links to tasks>
-7. Create playlists. <link to Playlist topic that contains concept information and tasks>
+1. Create playlists. <link to Playlist topic that contains concept information and tasks>
 ## Next steps

--- a/contribute/templates/doc-task-template.md
+++ b/contribute/templates/doc-task-template.md
@@ -42,7 +42,7 @@ Write one-step tasks as simple sentences, not as unordered lists or numbered lis
 Short tasks can be grouped. How short constitutes "short" is a judgment call based on number of steps and how long individual steps are.
 1. Use your judgment.
-2. Ask your coworkers or someone on the Comm team for advice if you aren't sure.
+1. Ask your coworkers or someone on the Comm team for advice if you aren't sure.
 ## Next steps

--- a/docs/README.md
+++ b/docs/README.md
@@ -9,7 +9,7 @@ Docker >= 2.1.0.3
 ## Build the doc site
 1. In the command line, make sure you are in the docs folder: `cd docs`.
-2. Run `make docs`. This launches a preview of the docs website at `http://localhost:3002/docs/grafana/latest/` which will refresh automatically when changes to content in the `sources` directory are made.
+1. Run `make docs`. This launches a preview of the docs website at `http://localhost:3002/docs/grafana/latest/` which will refresh automatically when changes to content in the `sources` directory are made.
 ---

--- a/docs/sources/administration/image_rendering.md
+++ b/docs/sources/administration/image_rendering.md
@@ -83,20 +83,20 @@ docker-compose up
 The following example describes how to build and run the remote HTTP rendering service as a standalone Node.js application and configure Grafana appropriately.
 1. Clone the [Grafana image renderer plugin](https://grafana.com/grafana/plugins/grafana-image-renderer) Git repository.
-2. Install dependencies and build:
+1. Install dependencies and build:
    ```bash
    yarn install --pure-lockfile
    yarn run build
    ```
-3. Run the server:
+1. Run the server:
    ```bash
    node build/app.js server --port=8081
    ```
-4. Update Grafana configuration:
+1. Update Grafana configuration:
    ```
    [rendering]
@@ -104,7 +104,7 @@ The following example describes how to build and run the remote HTTP rendering s
    callback_url = http://localhost:3000/
    ```
-5. Restart Grafana.
+1. Restart Grafana.
 ## PhantomJS

--- a/docs/sources/alerting/notifications.md
+++ b/docs/sources/alerting/notifications.md
@@ -175,15 +175,15 @@ In DingTalk PC Client:
 1. Click "more" icon on upper right of the panel.
-2. Click "Robot Manage" item in the pop menu, there will be a new panel call "Robot Manage".
+1. Click "Robot Manage" item in the pop menu, there will be a new panel call "Robot Manage".
-3. In the  "Robot Manage" panel, select "customized: customized robot with Webhook".
+1. In the  "Robot Manage" panel, select "customized: customized robot with Webhook".
-4. In the next new panel named "robot detail", click "Add" button.
+1. In the next new panel named "robot detail", click "Add" button.
-5. In "Add Robot" panel, input a nickname for the robot and select a "message group" which the robot will join in. click "next".
+1. In "Add Robot" panel, input a nickname for the robot and select a "message group" which the robot will join in. click "next".
-6. There will be a Webhook URL in the panel, looks like this: https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxx. Copy this URL to the Grafana DingTalk setting page and then click "finish".
+1. There will be a Webhook URL in the panel, looks like this: https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxx. Copy this URL to the Grafana DingTalk setting page and then click "finish".
 DingTalk supports the following "message type": `text`, `link` and `markdown`. Only the `link` message type is supported.
@@ -194,7 +194,7 @@ There are a couple of configuration options which need to be set up in Grafana U
 1. Kafka REST Proxy endpoint.
-2. Kafka Topic.
+1. Kafka Topic.
 Once these two properties are set, you can send the alerts to Kafka for further processing or throttling.

--- a/docs/sources/auth/generic-oauth.md
+++ b/docs/sources/auth/generic-oauth.md
@@ -56,11 +56,11 @@ You can also specify the SSL/TLS configuration used by the client.
 Grafana will attempt to determine the user's e-mail address by querying the OAuth provider as described below in the following order until an e-mail address is found:
 1. Check for the presence of an e-mail address via the `email` field encoded in the OAuth `id_token` parameter.
-2. Check for the presence of an e-mail address using the [JMESPath](http://jmespath.org/examples.html) specified via the `email_attribute_path` configuration option. The JSON used for the path lookup is the HTTP response obtained from querying the UserInfo endpoint specified via the `api_url` configuration option.
+1. Check for the presence of an e-mail address using the [JMESPath](http://jmespath.org/examples.html) specified via the `email_attribute_path` configuration option. The JSON used for the path lookup is the HTTP response obtained from querying the UserInfo endpoint specified via the `api_url` configuration option.
 **Note**: Only available in Grafana v6.4+.
-3. Check for the presence of an e-mail address in the `attributes` map encoded in the OAuth `id_token` parameter. By default Grafana will perform a lookup into the attributes map using the `email:primary` key, however, this is configurable and can be adjusted by using the `email_attribute_name` configuration option.
+1. Check for the presence of an e-mail address in the `attributes` map encoded in the OAuth `id_token` parameter. By default Grafana will perform a lookup into the attributes map using the `email:primary` key, however, this is configurable and can be adjusted by using the `email_attribute_name` configuration option.
-4. Query the `/emails` endpoint of the OAuth provider's API (configured with `api_url`) and check for the presence of an e-mail address marked as a primary address.
+1. Query the `/emails` endpoint of the OAuth provider's API (configured with `api_url`) and check for the presence of an e-mail address marked as a primary address.
-5. If no e-mail address is found in steps (1-4), then the e-mail address of the user is set to the empty string.
+1. If no e-mail address is found in steps (1-4), then the e-mail address of the user is set to the empty string.
 Grafana will also attempt to do role mapping through OAuth as described below.
@@ -85,10 +85,10 @@ You can customize the attribute name used to extract the ID token from the retur
    - Name: Grafana
    - Type: Regular Web Application
-2.  Go to the Settings tab and set:
+1. Go to the Settings tab and set:
    - Allowed Callback URLs: `https://<grafana domain>/login/generic_oauth`
-3. Click Save Changes, then use the values at the top of the page to configure Grafana:
+1. Click Save Changes, then use the values at the top of the page to configure Grafana:
    ```bash
    [auth.generic_oauth]
@@ -126,19 +126,19 @@ allowed_organizations =
 1. Create a new Custom OpenID Connect application configuration in the Centrify dashboard.
-2.  Create a memorable unique Application ID, e.g. "grafana", "grafana_aws", etc.
+1. Create a memorable unique Application ID, e.g. "grafana", "grafana_aws", etc.
-3.  Put in other basic configuration (name, description, logo, category)
+1. Put in other basic configuration (name, description, logo, category)
-4.  On the Trust tab, generate a long password and put it into the OpenID Connect Client Secret field.
+1. On the Trust tab, generate a long password and put it into the OpenID Connect Client Secret field.
-5.  Put the URL to the front page of your Grafana instance into the "Resource Application URL" field.
+1. Put the URL to the front page of your Grafana instance into the "Resource Application URL" field.
-6.  Add an authorized Redirect URI like https://your-grafana-server/login/generic_oauth
+1. Add an authorized Redirect URI like https://your-grafana-server/login/generic_oauth
-7.  Set up permissions, policies, etc. just like any other Centrify app
+1. Set up permissions, policies, etc. just like any other Centrify app
-8.  Configure Grafana as follows:
+1. Configure Grafana as follows:
    ```bash
    [auth.generic_oauth]
@@ -163,11 +163,11 @@ allowed_organizations =
    - Login URL: `https://<grafana domain>/login/generic_oauth`
    then:
-2.  Add an App to the Grafana Connector:
+1. Add an App to the Grafana Connector:
    - Display Name: Grafana
    then:
-3.  Under the SSO tab on the Grafana App details page you'll find the Client ID and Client Secret.
+1. Under the SSO tab on the Grafana App details page you'll find the Client ID and Client Secret.
    Your OneLogin Domain will match the URL you use to access OneLogin.

--- a/docs/sources/auth/google.md
+++ b/docs/sources/auth/google.md
@@ -19,15 +19,15 @@ To enable Google OAuth2 you must register your application with Google. Google w
 First, you need to create a Google OAuth Client:
 1. Go to https://console.developers.google.com/apis/credentials.
-2. Click **Create Credentials**, then click **OAuth Client ID** in the drop-down menu
+1. Click **Create Credentials**, then click **OAuth Client ID** in the drop-down menu
-3. Enter the following:
+1. Enter the following:
   - Application Type: Web Application
   - Name: Grafana
   - Authorized JavaScript Origins: https://grafana.mycompany.com
   - Authorized Redirect URLs: https://grafana.mycompany.com/login/google
   - Replace https://grafana.mycompany.com with the URL of your Grafana instance.
-4. Click Create
+1. Click Create
-5. Copy the Client ID and Client Secret from the 'OAuth Client' modal
+1. Copy the Client ID and Client Secret from the 'OAuth Client' modal
 ## Enable Google OAuth in Grafana

--- a/docs/sources/auth/ldap.md
+++ b/docs/sources/auth/ldap.md
@@ -114,8 +114,8 @@ Within this view, you'll be able to see which LDAP servers are currently reachab
 To use the debug view:
 1. Type the username of a user that exists within any of your LDAP server(s)
- 2. Then, press "Run"
+ 1. Then, press "Run"
- 3. If the user is found within any of your LDAP instances, the mapping information is displayed
+ 1. If the user is found within any of your LDAP instances, the mapping information is displayed
 {{< docs-imagebox img="/img/docs/ldap_debug_mapping_testing.png" class="docs-image--no-shadow" max-width="600px" >}}

--- a/docs/sources/dashboards/_index.md
+++ b/docs/sources/dashboards/_index.md
@@ -16,10 +16,10 @@ A _dashboard_ is a set of one or more panels organized and arranged into one or 
 <img src="/img/docs/v50/dashboard_annotated.png" class="no-shadow" width="700px">
 1. Zoom out time range
-2. Time picker dropdown. Here you can access relative time range options, auto refresh options and set custom absolute time ranges.
+1. Time picker dropdown. Here you can access relative time range options, auto refresh options and set custom absolute time ranges.
-3. Manual refresh button. Will cause all panels to refresh (fetch new data).
+1. Manual refresh button. Will cause all panels to refresh (fetch new data).
-4. Dashboard panel. Click the panel title to edit panels.
+1. Dashboard panel. Click the panel title to edit panels.
-5. Graph legend. You can change series colors, y-axis and series visibility directly from the legend.
+1. Graph legend. You can change series colors, y-axis and series visibility directly from the legend.
 ## Dashboard header
@@ -30,12 +30,12 @@ Click the new Dashboard link on the right side of the Dashboard picker. You now 
 The image above shows you the top header for a Dashboard.
 1. Side menubar toggle: This toggles the side menu, allowing you to focus on the data presented in the dashboard. The side menu provides access to features unrelated to a Dashboard such as Users, Organizations, and Data Sources.
-2. Dashboard dropdown: This dropdown shows you which Dashboard you are currently viewing, and allows you to easily switch to a new Dashboard. From here you can also create a new Dashboard or folder, import existing Dashboards, and manage Dashboard playlists.
+1. Dashboard dropdown: This dropdown shows you which Dashboard you are currently viewing, and allows you to easily switch to a new Dashboard. From here you can also create a new Dashboard or folder, import existing Dashboards, and manage Dashboard playlists.
-3. Add Panel: Adds a new panel to the current Dashboard
+1. Add Panel: Adds a new panel to the current Dashboard
-4. Star Dashboard: Star (or unstar) the current Dashboard. Starred Dashboards will show up on your own Home Dashboard by default, and are a convenient way to mark Dashboards that you're interested in.
+1. Star Dashboard: Star (or unstar) the current Dashboard. Starred Dashboards will show up on your own Home Dashboard by default, and are a convenient way to mark Dashboards that you're interested in.
-5. Share Dashboard: Share the current dashboard by creating a link or create a static Snapshot of it. Make sure the Dashboard is saved before sharing.
+1. Share Dashboard: Share the current dashboard by creating a link or create a static Snapshot of it. Make sure the Dashboard is saved before sharing.
-6. Save dashboard: The current Dashboard will be saved with the current Dashboard name.
+1. Save dashboard: The current Dashboard will be saved with the current Dashboard name.
-7. Settings: Manage Dashboard settings and features such as Templating and Annotations.
+1. Settings: Manage Dashboard settings and features such as Templating and Annotations.
 ## Manage dashboards

--- a/docs/sources/dashboards/search.md
+++ b/docs/sources/dashboards/search.md
@@ -16,11 +16,11 @@ Dashboards can be searched by the dashboard name, filtered by one (or many) tags
 <img class="no-shadow" src="/img/docs/v50/dashboard_search_annotated.png" width="700px">
 1. `Search Bar`: The search bar allows you to enter any string and search both database and file based dashboards in real-time.
-2. `Starred`: Here you find all your starred dashboards.
+1. `Starred`: Here you find all your starred dashboards.
-3. `Recent`: Here you find the latest created dashboards.
+1. `Recent`: Here you find the latest created dashboards.
-4. `Folders`: The tags filter allows you to filter the list by dashboard tags.
+1. `Folders`: The tags filter allows you to filter the list by dashboard tags.
-5. `Root`: The root contains all dashboards that are not placed in a folder.
+1. `Root`: The root contains all dashboards that are not placed in a folder.
-6. `Tags`: The tags filter allows you to filter the list by dashboard tags.
+1. `Tags`: The tags filter allows you to filter the list by dashboard tags.
 When using only a keyboard, you can use your keyboard arrow keys to navigate the results, hit enter to open the selected dashboard.

--- a/docs/sources/developers/plugins/legacy/_index.md
+++ b/docs/sources/developers/plugins/legacy/_index.md
@@ -15,8 +15,8 @@ Grafana already has a strong community of contributors and plugin developers. By
 ## Short version
 1. [Set up Grafana](https://github.com/grafana/grafana/blob/master/contribute/developer-guide.md)
-2. Clone an example plugin into `/var/lib/grafana/plugins` or `data/plugins` (relative to grafana git repo if you're running development version from source dir)
+1. Clone an example plugin into `/var/lib/grafana/plugins` or `data/plugins` (relative to grafana git repo if you're running development version from source dir)
-3. Use one of our example plugins as a starting point
+1. Use one of our example plugins as a starting point
 Example plugins
@@ -87,8 +87,8 @@ export { WorldmapCtrl as PanelCtrl };
 There are three ways that you can start developing a Grafana plugin.
 1. Set up a Grafana development environment. [(described here)](https://github.com/grafana/grafana/blob/master/contribute/developer-guide.md) and place your plugin in the `data/plugins` folder.
-2. Install Grafana and place your plugin in the plugins directory which is set in your [config file](/administration/configuration). By default this is `/var/lib/grafana/plugins` on Linux systems.
+1. Install Grafana and place your plugin in the plugins directory which is set in your [config file](/administration/configuration). By default this is `/var/lib/grafana/plugins` on Linux systems.
-3. Place your plugin directory anywhere you like and specify it grafana.ini.
+1. Place your plugin directory anywhere you like and specify it grafana.ini.
 We encourage people to set up the full Grafana environment so that you can get inspiration from the rest of the Grafana code base.

--- a/docs/sources/developers/plugins/legacy/style-guide.md
+++ b/docs/sources/developers/plugins/legacy/style-guide.md
@@ -146,8 +146,8 @@ We recommend that you use a linter for your JavaScript. For ES6, the standard li
 ### ES6 features
 1. Use `const` if a variable is not going to be reassigned.
-2. Prefer to use `let` instead `var` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-var-to-letconst))
+1. Prefer to use `let` instead `var` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-var-to-letconst))
-3. Use arrow functions, which don’t shadow `this` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-function-expressions-to-arrow-functions)):
+1. Use arrow functions, which don’t shadow `this` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-function-expressions-to-arrow-functions)):
   ```js
   testDatasource() {
@@ -170,7 +170,7 @@ We recommend that you use a linter for your JavaScript. For ES6, the standard li
   }
   ```
-4. Use native _Promise_ object:
+1. Use native _Promise_ object:
   ```js
   metricFindQuery(query) {
@@ -190,4 +190,4 @@ We recommend that you use a linter for your JavaScript. For ES6, the standard li
   }
   ```
-5. If using Lodash, then be consistent and prefer that to the native ES6 array functions.
+1. If using Lodash, then be consistent and prefer that to the native ES6 array functions.
--- a/docs/sources/enterprise/datasource_permissions.md
+++ b/docs/sources/enterprise/datasource_permissions.md
@@ -28,8 +28,8 @@ When permissions are enabled for a data source in an organization, you restrict 
 **Enable permissions for a data source:**
 1. Navigate to **Configuration > Data Sources**.
-2. Select the data source you want to enable permissions for.
+1. Select the data source you want to enable permissions for.
-3. On the Permissions tab, click **Enable**.
+1. On the Permissions tab, click **Enable**.
 <div class="clearfix"></div>
@@ -44,10 +44,10 @@ After you have enabled permissions for a data source you can assign query permis
 **Assign query permission to users and teams:**
 1. Navigate to **Configuration > Data Sources**.
-2. Select the data source you want to assign query permissions for.
+1. Select the data source you want to assign query permissions for.
-3. On the Permissions tab, click **Add Permission**.
+1. On the Permissions tab, click **Add Permission**.
-4. Select **Team** or **User**.
+1. Select **Team** or **User**.
-5. Select the entity you want to allow query access and then click **Save**.
+1. Select the entity you want to allow query access and then click **Save**.
 <div class="clearfix"></div>
@@ -62,7 +62,7 @@ Note that *all* existing permissions created for the data source will be deleted
 **Disable permissions for a data source:**
 1. Navigate to **Configuration > Data Sources**.
-2. Select the data source you want to disable permissions for.
+1. Select the data source you want to disable permissions for.
-3. On the Permissions tab, click **Disable Permissions**.
+1. On the Permissions tab, click **Disable Permissions**.
 <div class="clearfix"></div>
--- a/docs/sources/enterprise/license-expiration.md
+++ b/docs/sources/enterprise/license-expiration.md
@@ -23,10 +23,10 @@ If your license has expired most of Grafana keeps working as normal. Some enterp
    ```
    The configuration file's location may also be overridden by the `GF_ENTERPRISE_LICENSE_PATH` environment variable.
-2. Log in to your [Grafana Cloud Account](https://grafana.com/login) and make sure you're in the correct organization in the dropdown at the top of the page.
+1. Log in to your [Grafana Cloud Account](https://grafana.com/login) and make sure you're in the correct organization in the dropdown at the top of the page.
-3. Under the **Grafana Enterprise** section in the menu bar to the left, choose licenses and download the currently valid license with which you want to run Grafana. If you cannot see a valid license on Grafana.com, please contact your account manager at Grafana Labs to renew your subscription.
+1. Under the **Grafana Enterprise** section in the menu bar to the left, choose licenses and download the currently valid license with which you want to run Grafana. If you cannot see a valid license on Grafana.com, please contact your account manager at Grafana Labs to renew your subscription.
-4. Replace the current `license.jwt`-file with the one you've just downloaded.
+1. Replace the current `license.jwt`-file with the one you've just downloaded.
-5. Restart Grafana.
+1. Restart Grafana.
 ## If your license expires

--- a/docs/sources/explore/index.md
+++ b/docs/sources/explore/index.md
@@ -72,7 +72,7 @@ All queries that have been starred in the Query history tab are displayed in the
 By default, query history shows you the most recent queries. You can sort your history by date or by data source name in ascending or descending order.
 1. Click the **Sort queries by** field.
-2. Select one of the following options:
+1. Select one of the following options:
   - Newest first
   - Oldest first
   - Data source A-Z
@@ -85,7 +85,7 @@ By default, query history shows you the most recent queries. You can sort your h
 Filter query history in Query history and Starred tab by data source name:
 1. Click the **Filter queries for specific data source(s)** field.
-2. Select the data source for which you would like to filter your history. You can select multiple data sources.
+1. Select the data source for which you would like to filter your history. You can select multiple data sources.
 In **Query history** tab it is also possible to filter queries by date using the slider:

--- a/docs/sources/features/datasources/azuremonitor.md
+++ b/docs/sources/features/datasources/azuremonitor.md
@@ -33,34 +33,34 @@ The data source can access metrics from four different services. You can configu
 1. Accessed from the Grafana main menu, newly installed data sources can be added immediately within the Data Sources section. Next, click the "Add data source" button in the upper right. The Azure Monitor data source will be available for selection in the Cloud section in the list of data sources.
-2. In the name field, Grafana will automatically fill in a name for the data source - `Azure Monitor` or something like `Azure Monitor - 3`. If you are going to configure multiple data sources, then change the name to something more informative.
+1. In the name field, Grafana will automatically fill in a name for the data source - `Azure Monitor` or something like `Azure Monitor - 3`. If you are going to configure multiple data sources, then change the name to something more informative.
-3. If you are using Azure Monitor, you need 4 pieces of information from the Azure portal (see link above for detailed instructions):
+1. If you are using Azure Monitor, you need 4 pieces of information from the Azure portal (see link above for detailed instructions):
   - **Tenant Id** (Azure Active Directory -> Properties -> Directory ID)
   - **Client Id** (Azure Active Directory -> App Registrations -> Choose your app -> Application ID)
   - **Client Secret** (Azure Active Directory -> App Registrations -> Choose your app -> Keys)
   - **Default Subscription Id** (Subscriptions -> Choose subscription -> Overview -> Subscription ID)
-4. Paste these four items into the fields in the Azure Monitor API Details section:
+1. Paste these four items into the fields in the Azure Monitor API Details section:
   {{< docs-imagebox img="/img/docs/v62/config_1_azure_monitor_details.png" class="docs-image--no-shadow" caption="Azure Monitor Configuration Details" >}}
   - The Subscription Id can be changed per query. Save the data source and refresh the page to see the list of subscriptions available for the specified Client Id.
-5. If you are also using the Azure Log Analytics service, then you need to specify these two config values (or you can reuse the Client Id and Secret from the previous step).
+1. If you are also using the Azure Log Analytics service, then you need to specify these two config values (or you can reuse the Client Id and Secret from the previous step).
   - Client Id (Azure Active Directory -> App Registrations -> Choose your app -> Application ID)
   - Client Secret (Azure Active Directory -> App Registrations -> Choose your app -> Keys -> Create a key -> Use client secret)
-6. If you are using Application Insights, then you need two pieces of information from the Azure Portal (see link above for detailed instructions):
+1. If you are using Application Insights, then you need two pieces of information from the Azure Portal (see link above for detailed instructions):
   - Application ID
   - API Key
-7. Paste these two items into the appropriate fields in the Application Insights API Details section:
+1. Paste these two items into the appropriate fields in the Application Insights API Details section:
   {{< docs-imagebox img="/img/docs/v62/config_2_app_insights_api_details.png" class="docs-image--no-shadow" caption="Application Insights Configuration Details" >}}
-8. Test that the configuration details are correct by clicking on the "Save & Test" button:
+1. Test that the configuration details are correct by clicking on the "Save & Test" button:
   {{< docs-imagebox img="/img/docs/v62/config_3_save_and_test.png" class="docs-image--no-shadow" caption="Save and Test" >}}
 Alternatively on step 4 if creating a new Azure Active Directory App, use the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/?view=azure-cli-latest):

--- a/docs/sources/features/datasources/cloudmonitoring.md
+++ b/docs/sources/features/datasources/cloudmonitoring.md
@@ -21,10 +21,10 @@ Grafana ships with built-in support for Google Cloud Monitoring. Just add it as 
 ## Adding the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
+1. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select `Google Cloud Monitoring` from the _Type_ dropdown.
+1. Select `Google Cloud Monitoring` from the _Type_ dropdown.
-5. Upload or paste in the Service Account Key file. See below for steps on how to create a Service Account Key file.
+1. Upload or paste in the Service Account Key file. See below for steps on how to create a Service Account Key file.
 > **Note:** If you're not seeing the `Data Sources` link in your side menu, then your current user account does not have the `Admin` role for the current organization.
@@ -56,24 +56,24 @@ Click on the links above and click the `Enable` button:
 #### Create a GCP Service Account for a Project
 1. Navigate to the [APIs and Services Credentials page](https://console.cloud.google.com/apis/credentials).
-2. Click on the `Create credentials` dropdown/button and choose the `Service account key` option.
+1. Click on the `Create credentials` dropdown/button and choose the `Service account key` option.
   {{< docs-imagebox img="/img/docs/v71/cloudmonitoring_create_service_account_button.png" class="docs-image--no-shadow" caption="Create service account button" >}}
-3. On the `Create service account key` page, choose key type `JSON`. Then in the `Service Account` dropdown, choose the `New service account` option:
+1. On the `Create service account key` page, choose key type `JSON`. Then in the `Service Account` dropdown, choose the `New service account` option:
   {{< docs-imagebox img="/img/docs/v71/cloudmonitoring_create_service_account_key.png" class="docs-image--no-shadow" caption="Create service account key" >}}
-4. Some new fields will appear. Fill in a name for the service account in the `Service account name` field and then choose the `Monitoring Viewer` role from the `Role` dropdown:
+1. Some new fields will appear. Fill in a name for the service account in the `Service account name` field and then choose the `Monitoring Viewer` role from the `Role` dropdown:
   {{< docs-imagebox img="/img/docs/v71/cloudmonitoring_service_account_choose_role.png" class="docs-image--no-shadow" caption="Choose role" >}}
-5. Click the Create button. A JSON key file will be created and downloaded to your computer. Store this file in a secure place as it allows access to your Google Cloud Monitoring data.
+1. Click the Create button. A JSON key file will be created and downloaded to your computer. Store this file in a secure place as it allows access to your Google Cloud Monitoring data.
-6. Upload it to Grafana on the data source Configuration page. You can either upload the file or paste in the contents of the file.
+1. Upload it to Grafana on the data source Configuration page. You can either upload the file or paste in the contents of the file.
   {{< docs-imagebox img="/img/docs/v71/cloudmonitoring_grafana_upload_key.png" class="docs-image--no-shadow" caption="Upload service key file to Grafana" >}}
-7. The file contents will be encrypted and saved in the Grafana database. Don't forget to save after uploading the file!
+1. The file contents will be encrypted and saved in the Grafana database. Don't forget to save after uploading the file!
   {{< docs-imagebox img="/img/docs/v71/cloudmonitoring_grafana_key_uploaded.png" class="docs-image--no-shadow" caption="Service key file is uploaded to Grafana" >}}
@@ -82,8 +82,8 @@ Click on the links above and click the `Enable` button:
 If Grafana is running on a Google Compute Engine (GCE) virtual machine, it is possible for Grafana to automatically retrieve default credentials from the metadata server. This has the advantage of not needing to generate a private key file for the service account and also not having to upload the file to Grafana. However for this to work, there are a few preconditions that need to be met.
 1. First of all, you need to create a Service Account that can be used by the GCE virtual machine. See detailed instructions on how to do that [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#createanewserviceaccount).
-2. Make sure the GCE virtual machine instance is being run as the service account that you just created. See instructions [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#using).
+1. Make sure the GCE virtual machine instance is being run as the service account that you just created. See instructions [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#using).
-3. Allow access to the `Cloud Monitoring API` scope.
+1. Allow access to the `Cloud Monitoring API` scope.
 Read more about creating and enabling service accounts for GCE VM instances [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances).
@@ -100,10 +100,10 @@ The metric query editor allows you to select metrics, group/aggregate by labels 
 To create a metric query, follow these steps:
 1. Choose the option **Metrics** in the **Query Type** dropdown
-2. Choose a project from the **Project** dropdown
+1. Choose a project from the **Project** dropdown
-3. Choose a Google Cloud Platform service from the **Service** dropdown
+1. Choose a Google Cloud Platform service from the **Service** dropdown
-4. Choose a metric from the **Metric** dropdown.
+1. Choose a metric from the **Metric** dropdown.
-5. Use the plus and minus icons in the filter and group by sections to add/remove filters or group by clauses. This step is optional.
+1. Use the plus and minus icons in the filter and group by sections to add/remove filters or group by clauses. This step is optional.
 Google Cloud Monitoring metrics can be of different kinds (GAUGE, DELTA, CUMULATIVE) and these kinds have support for different aggregation options (reducers and aligners). The Grafana query editor shows the list of available aggregation methods for a selected metric and sets a default reducer and aligner when you select the metric. Units for the Y-axis are also automatically selected by the query editor.
@@ -198,10 +198,10 @@ The SLO query builder in the Google Cloud Monitoring data source allows you to d
 To create an SLO query, follow these steps:
 1. Choose the option **Service Level Objectives (SLO)** in the **Query Type** dropdown.
-2. Choose a project from the **Project** dropdown.
+1. Choose a project from the **Project** dropdown.
-3. Choose an [SLO service](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/services) from the **Service** dropdown.
+1. Choose an [SLO service](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/services) from the **Service** dropdown.
-4. Choose an [SLO](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/services.serviceLevelObjectives) from the **SLO** dropdown.
+1. Choose an [SLO](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/services.serviceLevelObjectives) from the **SLO** dropdown.
-5. Choose a [time series selector](https://cloud.google.com/monitoring/service-monitoring/timeseries-selectors#ts-selector-list) from the **Selector** dropdown.
+1. Choose a [time series selector](https://cloud.google.com/monitoring/service-monitoring/timeseries-selectors#ts-selector-list) from the **Selector** dropdown.
 The friendly names for the time series selectors are shown in Grafana. Here is the mapping from the friendly name to the system name that is used in the Service Monitoring documentation:

--- a/docs/sources/features/datasources/cloudwatch.md
+++ b/docs/sources/features/datasources/cloudwatch.md
@@ -19,8 +19,8 @@ build dashboards or use Explore with CloudWatch metrics and CloudWatch Logs.
 ## Adding the data source
 1. In the side menu under the `Configuration` link, click on `Data Sources`.
-2. Click the `Add data source` button.
+1. Click the `Add data source` button.
-3. Select `Cloudwatch` in the `Cloud` section.
+1. Select `Cloudwatch` in the `Cloud` section.
 > **Note:** If at any moment you have issues with getting this data source to work and Grafana is giving you undescriptive errors then don't
 > forget to check your log file (try looking in /var/log/grafana/grafana.log).

--- a/docs/sources/features/datasources/elasticsearch.md
+++ b/docs/sources/features/datasources/elasticsearch.md
@@ -18,9 +18,9 @@ visualize logs or metrics stored in Elasticsearch. You can also annotate your gr
 ## Adding the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
+1. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select *Elasticsearch* from the *Type* dropdown.
+1. Select *Elasticsearch* from the *Type* dropdown.
 > **Note:** If you're not seeing the `Data Sources` link in your side menu it means that your current user does not have the `Admin` role for the current organization.

--- a/docs/sources/features/datasources/influxdb.md
+++ b/docs/sources/features/datasources/influxdb.md
@@ -17,10 +17,10 @@ Grafana ships with a feature-rich data source plugin for InfluxDB. The plugin in
 ## Add the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
+1. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select *InfluxDB* from the *Type* dropdown.
+1. Select *InfluxDB* from the *Type* dropdown.
-5. Select *InfluxQL* or *Flux* from the `Query Language` list.
+1. Select *InfluxQL* or *Flux* from the `Query Language` list.
 > **Note:** If you're not seeing the `Data Sources` link in your side menu it means that your current user does not have the `Admin` role for the current organization.

--- a/docs/sources/features/datasources/mssql.md
+++ b/docs/sources/features/datasources/mssql.md
@@ -18,9 +18,9 @@ Grafana ships with a built-in Microsoft SQL Server (MSSQL) data source plugin th
 ## Adding the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Configuration` link you should find a link named `Data Sources`.
+1. In the side menu under the `Configuration` link you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select *Microsoft SQL Server* from the *Type* dropdown.
+1. Select *Microsoft SQL Server* from the *Type* dropdown.
 ### Data source options
@@ -84,10 +84,10 @@ You will find the MSSQL query editor in the metrics tab in Graph, Singlestat or 
 panel title, then edit. The editor allows you to define a SQL query to select data to be visualized.
 1. Select *Format as* `Time series` (for use in Graph or Singlestat panel's among others) or `Table` (for use in Table panel among others).
-2. This is the actual editor where you write your SQL queries.
+1. This is the actual editor where you write your SQL queries.
-3. Show help section for MSSQL below the query editor.
+1. Show help section for MSSQL below the query editor.
-4. Show actual executed SQL query. Will be available first after a successful query has been executed.
+1. Show actual executed SQL query. Will be available first after a successful query has been executed.
-5. Add an additional query where an additional query editor will be displayed.
+1. Add an additional query where an additional query editor will be displayed.
 <div class="clearfix"></div>

--- a/docs/sources/features/datasources/mysql.md
+++ b/docs/sources/features/datasources/mysql.md
@@ -21,9 +21,9 @@ data from a MySQL compatible database.
 ## Adding the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
+1. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select *MySQL* from the *Type* dropdown.
+1. Select *MySQL* from the *Type* dropdown.
 ### Data source options

--- a/docs/sources/features/datasources/opentsdb.md
+++ b/docs/sources/features/datasources/opentsdb.md
@@ -17,9 +17,9 @@ Grafana ships with advanced support for OpenTSDB.
 ## Adding the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
+1. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select *OpenTSDB* from the *Type* dropdown.
+1. Select *OpenTSDB* from the *Type* dropdown.
 > **Note:** If you're not seeing the `Data Sources` link in your side menu it means that your current user does not have the `Admin` role for the current organization.

--- a/docs/sources/features/datasources/postgres.md
+++ b/docs/sources/features/datasources/postgres.md
@@ -16,9 +16,9 @@ Grafana ships with a built-in PostgreSQL data source plugin that allows you to q
 ## Adding the data source
 1. Open the side menu by clicking the Grafana icon in the top header.
-2. In the side menu under the `Configuration` icon you should find a link named `Data Sources`.
+1. In the side menu under the `Configuration` icon you should find a link named `Data Sources`.
-3. Click the `+ Add data source` button in the top header.
+1. Click the `+ Add data source` button in the top header.
-4. Select *PostgreSQL* from the *Type* dropdown.
+1. Select *PostgreSQL* from the *Type* dropdown.
 ### Data source options

--- a/docs/sources/features/datasources/testdata.md
+++ b/docs/sources/features/datasources/testdata.md
@@ -20,9 +20,9 @@ This makes it much easier to verify functionality since the data can be shared v
 The `TestData DB` data source is not enabled by default. To enable it: 
 1. In the **Configuration** menu (small gear on the left side of the screen), click **Data Sources**. 
-2. Click **Add Data Source**.
+1. Click **Add Data Source**.
-3. Search and click `TestData DB`.
+1. Search and click `TestData DB`.
-4. Click **Save & Test** to enable it.
+1. Click **Save & Test** to enable it.
 ## Create mock data.

--- a/docs/sources/guides/whats-new-in-v2.md
+++ b/docs/sources/guides/whats-new-in-v2.md
@@ -94,11 +94,11 @@ The top header has gotten a major streamlining in Grafana V2.0.
 <img class="no-shadow" src="/img/docs/v2/v2_top_nav_annotated.png">
 1. `Side menubar toggle` Toggle the side menubar on or off. This allows you to focus on the data presented on the Dashboard. The side menubar provides access to features unrelated to a Dashboard such as Users, Organizations, and Data Sources.
-2. `Dashboard dropdown` The main dropdown shows you which Dashboard you are currently viewing, and allows you to easily switch to a new Dashboard. From here you can also create a new Dashboard, Import existing Dashboards, and manage the Playlist.
+1. `Dashboard dropdown` The main dropdown shows you which Dashboard you are currently viewing, and allows you to easily switch to a new Dashboard. From here you can also create a new Dashboard, Import existing Dashboards, and manage the Playlist.
-3. `Star Dashboard`: Star (or un-star) the current Dashboard. Starred Dashboards will show up on your own Home Dashboard by default, and are a convenient way to mark Dashboards that you're interested in.
+1. `Star Dashboard`: Star (or un-star) the current Dashboard. Starred Dashboards will show up on your own Home Dashboard by default, and are a convenient way to mark Dashboards that you're interested in.
-4. `Share Dashboard`: Share the current dashboard by creating a link or create a static Snapshot of it. Make sure the Dashboard is saved before sharing.
+1. `Share Dashboard`: Share the current dashboard by creating a link or create a static Snapshot of it. Make sure the Dashboard is saved before sharing.
-5. `Save dashboard`: Save the current Dashboard with the current name.
+1. `Save dashboard`: Save the current Dashboard with the current name.
-6. `Settings`: Manage Dashboard settings and features such as Templating, Annotations and the name.
+1. `Settings`: Manage Dashboard settings and features such as Templating, Annotations and the name.
 > **Note:** In Grafana v2.0 when you change the title of a dashboard and then save it, it will no
 > longer create a new Dashboard. It will just change the name for the current Dashboard.

--- a/docs/sources/guides/whats-new-in-v5-3.md
+++ b/docs/sources/guides/whats-new-in-v5-3.md
@@ -48,8 +48,8 @@ Please read [Using Google Stackdriver in Grafana]({{< relref "../features/dataso
 We've improved the TV and kiosk mode to make it easier to use. There's now an icon in the top bar that will let you cycle through the different view modes.
 1. In the first view mode, the sidebar and most of the buttons in the top bar will be hidden.
-2. In the second view mode, the top bar is completely hidden so that only the dashboard itself is shown.
+1. In the second view mode, the top bar is completely hidden so that only the dashboard itself is shown.
-3. Hit the escape key to go back to the default view mode.
+1. Hit the escape key to go back to the default view mode.
 When switching view modes, the URL will be updated to reflect the view mode selected. This allows a dashboard to be opened with a
 certain view mode enabled. Additionally, this also enables [playlists](/dashboards/playlist) to be started with a certain view mode enabled.

--- a/docs/sources/guides/whats-new-in-v5-4.md
+++ b/docs/sources/guides/whats-new-in-v5-4.md
@@ -75,7 +75,7 @@ automatically be rendered for that data point. This should make it easier to und
 Grafana v5.4 adds support for customizing home dashboard, timezone and theme for teams, in addition to the existing customization on Organization and user Profile level.
 1. Specifying a preference on User Profile level will override preference on Team and/or Organization level
-2. Specifying a preference on Team level will override preference on Organization level.
+1. Specifying a preference on Team level will override preference on Organization level.
 ## Changelog

--- a/docs/sources/http_api/create-api-tokens-for-org.md
+++ b/docs/sources/http_api/create-api-tokens-for-org.md
@@ -29,17 +29,17 @@ The task is to create a new organization and then add a Token that can be used b
    This should return a response: `{"message":"Organization created","orgId":6}`. Use the orgId for the next steps.
-2. Optional step. If the org was created previously and/or step 3 fails then first [add your Admin user to the org](http://docs.grafana.org/http_api/org/#add-user-in-organization):
+1. Optional step. If the org was created previously and/or step 3 fails then first [add your Admin user to the org](http://docs.grafana.org/http_api/org/#add-user-in-organization):
    ```bash
    curl -X POST -H "Content-Type: application/json" -d '{"loginOrEmail":"admin", "role": "Admin"}' http://admin:admin@localhost:3000/api/orgs/<org id of new org>/users
    ```
-3. [Switch the org context for the Admin user to the new org](http://docs.grafana.org/http_api/user/#switch-user-context-for-signed-in-user):
+1. [Switch the org context for the Admin user to the new org](http://docs.grafana.org/http_api/user/#switch-user-context-for-signed-in-user):
    ```bash
    curl -X POST http://admin:admin@localhost:3000/api/user/using/<id of new org>
    ```
-4. [Create the API token](http://docs.grafana.org/http_api/auth/#create-api-key):
+1. [Create the API token](http://docs.grafana.org/http_api/auth/#create-api-key):
    ```bash
    curl -X POST -H "Content-Type: application/json" -d '{"name":"apikeycurl", "role": "Admin"}' http://admin:admin@localhost:3000/api/auth/keys
    ```

--- a/docs/sources/installation/rpm.md
+++ b/docs/sources/installation/rpm.md
@@ -87,11 +87,11 @@ If you install manually with YUM, then you will need to manually update Grafana 
 1. On the [Grafana download page](https://grafana.com/grafana/download), select the Grafana version you want to install. 
   * The most recent Grafana version is selected by default.
   * The **Version** field displays only finished releases. If you want to install a beta version, click **Nightly Builds** and then select a version.
-2. Select an **Edition**.
+1. Select an **Edition**.
   * **Enterprise** - Recommended download. Functionally identical to the open source version, but includes features you can unlock with a license if you so choose.
   * **Open Source** - Functionally identical to the Enterprise version, but you will need to download the Enterprise version if you want enterprise features.
-3. Depending on which system you are running, click **Linux** or **ARM**.
+1. Depending on which system you are running, click **Linux** or **ARM**.
-4. Copy and paste the code from the installation page into your command line and run. It follows the pattern shown below.
+1. Copy and paste the code from the installation page into your command line and run. It follows the pattern shown below.
 ```bash
 wget <rpm package url>
@@ -112,11 +112,11 @@ If you install with RPM, then you will need to manually update Grafana for each 
 1. On the [Grafana download page](https://grafana.com/grafana/download), select the Grafana version you want to install. 
   * The most recent Grafana version is selected by default.
   * The **Version** field displays only finished releases. If you want to install a beta version, click **Nightly Builds** and then select a version.
-2. Select an **Edition**.
+1. Select an **Edition**.
   * **Enterprise** - Recommended download. Functionally identical to the open source version, but includes features you can unlock with a license if you so choose.
   * **Open Source** - Functionally identical to the Enterprise version, but you will need to download the Enterprise version if you want Enterprise features.
-3. Depending on which system you are running, click **Linux** or **ARM**.
+1. Depending on which system you are running, click **Linux** or **ARM**.
-4. Copy and paste the .rpm package URL and the local .rpm package information from the installation page into the pattern shown below, then run the commands.
+1. Copy and paste the .rpm package URL and the local .rpm package information from the installation page into the pattern shown below, then run the commands.
 **On CentOS, Fedora, Red Hat, or RHEL:**

--- a/docs/sources/linking/dashboard-links.md
+++ b/docs/sources/linking/dashboard-links.md
@@ -40,9 +40,9 @@ Add links to other dashboards at the top of your current dashboard.
 Add a link to a URL at the top of your current dashboard. You can link to any available URL, including dashboards, panels, or external sites. You can even control the time range to ensure the user is zoomed in on the right data in Grafana.
 1. While viewing the dashboard you want to link, click the gear at the top of the screen to open **Dashboard settings**.
-2. Click **Links** and then click **Add Dashboard Link** or **New**.
+1. Click **Links** and then click **Add Dashboard Link** or **New**.
-3. In **Type**, select **link**.
+1. In **Type**, select **link**.
-4. Select link options:
+1. Select link options:
   - **Url** – Enter the URL you want to link to. Depending on the target, you might want to include field values. **Example:** https://github.com/grafana/grafana/issues/new?title=Dashboard%3A%20HTTP%20Requests
   - **Title** – Enter the title you want the link to display.
   - **Tooltip** – Enter the tooltip you want the link to display when the user hovers their mouse over it.
@@ -53,7 +53,7 @@ Add a link to a URL at the top of your current dashboard. You can link to any av
     - `time` and `time.window` - Define a time range from `time-time.window/2` to `time+time.window/2`. Both params should be specified in ms. For example `?time=1500000000000&time.window=10000` will result in 10s time range from 1499999995000 to 1500000005000.
   - **Variable values** – Select this option to include template variables currently used as query parameters in the link. When the user clicks the link, any matching templates in the linked dashboard are set to the values from the link. **Example:** https://play.grafana.org/d/000000074/alerting?var-app=backend&var-server=backend_01&var-server=backend_03&var-interval=1h
   - **Open in new tab** – Select this option if you want the dashboard link to open in a new tab or window.
-5. Click **Add**.
+1. Click **Add**.
 ## Update a dashboard link

--- a/docs/sources/plugins/installation.md
+++ b/docs/sources/plugins/installation.md
@@ -12,7 +12,7 @@ weight = 1
 Grafana supports data source, panel, and app plugins. Having panels as plugins makes it easy to create and add any kind of panel, to show your data, or improve your favorite dashboards. Apps enable the bundling of data sources, panels, dashboards, and Grafana pages into a cohesive experience.
 1. In a web browser, navigate to the official [Grafana Plugins page](https://grafana.com/plugins) and find a plugin that you want to install.
-2. Click the plugin, and then click the **Installation** tab.
+1. Click the plugin, and then click the **Installation** tab.
 ## Install plugin on Grafana Cloud

--- a/docs/sources/reference/dashboard.md
+++ b/docs/sources/reference/dashboard.md
@@ -15,8 +15,8 @@ A dashboard in Grafana is represented by a JSON object, which stores metadata of
 To view the JSON of a dashboard, follow the steps mentioned below:
  1. Go to a dashboard
-  2. Click on `Manage dashboard` menu on the top navigation bar
+  1. Click on `Manage dashboard` menu on the top navigation bar
-  3. Select `View JSON` from the dropdown menu
+  1. Select `View JSON` from the dropdown menu
 ## JSON fields