address doc comments

Author: izeigerman

docs/guides/configuration.md

@@ -538,11 +538,11 @@ sqlmesh_md5__d3b07384d113edec49eaa6238ad5ff00__dev
 
 This has a downside that now it's much more difficult to determine which table corresponds to which model by just looking at the database with a SQL client. However, the table names have a predictable length so there are no longer any surprises with identfiers exceeding the max length at the physical layer.
 
-#### Virtual Data Environment modes
+#### Virtual Data Environment Modes
 
 By default, Virtual Data Environments (VDE) are applied across both development and production environments. This allows SQLMesh to reuse physical tables when appropriate, even when promoting from development to production.
 
-However, users may sometimes prefer their production environment to be non-virtual. The non-exhaustive list of reasons may include:
+However, users may prefer their production environment to be non-virtual. The non-exhaustive list of reasons may include:
 
 - Integration with third-party tools and platforms, such as data catalogs, may not work well with the virtual view layer that SQLMesh imposes by default
 - A desire to rely on time travel features provided by cloud data warehouses such as BigQuery, Snowflake, and Databricks
@@ -565,15 +565,15 @@ To mitigate this, SQLMesh offers an alternative 'dev-only' mode for using VDE. I
     )
     ```
 
-As the name suggests, 'dev-only' mode means that VDE is applied only in development environments, while in production, model tables and views are updated directly, bypassing the virtual layer. This also means that physical tables in production will be created using the original, unversioned model names. Users will still benefit from VDE and data reuse across development environments.
+'dev-only' mode means that VDE is applied only in development environments. While in production, model tables and views are updated directly and bypass the virtual layer. This also means that physical tables in production will be created using the original, **unversioned** model names. Users will still benefit from VDE and data reuse across development environments.
 
 Please note the following tradeoffs when enabling this mode:
 
 - All data inserted in development environments is used only for [preview](../concepts/plans.md#data-preview-for-forward-only-changes) and will **not** be reused in production
 - Reverting a model to a previous version will be applied going forward and may require an explicit data restatement
 
 !!! warning
-    Switching the mode for an existing project will result in a complete rebuild of all models in the project. Refer to the [Table Migration Guide](./table_migration.md) to migrate existing tables without rebuilding them from scratch.
+    Switching the mode for an existing project will result in a **complete rebuild** of all models in the project. Refer to the [Table Migration Guide](./table_migration.md) to migrate existing tables without rebuilding them from scratch.
 
 
 #### Environment view catalogs