From c6d18a279f51915dfc2a4bd9a19332a04162a31e Mon Sep 17 00:00:00 2001
From: Larissa Wandzura <larissa.wandzura@grafana.com>
Date: Mon, 12 Jan 2026 15:04:18 -0600
Subject: [PATCH] ran prettier

---
 docs/sources/datasources/mysql/_index.md      |  2 +-
 .../datasources/mysql/annotations/index.md    | 20 +++++++++----------
 .../datasources/mysql/query-editor/_index.md  |  1 -
 3 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/docs/sources/datasources/mysql/_index.md b/docs/sources/datasources/mysql/_index.md
index 27496d42335..ada1d3bce67 100644
--- a/docs/sources/datasources/mysql/_index.md
+++ b/docs/sources/datasources/mysql/_index.md
@@ -152,7 +152,7 @@ To use these dashboards:
 For more MySQL dashboards, browse the [Grafana dashboard catalog](https://grafana.com/grafana/dashboards/?search=mysql).
 
 {{< admonition type="note" >}}
-The MySQL integration monitors your MySQL *server* using Prometheus metrics. The MySQL *data source* documented here queries data stored *in* MySQL tables. These are complementary features for different use cases.
+The MySQL integration monitors your MySQL _server_ using Prometheus metrics. The MySQL _data source_ documented here queries data stored _in_ MySQL tables. These are complementary features for different use cases.
 {{< /admonition >}}
 
 ## Related data sources
diff --git a/docs/sources/datasources/mysql/annotations/index.md b/docs/sources/datasources/mysql/annotations/index.md
index 852cb344ad0..cf0683a9bde 100644
--- a/docs/sources/datasources/mysql/annotations/index.md
+++ b/docs/sources/datasources/mysql/annotations/index.md
@@ -52,12 +52,12 @@ To add a MySQL annotation to your dashboard:
 
 Your annotation query must return a `time` column and can optionally include `timeend`, `text`, and `tags` columns.
 
-| Column    | Required | Description                                                                                              |
-| --------- | -------- | -------------------------------------------------------------------------------------------------------- |
-| `time`    | Yes      | The timestamp for the annotation. Can be a SQL datetime or UNIX epoch value.                            |
-| `timeend` | No       | The end timestamp for range annotations. Creates a shaded region instead of a vertical line.            |
-| `text`    | No       | The annotation description displayed when you hover over the annotation.                                 |
-| `tags`    | No       | Tags for the annotation as a comma-separated string. Helps categorize and filter annotations.           |
+| Column    | Required | Description                                                                                   |
+| --------- | -------- | --------------------------------------------------------------------------------------------- |
+| `time`    | Yes      | The timestamp for the annotation. Can be a SQL datetime or UNIX epoch value.                  |
+| `timeend` | No       | The end timestamp for range annotations. Creates a shaded region instead of a vertical line.  |
+| `text`    | No       | The annotation description displayed when you hover over the annotation.                      |
+| `tags`    | No       | Tags for the annotation as a comma-separated string. Helps categorize and filter annotations. |
 
 ## Example queries
 
@@ -147,10 +147,10 @@ WHERE $__timeFilter(start_time)
 
 Use these macros in your annotation queries to filter by the dashboard time range:
 
-| Macro                          | Description                                                                      |
-| ------------------------------ | -------------------------------------------------------------------------------- |
-| `$__timeFilter(column)`        | Filters by time range using a native SQL datetime column.                        |
-| `$__unixEpochFilter(column)`   | Filters by time range using a column with UNIX epoch timestamps.                 |
+| Macro                        | Description                                                      |
+| ---------------------------- | ---------------------------------------------------------------- |
+| `$__timeFilter(column)`      | Filters by time range using a native SQL datetime column.        |
+| `$__unixEpochFilter(column)` | Filters by time range using a column with UNIX epoch timestamps. |
 
 ## Best practices
 
diff --git a/docs/sources/datasources/mysql/query-editor/_index.md b/docs/sources/datasources/mysql/query-editor/_index.md
index 459e03d261d..46601dabc46 100644
--- a/docs/sources/datasources/mysql/query-editor/_index.md
+++ b/docs/sources/datasources/mysql/query-editor/_index.md
@@ -337,4 +337,3 @@ For detailed information on creating annotations with MySQL, refer to [MySQL ann
 You can use time series queries to create Grafana-managed alert rules. Table formatted queries are not supported in alert rule conditions.
 
 For detailed information on creating alerts with MySQL, refer to [MySQL alerting](ref:mysql-alerting).
-