Tiny edits

Author: igorlukanin

docs/pages/product/configuration/data-sources/mysql.mdx

@@ -38,6 +38,7 @@ CUBEJS_DB_PASS=**********
 | `CUBEJS_DB_SSL`         | If `true`, enables SSL encryption for database connections from Cube                | `true`, `false`           |    ❌    |
 | `CUBEJS_CONCURRENCY`    | The number of concurrent connections each queue has to the database. Default is `2` | A valid number            |    ❌    |
 | `CUBEJS_DB_MAX_POOL`    | The maximum number of concurrent database connections to pool. Default is `8`       | A valid number            |    ❌    |
+| `CUBEJS_DB_MYSQL_USE_NAMED_TIMEZONES` | The flag to use time zone names or numeric offsets for time zone conversion. Default is `false` | `true`, `false` | ❌ |
 
 ## Pre-Aggregation Feature Support
 

docs/pages/reference/configuration/environment-variables.mdx

@@ -605,13 +605,14 @@ The cluster name to use when connecting to [Materialize](/product/configuration/
 
 ## `CUBEJS_DB_MYSQL_USE_NAMED_TIMEZONES`
 
-This flag controls how timezones are passed to CONVERT_TZ. If it is set to TRUE - timezone names will be used.
-IF it is set to FALSE - numeric offsets will be passed instead. To use named timezones, MySQL Server needs
+This flag controls how time zones conversion is done in the generated SQL for MySQL:
+- If it is set to `true`, time zone names are used. In this case, your MySQL server needs
 to be [configured][mysql-server-tz-support] properly.
+- If it is set to `false`, numeric offsets are used instead.
 
-| Possible Values                       | Default in Development | Default in Production |
-| ------------------------------------- | ---------------------- | --------------------- |
-| Whether to use named timezones or not | `false`                | `false`               |
+| Possible Values | Default in Development | Default in Production |
+| --------------- | ---------------------- | --------------------- |
+| `true`, `false` | `false`                | `false`               |
 
 ## `CUBEJS_DB_SNOWFLAKE_ACCOUNT`