Hot fixes

Author: Mayra Pena

docs/how-tos/airflow/initial-setup.md

@@ -25,9 +25,12 @@ Once you enabled Airflow, click on the `Services configuration > Airflow Setting
   ![Airflow Settings](./assets/environments_airflow_config.gif)
 
 ### DAGs Sync Configuration
-There are **2 options** to choose from for your DAGs sync - **Git Sync** and **S3 Sync**. Each requires specific information to be provided during configuration. Our recommended default is Git Sync.
+
+There are **2 options** to choose from for your DAGs sync: **Git Sync** and **S3 Sync**. 
+Each requires specific information to be provided during configuration. Our recommended default is Git Sync.
 
 **Git Sync**
+
 - **Provider** Select `Git`
 - **Git branch name** The branch airflow will monitor for changes. If you have more than 1 environment (Development and Production), we suggest `airflow_development` for the development environment and `main` for the production environment. Note: You would need to create an  `airflow_development` branch in your repo. If only have 1 environment, then the `Git branch name` should be `main`. 
 

docs/how-tos/airflow/run-fivetran-sync-jobs.md

@@ -98,16 +98,20 @@ dag = daily_loan_run()
 ```
 
 ### Fields reference
+
 - **extract_and_load_fivetran**: The name of the task group. This can be named whatever you like and will show up in airflow.
 ![Extract and Load DAG](assets/extract_load_airflow_dag.png)
 - **tooltip**: The tooltip argument allows you to provide explanatory text or helpful hints about specific elements in the Airflow UI
 - **tasks**: Define all of your tasks within the task group.
 
 You will need to define two operators: `fivetran_provider.operators.fivetran.FivetranOperator` and `fivetran_provider.sensors.fivetran.FivetranSensor`
+
 - **example_task_trigger**: Name your trigger task accordingly and define arguments below.
   - **operator**: `fivetran_provider.operators.fivetran.FivetranOperator`
   - **connector_id**: Find in Fivetran UI. Select your desired source. Click into `Setup` and locate the `Fivetran Connector ID`
+
   ![Fivetran Connection ID](assets/fivetran_connector_id.png)
+
   - **do_xcom_push**:  Indicate that the output of the task should be sent to XCom, making it available for other tasks to use.
   - **fivetran_conn_id**: This is the `connection_id` that was configured above in the Fivetran UI as seen [above](#id=fivetran-connection).
 - **example_task_sensor**: Name your Sensor task accordingly and define arguments below.

docs/how-tos/dbt/advenced-dbt-debug.md

@@ -79,6 +79,7 @@ export DBT_MACRO_DEBUGGING=1
 ```
 
 When the `debug()` macro is hit:
+
 1. Execution pauses
 2. Debugger opens
 3. You can inspect variables and other state

docs/how-tos/vscode/datacoves-copilot/llm-config.md

@@ -1,5 +1,7 @@
 # Configure your LLM in Datacoves
 
+>[!NOTE] We currently only support the 4o model gpt model.
+
 ### Step 1: Create a Datacoves Secret
 
 Creating a [Datacoves Secret](/how-tos/datacoves/how_to_secrets.md) requires some key fields to be filled out: 
@@ -8,9 +10,6 @@ Creating a [Datacoves Secret](/how-tos/datacoves/how_to_secrets.md) requires som
 - **Description:** Provide a simple description such as: `Open AI config`
 - **Format:** Select `Raw JSON`  
 - **Value**: The value will vary based on the LLM you are utilizing.
-
->[!NOTE] We currently only support the 4o model gpt model.
-
   - **Open AI:** You only need your API key. Head to [Open AI](https://platform.openai.com/api-keys) to create your key. 
     ```json
     {
@@ -25,7 +24,6 @@ Creating a [Datacoves Secret](/how-tos/datacoves/how_to_secrets.md) requires som
           "AZURE_OPENAI_API_KEY"  : "Your key here"
       }
     ```
-
 - **Scope:** Select the desired scope, either `Project` or `Environment`. 
 - **Project/Environment:** Select the `Project` or `Environment` that will access this LLM.
 

docs/reference/admin-menu/integrations.md

@@ -5,6 +5,7 @@
 Integrations are used to configure external services such as Email, MS Teams and Slack notifications
 
 For more information see:
+
 - SMTP: used to [send email notifications from Airflow](/how-tos/airflow/send-emails.md)
 - MS Teams: used to [send Microsoft Teams messages from Airflow](/how-tos/airflow/send-ms-teams-notifications.md)
 - Slack: used to [send Slack messages from Airflow](/how-tos/airflow/send-slack-notifications.md)

docs/reference/admin-menu/secrets.md

@@ -5,6 +5,7 @@
 Secrets are used to manage confidential information that are used by tools running in VSCode, or services like Airflow.
 
 Some uses could be:
+
 - Storing Airbyte connections credentials using `dbt-coves extract` and `dbt-coves load` commands.
 - Storing Airflow connections or variables used by Airflow DAGs