PackageJson: Prettify markdown/mdx on commit with lint-staged (#37616)

* Format md,mdx files with prettier on lint-staged

* Manually run prettier on docs/sources

docs/sources/panels/transformations/_index.md

@@ -10,7 +10,7 @@ Transformations process the result set of a query before it’s passed on for vi
 The transformations feature is accessible from the **Transform** tab of the Grafana panel editor.
 
 Transformations sometimes result in data that cannot be graphed. When that happens, click the `Table view` toggle above the visualization to switch to a table view of the data. This can help you understand
-the final result of your transformations. 
+the final result of your transformations.
 
 ## Order of transformations
 
@@ -24,7 +24,7 @@ Before you can configure and apply transformations:
 
 - You must have entered a query that return data. For more information on queries, refer to [Queries]({{< relref "../queries.md" >}}).
 
-## List of transformations 
+## List of transformations
 
 - [Add field from calculation]({{< relref "./types-options.md#add-field-from-calculation" >}})
 - [Concatenate fields]({{< relref "./types-options.md#concatenate-fields" >}})
@@ -41,4 +41,4 @@ Before you can configure and apply transformations:
 - [Rename by regex]({{< relref "./types-options.md#rename-by-regex" >}})
 - [Rows to fields]({{< relref "./rows-to-fields" >}})
 - [Series to rows]({{< relref "./types-options.md#series-to-rows" >}})
-- [Sort by]({{< relref "./types-options.md#sort-by" >}})
+- [Sort by]({{< relref "./types-options.md#sort-by" >}})

docs/sources/panels/transformations/apply-transformations.md

@@ -3,10 +3,9 @@ title = "Apply a transformation"
 weight = 1
 +++
 
-
 # Apply transformations
 
-You can apply transformations from the Transform tab of the Grafana panel editor, which is located next to the Queries tab. See also, [Debug  transformations](#debug-transformations).
+You can apply transformations from the Transform tab of the Grafana panel editor, which is located next to the Queries tab. See also, [Debug transformations](#debug-transformations).
 
 To apply a transformation:
 

docs/sources/panels/transformations/config-from-query.md

@@ -5,7 +5,7 @@ weight = 300
 
 # Config from query results transform
 
-> **Note:** This is a new beta transformation introduced in v8.1. 
+> **Note:** This is a new beta transformation introduced in v8.1.
 
 This transformation allow you select one query and from it extract [standard options]({{< relref "../standard-options.md" >}}) like **Min**, **Max**, **Unit** and **Thresholds** and apply it to other query results. This enables dynamic query driven visualization configuration.
 
@@ -19,7 +19,7 @@ If you want to extract a unique config for every row in the config query result
 
 ### Field mapping table
 
-This transformation includes a field table which lists all fields in the data returned by the config query. This table gives you control over what field should be mapped to each config property (the *Use as** option). You can also choose which value to select if there are multiple rows in the returned data. 
+This transformation includes a field table which lists all fields in the data returned by the config query. This table gives you control over what field should be mapped to each config property (the \*Use as\*\* option). You can also choose which value to select if there are multiple rows in the returned data.
 
 ## Example
 
@@ -48,7 +48,7 @@ As you can see each row in the source data becomes a separate field. Each field
 
 ## Value mappings
 
-You can also transform a query result into value mappings. This is is a bit different as here every row in the config query result will be used to define a single value mapping row. See example below. 
+You can also transform a query result into value mappings. This is is a bit different as here every row in the config query result will be used to define a single value mapping row. See example below.
 
 Config query result:
 
@@ -66,4 +66,4 @@ In the field mapping specify:
 | Text  | Value mappings / Text   | All values |
 | Color | Value mappings / Ciolor | All values |
 
-Grafana will build the value mappings from you query result and apply it the the real data query results. You should see values being mapped and colored according to the config query results.
+Grafana will build the value mappings from you query result and apply it the the real data query results. You should see values being mapped and colored according to the config query results.

docs/sources/panels/transformations/rows-to-fields.md

@@ -5,9 +5,9 @@ weight = 300
 
 # Rows to fields transform
 
-> **Note:** This is a new beta transformation introduced in v8.1. 
+> **Note:** This is a new beta transformation introduced in v8.1.
 
-This transforms rows into separate fields. This can be useful as fields can be styled and configured individually, something rows cannot. It can also use additional fields as sources for dynamic field  configuration or map them to field labels. The additional labels can then be used to define better display names for the resulting fields.
+This transforms rows into separate fields. This can be useful as fields can be styled and configured individually, something rows cannot. It can also use additional fields as sources for dynamic field configuration or map them to field labels. The additional labels can then be used to define better display names for the resulting fields.
 
 Useful when visualizing data in:
 
@@ -69,4 +69,4 @@ Output:
 | -------------------------------- | -------------------------------- |
 | 10                               | 20                               |
 
-The extra labels can now be used in the field display name provide more complete field names. 
+The extra labels can now be used in the field display name provide more complete field names.