Docs: Minor edits to the README and several md files (#19238)

* Update README.md Capitalized the G and S in "Getting Started," and moved "guide" to match the section title in the docs. * Fixed sentence structure. Changed "download" to "grafana.com/get" and changed "get" to "download". * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111) * Docs: Replace "datasources" with "data sources" (#19111)
2019-09-20 00:04:56 +02:00
parent b20a258b72
commit c9e566b156
62 changed files with 302 additions and 302 deletions
@@ -79,7 +79,7 @@ Each field in the dashboard JSON is explained below with its usage:

 ## Panels

-Panels are the building blocks of a dashboard. It consists of datasource queries, type of graphs, aliases, etc. Panel JSON consists of an array of JSON objects, each representing a different panel. Most of the fields are common for all panels but some fields depend on the panel type. Following is an example of panel JSON of a text panel.
+Panels are the building blocks of a dashboard. It consists of data source queries, type of graphs, aliases, etc. Panel JSON consists of an array of JSON objects, each representing a different panel. Most of the fields are common for all panels but some fields depend on the panel type. Following is an example of panel JSON of a text panel.

 ```json
 "panels": [
@@ -239,15 +239,15 @@ Usage of the above mentioned fields in the templating section is explained below
 | ---- | ----- |
 | **enable** | whether templating is enabled or not |
 | **list** | an array of objects each representing one template variable |
-| **allFormat** | format to use while fetching all values from datasource, eg: `wildcard`, `glob`, `regex`, `pipe`, etc. |
+| **allFormat** | format to use while fetching all values from data source, eg: `wildcard`, `glob`, `regex`, `pipe`, etc. |
 | **current** | shows current selected variable text/value on the dashboard |
-| **datasource** | shows datasource for the variables |
+| **data source** | shows data source for the variables |
 | **includeAll** | whether all value option is available or not |
 | **multi** | whether multiple values can be selected or not from variable value list |
-| **multiFormat** | format to use while fetching timeseries from datasource |
+| **multiFormat** | format to use while fetching timeseries from data source |
 | **name** | name of variable |
 | **options** | array of variable text/value pairs available for selection on dashboard |
-| **query** | datasource query used to fetch values for a variable |
+| **query** | data source query used to fetch values for a variable |
 | **refresh** | TODO |
 | **regex** | TODO |
 | **type** | type of variable, i.e. `custom`, `query` or `interval` |
@@ -100,7 +100,7 @@ These are then referenced in the dashboard panels like this:

 These inputs and their usage in data source properties are automatically added during export in Grafana 3.1.
 If you run an older version of Grafana and want to share a dashboard on Grafana.com you need to manually
-add the inputs and templatize the datasource properties like above.
+add the inputs and templatize the data source properties like above.

 If you want to import a dashboard from Grafana.com into an older version of Grafana then you can either import
 it as usual and then update the data source option in the metrics tab so that the panel is using the correct
@@ -38,7 +38,7 @@ documentation article for details on value escaping during interpolation.

 ### Advanced Formatting Options

-The formatting of the variable interpolation depends on the data source but there are some situations where you might want to change the default formatting. For example, the default for the MySql datasource is to join multiple values as comma-separated with quotes: `'server01','server02'`. In some cases you might want to have a comma-separated string without quotes: `server01,server02`. This is now possible with the advanced formatting options.
+The formatting of the variable interpolation depends on the data source but there are some situations where you might want to change the default formatting. For example, the default for the MySql data source is to join multiple values as comma-separated with quotes: `'server01','server02'`. In some cases you might want to have a comma-separated string without quotes: `server01,server02`. This is now possible with the advanced formatting options.

 Syntax: `${var_name:option}`

@@ -147,7 +147,7 @@ Type | Description
 ------- | --------
 *Query* | This variable type allows you to write a data source query that usually returns a list of metric names, tag values or keys. For example, a query that returns a list of server names, sensor ids or data centers.
 *Interval* | This variable can represent time spans. Instead of hard-coding a group by time or date histogram interval, use a variable of this type.
-*Datasource* | This type allows you to quickly change the data source for an entire Dashboard. Useful if you have multiple instances of a data source in for example different environments.
+*Data source* | This type allows you to quickly change the data source for an entire Dashboard. Useful if you have multiple instances of a data source in for example different environments.
 *Custom* | Define the variable options manually using a comma separated list.
 *Constant* | Define a hidden constant. Useful for metric path prefixes for dashboards you want to share. During dashboard export, constant variables will be made into an import option.
 *Ad hoc filters* | Very special kind of variable that only works with some data sources, InfluxDB & Elasticsearch currently. It allows you to add key/value filters that will automatically be added to all metric queries that use the specified data source.