remove multiple h1s

connectors/dashboard/domo-dashboard/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Domo Dashboard | Collate Connector Setup Guide
 description: Connect Domo dashboards to Collate with our comprehensive connector guide. Easy setup, configuration steps, and metadata extraction explained.
 slug: /connectors/dashboard/domo-dashboard
 sidebarTitle: Overview
 ---
@@ -18,16 +18,16 @@
   unavailableFeatures={["Tags", "Datamodels", "Projects", "Lineage"]}
 />
 In this section, we provide guides and references to use the DomoDashboard connector.
 Configure and schedule DomoDashboard metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Troubleshooting](/connectors/dashboard/domo-dashboard/troubleshooting)
 ## Requirements
 For metadata ingestion, make sure to add at least `data` scopes to the clientId provided.
 For questions related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Domo Dashboard"} selectServicePath={"/public/images/connectors/domo-dashboard/select-service.png"} addNewServicePath={"/public/images/connectors/domo-dashboard/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/domo-dashboard/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/lightdash/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Lightdash Connector | Collate Dashboard Integration
 description: Connect Lightdash to Collate with our comprehensive dashboard connector guide. Set up data lineage, metadata extraction, and BI integration easily.
 slug: /connectors/dashboard/lightdash
 sidebarTitle: Overview
 ---
@@ -18,17 +18,17 @@
 availableFeatures={["Dashboards", "Charts", "Owners", "Datamodels", "Lineage"]}
   unavailableFeatures={["Tags", "Projects"]}
 />
 In this section, we provide guides and references to use the Lightdash connector.
 Configure and schedule Lightdash metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
 - [Troubleshooting](/connectors/dashboard/lightdash/troubleshooting)
 ## Requirements
 To integrate Lightdash, ensure you are using OpenMetadata version 1.2.x or higher.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Lightdash"} selectServicePath={"/public/images/connectors/lightdash/select-service.png"} addNewServicePath={"/public/images/connectors/lightdash/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/lightdash/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/looker/index.mdx

@@ -19,7 +19,7 @@
   unavailableFeatures={["Tags", "Projects"]}
 />
 In this section, we provide guides and references to use the Looker connector.
 Configure and schedule Looker metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
@@ -44,7 +44,7 @@
 </Tip>
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Looker"} selectServicePath={"/public/images/connectors/looker/select-service.png"} addNewServicePath={"/public/images/connectors/looker/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/looker/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/metabase/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Metabase Connector | Collate Dashboard Integration
 description: Connect Metabase dashboards to Collate effortlessly. Complete setup guide, configuration steps, and metadata extraction for seamless integration.
 slug: /connectors/dashboard/metabase
 sidebarTitle: Overview
 ---
@@ -17,18 +17,18 @@
   stage="PROD"
 availableFeatures={["Dashboards", "Charts", "Lineage", "Projects"]}
   unavailableFeatures={["Owners", "Tags", "Datamodels"]} />
 In this section, we provide guides and references to use the Metabase connector.
 Configure and schedule Metabase metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
 - [Troubleshooting](/connectors/dashboard/metabase/troubleshooting)
 ## Requirements
 The service account must have view access to all dashboards and charts that need to be ingested. Without view access, the connector cannot retrieve those objects.
 **Note:** We have tested Metabase with Versions `0.42.4` and `0.43.4`.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Metabase"} selectServicePath={"/public/images/connectors/metabase/select-service.png"} addNewServicePath={"/public/images/connectors/metabase/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/metabase/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/microstrategy/index.mdx

@@ -17,14 +17,14 @@
 availableFeatures={["Dashboards", "Charts", "Owners", "Datamodels", "Lineage"]}
   unavailableFeatures={["Tags", "Projects"]} />
 In this section, we provide guides and references to use the MicroStrategy connector.
 Configure and schedule MicroStrategy metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Troubleshooting](/connectors/dashboard/microstrategy/troubleshooting)
 ## Requirements
 To integrate MicroStrategy, ensure you are using OpenMetadata version 1.2.x or higher.
 When a service user is created, it is already provisioned with the necessary permissions.
 However, if the user still cannot access the APIs, the following should be checked as part of the troubleshooting process:
 - Required DSS Privileges for MicroStrategy REST/JSON API:
 - Web Services API: Essential for REST API usage.
 - Login to MicroStrategy: User authentication.
@@ -34,7 +34,7 @@
 - Browse Repository: Object navigation within projects/folders.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"MicroStrategy"} selectServicePath={"/public/images/connectors/microstrategy/select-service.png"} addNewServicePath={"/public/images/connectors/microstrategy/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/microstrategy/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/mode/index.mdx

@@ -18,7 +18,7 @@
 availableFeatures={["Dashboards", "Charts", "Lineage"]}
   unavailableFeatures={["Owners", "Tags", "Datamodels", "Projects"]} />
 In this section, we provide guides and references to use the Mode connector.
 Configure and schedule Mode metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
@@ -27,7 +27,7 @@
 OpenMetadata relies on Mode's API, which is exclusive to members of the Mode Business Workspace. This means that only resources that belong to a Mode Business Workspace can be accessed via the API.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Mode"} selectServicePath={"/public/images/connectors/mode/select-service.png"} addNewServicePath={"/public/images/connectors/mode/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/mode/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/powerbi/index.mdx

@@ -18,7 +18,7 @@
 availableFeatures={["Dashboards", "Charts", "Datamodels", "Projects", "Lineage", "Column Lineage", "Owners"]}
   unavailableFeatures={[]} />
 In this section, we provide guides and references to use the PowerBI connector.
 Configure and schedule PowerBI metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
@@ -36,15 +36,15 @@
 <Tip>
 When configuring Azure Authentication, ensure that "Allow public client flows" is enabled. This setting is required to support authentication for public client applications.
 </Tip>
 ### PowerBI Admin and Non-Admin APIs:
 While configuring the PowerBI ingestion you can choose whether to use the PowerBI Admin APIs to retrieve the metadata or use the PowerBI Non-Admin APIs. Please check below for the the difference in their functionality:
 - Enabled (Use PowerBI Admin APIs)
 Using the admin APIs will fetch the dashboard and chart metadata from all the workspaces available in the PowerBI instance.
 <Tip>
 When using the PowerBI Admin APIs, the table and dataset information used to generate lineage is gathered using the PowerBI [Scan Result](https://learn.microsoft.com/en-us/rest/api/power-bi/admin/workspace-info-get-scan-result) API. This API has no limitations and hence does not restrict getting the necessary data for generating lineage.
 </Tip>
 - Disabled (Use Non-Admin PowerBI APIs)
 Using the non-admin APIs will only fetch the dashboard and chart metadata from the workspaces that have the security group of the service principal assigned to them.
 <Tip>
 When using the PowerBI Non-Admin APIs, the table and dataset information used to generate lineage is gathered using the PowerBI [Get Dataset Tables](https://learn.microsoft.com/en-us/rest/api/power-bi/push-datasets/datasets-get-tables) API. This API only retrieves the table information if the dataset is a [Push Dataset](https://learn.microsoft.com/en-us/rest/api/power-bi/push-datasets).
 Hence the lineage can only be created for push datasets in this case.
@@ -53,18 +53,18 @@
 ### PowerBI Account Setup
 Follow the steps below to configure the account setup for PowerBI connector:
 ### Step 1: Enable API permissions from the PowerBI Admin console
 We extract the information from PowerBI using APIs, this is a manual step a PowerBI Admin needs to do to ensure we can get the right information.
 Login to the [Power BI](https://app.powerbi.com/) as Admin and from `Tenant` settings allow below permissions.
 - Allow service principles to use Power BI APIs
 - Allow service principals to use read-only Power BI admin APIs
 - Enhance admin APIs responses with detailed metadata
 ### Step 2: Create the App in Azure AD
 Please follow the steps mentioned [here](https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-service-principal) for setting up the Azure AD application service principle.
 ### Step 3: Provide necessary API permissions to the Azure AD app
 Go to the `Azure Ad app registrations` page, select your app and add the dashboard permissions to the app for PowerBI service and grant admin consent for the same:
 The required permissions are:
 - `Dashboard.Read.All`
 Optional Permissions: (Without granting these permissions, the dataset information cannot be retrieved and the datamodel and lineage processing will be skipped)
 - `Dataset.Read.All`
 <Warning>
 Make sure that in the API permissions section **Tenant** related permissions are not being given to the app
@@ -76,7 +76,7 @@
 For reference here is a [thread](https://community.powerbi.com/t5/Service/Error-while-executing-Get-dataset-call-quot-API-is-not/m-p/912360#M85711) referring to the same
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"PowerBI"} selectServicePath={"/public/images/connectors/powerbi/select-service.png"} addNewServicePath={"/public/images/connectors/powerbi/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/powerbi/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/powerbireportserver/index.mdx

@@ -27,7 +27,7 @@ Configure and schedule PowerBI Report Server metadata from CLI:
 The PowerBI Report Server should be accessible from the ingestion environment.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"PowerBI Report Server"} selectServicePath={"/public/images/connectors/powerbi-report-server/select-service.png"} addNewServicePath={"/public/images/connectors/powerbi-report-server/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/powerbi-report-server/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/qlikcloud/api_keys.mdx

@@ -1,24 +1,24 @@
 ---
 title: Qlik Cloud
 slug: /connectors/dashboard/qlikcloud/api_keys
 sidebarTitle: API Keys
 ---
 
 # How to generate API Key
 
 OpenMetadata Uses [REST APIs](https://qlik.dev/apis/) to communicate with Qlik Cloud and fetch relevant metadata, and connecting to these APIs require authentication token as described in [these docs](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-generate-api-keys.htm).
 
 
 In this document we will explain how you can generate this token so that OpenMetadata can communicate with Qlik Cloud.
 
 
-# Step 1: Open Qlik Cloud Management Console (QMC)
+## Step 1: Open Qlik Cloud Management Console (QMC)
 
 Open your Qlik Cloud Management Console (QMC) and navigate to API Keys section.
 
 <img src="/public/images/connectors/qlikcloud/qlik-cloud-management-console.png" alt="Navigate to API Keys in QMC" />
 
-# Step 2: Provide Name and Generate API Key
+## Step 2: Provide Name and Generate API Key
 
 1. Provide name for the API key you will generate.
 

connectors/dashboard/qlikcloud/index.mdx

@@ -1,5 +1,5 @@
 ---
 title: Qlik Cloud Connector | Collate Dashboard Integration
 description: Connect QlikCloud dashboards to Collate effortlessly. Complete setup guide, configuration steps, and metadata extraction for seamless data governance.
 slug: /connectors/dashboard/qlikcloud
 sidebarTitle: Overview
@@ -17,8 +17,8 @@
   stage="PROD"
 availableFeatures={["Projects", "Dashboards", "Charts", "Datamodels", "Lineage", "Column Lineage"]}
   unavailableFeatures={["Owners", "Tags"]} />
 In this section, we provide guides and references to use the Qlik Cloud connector.
 Configure and schedule QlikCloud metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
@@ -29,7 +29,7 @@
   </Card>
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"QlikCloud"} selectServicePath={"/public/images/connectors/qlikcloud/select-service.png"} addNewServicePath={"/public/images/connectors/qlikcloud/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/qlikcloud/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/qliksense/certificates.mdx

@@ -1,5 +1,5 @@
 ---
 title: Qlik Sense Certificates | Collate Connector Setup
 description: Configure QlikSense certificate authentication for Collate dashboard connectors. Step-by-step setup guide for secure SSL/TLS connections and data integration.
 slug: /connectors/dashboard/qliksense/certificates
 sidebarTitle: Export Certificates
@@ -7,19 +7,19 @@
 
 # How to generate authentication certificates
 
 OpenMetadata Uses [Qlik Engine APIs](https://help.qlik.com/en-US/sense-developer/May2023/Subsystems/EngineAPI/Content/Sense_EngineAPI/introducing-engine-API.htm) to communicate with Qlik Sense and fetch relevant metadata, and connecting to these APIs require authentication certificates as described in [these docs](https://help.qlik.com/en-US/sense-developer/May2023/Subsystems/EngineAPI/Content/Sense_EngineAPI/GettingStarted/connecting-to-engine-api.htm).
 
 
 In this document we will explain how you can generate these certificates so that OpenMetadata can communicate with Qlik Sense.
 
 
-# Step 1: Open Qlik Management Console (QMC)
+## Step 1: Open Qlik Management Console (QMC)
 
 Open your Qlik Management Console (QMC) and navigate to certificates section.
 
 <img src="/public/images/connectors/qliksense/qlik-certificate-nav.png" alt="Navigate to certificates in QMC" />
 
-# Step 2: Provide Details and Export Certificates
+## Step 2: Provide Details and Export Certificates
 
 1. In the Machine name box, type the full computer name of the computer that you are creating the certificates for: MYMACHINE.mydomain.com or the IP address.
 
@@ -35,7 +35,7 @@
 <img src="/public/images/connectors/qliksense/qlik-export-cert.png" alt="Provide Certificate Details" />
 
 
-# Step 3: Locate the certificates
+## Step 3: Locate the certificates
 
 Once you have exported the certificates you can see the location of exported certificates just below the certificate details page. When you navigate to that location you will find the `root.pem`, `client.pem` & `client_key.pem` certificates which will be used by OpenMetadata.
 

connectors/dashboard/qliksense/index.mdx

@@ -1,5 +1,5 @@
 ---
 title: Qlik Sense Connector | Collate Integration Guide
 description: Connect QlikSense dashboards to Collate with our comprehensive connector guide. Step-by-step setup, configuration, and metadata extraction instructions.
 slug: /connectors/dashboard/qliksense
 sidebarTitle: Overview
@@ -17,8 +17,8 @@
   stage="PROD"
 availableFeatures={["Dashboards", "Charts", "Datamodels", "Lineage", "Column Lineage"]}
   unavailableFeatures={["Owners", "Tags", "Projects"]} />
 In this section, we provide guides and references to use the Qlik Sense connector.
 Configure and schedule Metabase metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Enable Security](#securing-qlik-sense-connection-with-ssl-in-openmetadata)
@@ -30,7 +30,7 @@
   </Card>
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"QlikSense"} selectServicePath={"/public/images/connectors/qliksense/select-service.png"} addNewServicePath={"/public/images/connectors/qliksense/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/qliksense/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>
@@ -76,11 +76,11 @@
 <ConfigureIngestion />
 <IngestionScheduleAndDeploy />
 </Steps>
 ## Securing Qlik Sense Connection with SSL in OpenMetadata
 To establish secure connections between OpenMetadata and Qlik Sense, there are two ways to communicate: defining the certificate file path or using the certificates value. Navigate to the `Advanced Config` section.
 When using the local certificate file path, ensure that the certificates are accessible from the Airflow Server. You can specify the path for the `client certificate`, `client key certificate`, and `root certificate`.
 Alternatively, when using the certificates value, you can provide the CA certificate used for SSL validation by specifying the `CA Certificate`. If both client and server require mutual authentication, you can upload all three: `CA Certificate`, `SSL Certificate`, and `SSL Key`.
 Refer to the guide on how to generate authentication certificates so that OpenMetadata can communicate with Qlik Sense [here](/connectors/dashboard/qliksense/certificates).
 <img src="/public/images/connectors/ssl_qlik_1.png" alt="SSL Configuration by local file path" height="450px" />
   <img src="/public/images/connectors/ssl_qlik_2.png" alt="SSL Configuration" height="450px" />
 <DashboardLineage />

connectors/dashboard/quicksight/index.mdx

@@ -18,7 +18,7 @@
 availableFeatures={["Dashboards", "Charts", "Lineage", "Datamodels"]}
   unavailableFeatures={["Owners", "Tags", "Projects"]} />
 In this section, we provide guides and references to use the QuickSight connector.
 Configure and schedule QuickSight metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
@@ -64,7 +64,7 @@
 ```
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"QuickSight"} selectServicePath={"/public/images/connectors/quicksight/select-service.png"} addNewServicePath={"/public/images/connectors/quicksight/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/quicksight/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/redash/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Redash Connector | Collate Dashboard Integration
 description: Connect Redash dashboards to Collate Easily. Complete setup guide, configuration steps, and integration instructions for seamless data lineage tracking.
 slug: /connectors/dashboard/redash
 sidebarTitle: Overview
 ---
@@ -17,19 +17,19 @@
   stage="PROD"
 availableFeatures={["Dashboards", "Charts", "Lineage", "Owners", "Tags"]}
   unavailableFeatures={["Datamodels", "Projects"]} />
 In this section, we provide guides and references to use the Redash connector.
 Configure and schedule Redash metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
 - [Troubleshooting](/connectors/dashboard/redash/troubleshooting)
 ## Requirements
 We connect to Redash through the [API](https://redash.io/help/user-guide/integrations-and-api/api) endpoint, so the user
 we use in the configuration to ingest data must have enough permissions to view all the data. For more info about the
 permissions, please visit Redash documentation [here](https://redash.io/help/user-guide/users/permissions-groups).
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Redash"} selectServicePath={"/public/images/connectors/redash/select-service.png"} addNewServicePath={"/public/images/connectors/redash/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/redash/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/sigma/index.mdx

@@ -18,7 +18,7 @@
 availableFeatures={["Dashboards", "Charts", "Lineage", "Owners"]}
   unavailableFeatures={["Tags", "Datamodels", "Projects"]} />
 In this section, we provide guides and references to use the Sigma connector.
 Configure and schedule Sigma metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](#lineage)
@@ -27,7 +27,7 @@
 OpenMetadata relies on Sigma's REST API. To know more you can read the [Sigma API Get Started docs](https://help.sigmacomputing.com/reference/get-started-sigma-api#about-the-api). To [generate API client credentials](https://help.sigmacomputing.com/reference/generate-client-credentials#user-requirements), you must be assigned the Admin account type.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Sigma"} selectServicePath={"/public/images/connectors/sigma/select-service.png"} addNewServicePath={"/public/images/connectors/sigma/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/sigma/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/dashboard/superset/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Superset Connector | Collate Dashboard Integration
 description: Learn how to connect Apache Superset dashboards to Collate with our comprehensive connector guide. Setup instructions, configuration, and metadata integration.
 slug: /connectors/dashboard/superset
 sidebarTitle: Overview
 ---
@@ -18,20 +18,20 @@
   stage="PROD"
 availableFeatures={["Dashboards", "Charts", "Lineage", "Owners", "Datamodels", "Column Lineage"]}
   unavailableFeatures={["Tags", "Projects"]} />
 In this section, we provide guides and references to use the Superset connector.
 Configure and schedule Superset metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Enable Security](#securing-superset-connection-with-ssl-in-openmetadata)
 - [Lineage](#lineage)
 - [Troubleshooting](/connectors/dashboard/superset/troubleshooting)
 ## Requirements
 The ingestion also works with Superset 2.0.0 🎉
 **API Connection**: To extract metadata from Superset via API, user must have at least `can read on Chart` & `can read on Dashboard` permissions.
 **Database Connection**: To extract metadata from Superset via MySQL or Postgres database, database user must have at least `SELECT` privilege on `dashboards` & `slices` tables within superset schema.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Superset"} selectServicePath={"/public/images/connectors/superset/select-service.png"} addNewServicePath={"/public/images/connectors/superset/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/superset/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>
@@ -84,11 +84,11 @@
 <ConfigureIngestion />
 <IngestionScheduleAndDeploy />
 </Steps>
 ## Securing Superset Connection with SSL in OpenMetadata
 1. To establish secure connections between OpenMetadata and Superset, navigate to the `Advanced Config` section. We need to update the `Certificate Path` and ensure that the certificates are accessible from the Airflow Server.
   <img src="/public/images/connectors/ssl_superset.png" alt="Supertset API SSL Configuration" height="450px" />
 2. To establish secure connections between OpenMetadata and Superset's MySQL database, you need to configure SSL certificates appropriately. If you only require SSL validation, specify the `caCertificate` to use the CA certificate for validating the server's certificate. For mutual authentication, where both client and server need to authenticate each other, you must provide all three parameters: `ssl_key` for the client’s private key, `ssl_cert` for the client’s SSL certificate, and `ssl_ca` for the CA certificate to validate the server’s certificate.
 <img src="/public/images/connectors/ssl_superset_mysql.png" alt="MySQL SSL Configuration" height="450px" />
 3. To establish secure connections between OpenMetadata and Superset's PostgreSQL database, you can configure SSL using different SSL modes provided by PostgreSQL, each offering varying levels of security.Under `PostgresConnection Advanced Config`, specify the SSL mode appropriate for your connection, such as `prefer`, `verify-ca`, `allow`, and others. After selecting the SSL mode, provide the CA certificate used for SSL validation (`caCertificate`). Note that PostgreSQL requires only the CA certificate for SSL validation.
 <img src="/public/images/connectors/ssl_superset_postgres.png" alt="Postgres SSL Configuration" height="450px" />
 <DashboardLineage />

connectors/dashboard/tableau/index.mdx

@@ -19,7 +19,7 @@
 availableFeatures={["Dashboards", "Charts", "Lineage", "Owners", "Datamodels", "Tags", "Projects", "Column Lineage", "Usage", "Reverse Metadata (Collate Only)"]}
 unavailableFeatures={[]} />
 In this section, we provide guides and references to use the Tableau connector.
 Configure and schedule Tableau metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Entity Mapping](#entity-mapping)
 - [Metadata Ingestion](#metadata-ingestion)
@@ -30,7 +30,7 @@
 ## Requirements
 To ingest tableau metadata, minimum `Site Role: Viewer` is required for the tableau user.
 To create lineage between tableau dashboard and any database service via the queries provided from Tableau Metadata API, please enable the Tableau Metadata API for your tableau server.
 For more information on enabling the Tableau Metadata APIs follow the link [here](https://help.tableau.com/current/api/metadata_api/en-us/docs/meta_api_start.html)
 <Tip>
 - If using a **default site** on Tableau Server, leave the **Site URL** and **Site Name** fields **blank** in the ingestion configuration.
 - Ensure that the **Metadata API** is enabled for the user performing the ingestion. If it is not enabled, ingestion may fail. Follow the official Tableau documentation to [enable the Metadata API](https://help.tableau.com/current/api/metadata_api/en-us/docs/meta_api_start.html#enable-the-tableau-metadata-api-for-tableau-server).
@@ -71,7 +71,7 @@
 - Chrome Extension compatibility is maintained
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Tableau"} selectServicePath={"/public/images/connectors/tableau/select-service.png"} addNewServicePath={"/public/images/connectors/tableau/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/tableau/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/database/cassandra/hybrid-runner.mdx

@@ -26,10 +26,10 @@
 ## Requirements
 To extract metadata using the Cassandra connector, ensure the user in the connection has the following permissions:
 - Read Permissions: The ability to query tables and perform data extraction.
 - Schema Operations: Access to list and describe keyspaces and tables.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Cassandra"} selectServicePath={"/public/images/connectors/cassandra/select-service.png"} addNewServicePath={"/public/images/connectors/cassandra/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/cassandra/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/database/cassandra/index.mdx

@@ -26,10 +26,10 @@
 ## Requirements
 To extract metadata using the Cassandra connector, ensure the user in the connection has the following permissions:
 - Read Permissions: The ability to query tables and perform data extraction.
 - Schema Operations: Access to list and describe keyspaces and tables.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Cassandra"} selectServicePath={"/public/images/connectors/cassandra/select-service.png"} addNewServicePath={"/public/images/connectors/cassandra/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/cassandra/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 - **Username**: Username to connect to Cassandra. This user must have the necessary permissions to perform metadata extraction and table queries.

connectors/database/clickhouse/hybrid-runner.mdx

@@ -19,8 +19,8 @@
 stage="PROD"
 availableFeatures={["Metadata", "Query Usage", "Lineage", "Column-level Lineage", "Data Profiler", "Data Quality", "dbt", "Sample Data", "Reverse Metadata (Collate Only)", "Auto-Classification"]}
 unavailableFeatures={["Owners", "Tags", "Stored Procedures"]} />
 In this section, we provide guides and references to use the Clickhouse connector.
 Configure and schedule Clickhouse metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
   - [Profiler \& Data Quality](#profiler-&-data-quality)
   - [Usage \& Lineage](#usage-&-lineage)
@@ -30,7 +30,7 @@
 - [Related](#related)
 - [Reverse Metadata](#reverse-metadata)
 ## Requirements
 Clickhouse user must grant `SELECT` privilege on `system.*` and schema/tables to fetch the metadata of tables and views.
 * Create a new user
 * More details https://clickhouse.com/docs/en/sql-reference/statements/create/user
 ```sql
@@ -45,12 +45,12 @@
 GRANT SELECT ON <schema_name>.* to <username>;
 ```
 ### Profiler & Data Quality
 Executing the profiler workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](/how-to-guides/data-quality-observability/profiler/profiler-workflow) and data quality tests [here](/how-to-guides/data-quality-observability/quality).
 ### Usage & Lineage
 For the usage and lineage workflow, the user will need `SELECT` privilege. You can find more information on the usage workflow [here](/how-to-guides/guide-for-data-users/ingestion/workflows/usage) and the lineage workflow [here](/how-to-guides/guide-for-data-users/ingestion/workflows/lineage).
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"ClickHouse"} selectServicePath={"/public/images/connectors/clickhouse/select-service.png"} addNewServicePath={"/public/images/connectors/clickhouse/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/clickhouse/service-connection.png"} />
-# Connection Options
+## Connection Options
 <Steps>
 <Step title="Connection Options">
 <Tip>

connectors/database/cockroach/hybrid-runner.mdx

@@ -33,7 +33,7 @@
 - The Hybrid Ingestion Runner is installed and configured, and can reach both CockroachDB and the Collate SaaS control plane.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"CockroachDB"} selectServicePath={"/public/images/connectors/cockroach/select-service.png"} addNewServicePath={"/public/images/connectors/cockroach/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/cockroach/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>
@@ -62,9 +62,9 @@
 - **prefer**: SSL is used if the server supports it.
 - **require**: SSL is required.
 - **verify-ca**: SSL must be used and the server certificate must be verified.
 - **verify-full**: SSL must be used. The server certificate must be verified, and the server hostname must match the hostname attribute on the certificate.
 **SSL Configuration**
 In order to integrate SSL in the Metadata Ingestion Config, the user will have to add the SSL config under sslConfig which is placed in the source.
 ## Securing Cockroach Connection with SSL in OpenMetadata
 To establish secure connections between OpenMetadata and a Cockroach database, you can configure SSL using different SSL modes provided by Cockroach, each offering varying levels of security.
 Under `Advanced Config`, specify the SSL mode appropriate for your connection, such as `prefer`, `verify-ca`, `allow`, and others. After selecting the SSL mode, provide the CA certificate used for SSL validation (`caCertificate`). Note that Cockroach requires only the CA certificate for SSL validation.

connectors/database/cockroach/index.mdx

@@ -27,7 +27,7 @@
 ## Requirements
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"CockroachDB"} selectServicePath={"/public/images/connectors/cockroach/select-service.png"} addNewServicePath={"/public/images/connectors/cockroach/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/cockroach/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 - **Username**: Specify the User to connect to Cockroach. It should have enough privileges to read all the metadata.
@@ -48,9 +48,9 @@
 - **prefer**: SSL is used if the server supports it.
 - **require**: SSL is required.
 - **verify-ca**: SSL must be used and the server certificate must be verified.
 - **verify-full**: SSL must be used. The server certificate must be verified, and the server hostname must match the hostname attribute on the certificate.
 **SSL Configuration**
 In order to integrate SSL in the Metadata Ingestion Config, the user will have to add the SSL config under sslConfig which is placed in the source.
 ## Securing Cockroach Connection with SSL in OpenMetadata
 To establish secure connections between OpenMetadata and a Cockroach database, you can configure SSL using different SSL modes provided by Cockroach, each offering varying levels of security.
 Under `Advanced Config`, specify the SSL mode appropriate for your connection, such as `prefer`, `verify-ca`, `allow`, and others. After selecting the SSL mode, provide the CA certificate used for SSL validation (`caCertificate`). Note that Cockroach requires only the CA certificate for SSL validation.

connectors/database/couchbase/hybrid-runner.mdx

@@ -1,6 +1,6 @@
 ---
 title: Couchbase Connector | Collate NoSQL Integration Guide
 description: Connect Couchbase to Collate effortlessly. Complete setup guide, configuration steps, and metadata extraction for your NoSQL database connector.
 slug: /connectors/database/couchbase
 sidebarTitle: Hybrid Runner
 ---
@@ -18,13 +18,13 @@
 stage="BETA"
 availableFeatures={["Metadata"]}
 unavailableFeatures={["Owners", "Tags", "Stored Procedures", "Query Usage", "Lineage", "Column-level Lineage", "Data Profiler", "Data Quality", "dbt", "Sample Data", "Auto-Classification"]} />
 In this section, we provide guides and references to use the Couchbase connector.
 Configure and schedule Couchbase metadata workflows from the Collate UI:
 - [Metadata Ingestion](#metadata-ingestion)
 - [Troubleshooting](/connectors/database/couchbase/troubleshooting)
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Couchbase"} selectServicePath={"/public/images/connectors/couchbase/select-service.png"} addNewServicePath={"/public/images/connectors/couchbase/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/couchbase/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/database/couchbase/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Couchbase Connector | Collate NoSQL Integration Guide
 description: Connect Couchbase to Collate effortlessly. Complete setup guide, configuration steps, and metadata extraction for your NoSQL database connector.
 slug: /connectors/database/couchbase
 sidebarTitle: SaaS/BYOC
 ---
@@ -18,13 +18,13 @@
 stage="BETA"
 availableFeatures={["Metadata"]}
 unavailableFeatures={["Owners", "Tags", "Stored Procedures", "Query Usage", "Lineage", "Column-level Lineage", "Data Profiler", "Data Quality", "dbt", "Sample Data", "Auto-Classification"]} />
 In this section, we provide guides and references to use the Couchbase connector.
 Configure and schedule Couchbase metadata workflows from the Collate UI:
 - [Metadata Ingestion](#metadata-ingestion)
 - [Troubleshooting](/connectors/database/couchbase/troubleshooting)
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Couchbase"} selectServicePath={"/public/images/connectors/couchbase/select-service.png"} addNewServicePath={"/public/images/connectors/couchbase/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/couchbase/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 - **Username**: Username to connect to Couchbase.

connectors/database/databricks/hybrid-runner.mdx

@@ -1,6 +1,6 @@
 ---
 title: Databricks Connector | Collate Integration Guide
 description: Connect Databricks to Collate effortlessly. Complete setup guide, configuration steps, and metadata extraction for your data lakehouse platform.
 slug: /connectors/database/databricks
 sidebarTitle: Hybrid Runner
 ---
@@ -23,8 +23,8 @@
 <Tip>
 As per the [documentation](https://docs.databricks.com/en/data-governance/unity-catalog/tags.html#manage-tags-with-sql-commands) here, note that we only support metadata `tag` extraction for Databricks version 13.3 and higher.
 </Tip>
 In this section, we provide guides and references to use the Databricks connector.
 Configure and schedule Databricks metadata and profiler workflows from the Collate UI:
 
 <Note>
 **Iceberg Table Support**: Collate supports ingestion and profiling of Iceberg tables through Databricks. If your Iceberg tables are accessible via Databricks (or Unity Catalog), use this connector — it provides full metadata ingestion and profiler support for Iceberg tables without requiring a separate Iceberg connector.
@@ -36,13 +36,13 @@
 - [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
 - [Data Quality](/how-to-guides/data-quality-observability/quality)
 - [Lineage](/how-to-guides/data-lineage/workflow)
 - [dbt Integration](/connectors/database/dbt)
 - [Troubleshooting](/connectors/database/databricks/troubleshooting)
 - [Reverse Metadata](#reverse-metadata)
 <ExternalIngestionDeployment />
 ## Requirements
 ### Permission Requirement
 To enable full functionality of metadata extraction, profiling, usage, and lineage features in OpenMetadata, the following permissions must be granted to the relevant users in your Databricks environment.
 ### Metadata and Profiling Permissions
 These permissions are required on the catalogs, schemas, and tables from which metadata and profiling information will be ingested.
 ```sql
@@ -57,15 +57,15 @@
 GRANT SELECT ON SYSTEM.QUERY.HISTORY TO `<user>`;
 GRANT USE SCHEMA ON SCHEMA system.query TO `<user>`;
 ```
 These permissions allow access to Databricks system tables that track query activity, enabling lineage and usage statistics generation.
 <Tip>
 Adjust &lt;user&gt;, &lt;catalog_name&gt;, &lt;schema_name&gt;, and &lt;table_name&gt; according to your specific deployment and security requirements.
 </Tip>
 ## Unity Catalog
 If you are using Unity Catalog in Databricks, then checkout the [Unity Catalog](/connectors/database/unity-catalog) connector.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Databricks"} selectServicePath={"/public/images/connectors/databricks/select-service.png"} addNewServicePath={"/public/images/connectors/databricks/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/databricks/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/database/databricks/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Databricks Connector | Collate Integration Guide
 description: Connect Databricks to Collate effortlessly. Complete setup guide, configuration steps, and metadata extraction for your data lakehouse platform.
 slug: /connectors/database/databricks
 sidebarTitle: SaaS/BYOC
 ---
@@ -23,8 +23,8 @@
 <Tip>
 As per the [documentation](https://docs.databricks.com/en/data-governance/unity-catalog/tags.html#manage-tags-with-sql-commands) here, note that we only support metadata `tag` extraction for Databricks version 13.3 version and higher.
 </Tip>
 In this section, we provide guides and references to use the Databricks connector.
 Configure and schedule Databricks metadata and profiler workflows from the Collate UI:
 
 <Note>
 **Iceberg Table Support**: Collate supports ingestion and profiling of Iceberg tables through Databricks. If your Iceberg tables are accessible via Databricks (or Unity Catalog), use this connector — it provides full metadata ingestion and profiler support for Iceberg tables without requiring a separate Iceberg connector.
@@ -36,13 +36,13 @@
 - [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
 - [Data Quality](/how-to-guides/data-quality-observability/quality)
 - [Lineage](/how-to-guides/data-lineage/workflow)
 - [dbt Integration](/connectors/database/dbt)
 - [Troubleshooting](/connectors/database/databricks/troubleshooting)
 - [Reverse Metadata](#reverse-metadata)
 <ExternalIngestionDeployment />
 ## Requirements
 ### Permission Requirement
 To enable full functionality of metadata extraction, profiling, usage, and lineage features in OpenMetadata, the following permissions must be granted to the relevant users in your Databricks environment.
 ### Metadata and Profiling Permissions
 These permissions are required on the catalogs, schemas, and tables from which metadata and profiling information will be ingested.
 ```sql
@@ -57,15 +57,15 @@
 GRANT SELECT ON SYSTEM.QUERY.HISTORY TO `<user>`;
 GRANT USE SCHEMA ON SCHEMA system.query TO `<user>`;
 ```
 These permissions allow access to Databricks system tables that track query activity, enabling lineage and usage statistics generation.
 <Tip>
 Adjust &lt;user&gt;, &lt;catalog_name&gt;, &lt;schema_name&gt;, and &lt;table_name&gt; according to your specific deployment and security requirements.
 </Tip>
 ## Unity Catalog
 If you are using Unity Catalog in Databricks, then checkout the [Unity Catalog](/connectors/database/unity-catalog) connector.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Databricks"} selectServicePath={"/public/images/connectors/databricks/select-service.png"} addNewServicePath={"/public/images/connectors/databricks/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/databricks/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 - **Host and Port**: Enter the fully qualified hostname and port number for your Databricks deployment in the Host and Port field.

connectors/database/db2/hybrid-runner.mdx

@@ -31,13 +31,13 @@
 ```
 </Warning>
 In this section, we provide guides and references to use the DB2 connector.
 Configure and schedule DB2 metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](/how-to-guides/data-lineage/workflow)
 - [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
 - [Data Quality](/how-to-guides/data-quality-observability/quality)
 - [dbt Integration](/connectors/database/dbt)
 - [Troubleshooting](/connectors/database/db2/troubleshooting)
 ## Requirements
 To create a new Db2 user please follow the guidelines mentioned [here](https://www.ibm.com/docs/ko/samfess/8.2.0?topic=schema-creating-users-manually)
@@ -112,10 +112,10 @@
 GRANT SELECT ON SYSIBM.SYSSEQUENCES TO USER_NAME;
 ```
 ### Profiler & Data Quality
 Executing the profiler workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](/how-to-guides/data-quality-observability/profiler/profiler-workflow) and data quality tests [here](/how-to-guides/data-quality-observability/quality).
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"DB2"} selectServicePath={"/public/images/connectors/db2/select-service.png"} addNewServicePath={"/public/images/connectors/db2/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/db2/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/database/db2/index.mdx

@@ -31,13 +31,13 @@
 ```
 </Warning>
 In this section, we provide guides and references to use the DB2 connector.
 Configure and schedule DB2 metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Lineage](/how-to-guides/data-lineage/workflow)
 - [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
 - [Data Quality](/how-to-guides/data-quality-observability/quality)
 - [dbt Integration](/connectors/database/dbt)
 - [Troubleshooting](/connectors/database/db2/troubleshooting)
 ## Requirements
 To create a new Db2 user please follow the guidelines mentioned [here](https://www.ibm.com/docs/ko/samfess/8.2.0?topic=schema-creating-users-manually)
@@ -112,10 +112,10 @@
 GRANT SELECT ON SYSIBM.SYSSEQUENCES TO USER_NAME;
 ```
 ### Profiler & Data Quality
 Executing the profiler workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](/how-to-guides/data-quality-observability/profiler/profiler-workflow) and data quality tests [here](/how-to-guides/data-quality-observability/quality).
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"DB2"} selectServicePath={"/public/images/connectors/db2/select-service.png"} addNewServicePath={"/public/images/connectors/db2/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/db2/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 - **Username**: Specify the User to connect to DB2. It should have enough privileges to read all the metadata.

connectors/database/dbt/configure-dbt-workflow.mdx

@@ -1,8 +1,8 @@
 ---
 title: Configure dbt workflow
 description: Learn to configure dbt workflows in Collate with our step-by-step guide. Streamline data lineage, documentation, and metadata management effortlessly.
 slug: /connectors/database/dbt/configure-dbt-workflow
 sidebarTitle: Configure dbt workflow
 ---
 
 import { ConnectorDetailsHeader } from '/snippets/components/ConnectorDetailsHeader/ConnectorDetailsHeader.jsx'
@@ -13,8 +13,8 @@
 stage="PROD"
 availableFeatures={["Metadata", "Queries", "Lineage", "Tags", "Tiers", "Domains", "Custom Properties", "Glossary", "Owners", "Descriptions", "Tests", "Exposures"]} />
 
-# Configure dbt workflow
+## Configure dbt workflow
 Learn how to configure the dbt workflow to ingest dbt data from your data sources.
 
 <Note>
 **Prerequisites for dbt Core**: Before configuring the workflow, ensure you have set up artifact storage. dbt Core requires artifacts (manifest.json, catalog.json) to be accessible to Collate.
@@ -34,20 +34,20 @@
 
 ## Configuration
 
 Once the dbt metadata ingestion pipeline runs successfully and the service entities are available in Collate, dbt metadata is automatically ingested and associated with the corresponding data assets.
 
 As part of dbt ingestion, Collate can ingest and apply the following metadata from dbt:
 
 - dbt models and their relationships
 - Model and source lineage
 - dbt tests and test execution results
 - dbt tags
 - dbt owners
 - dbt descriptions
 - dbt tiers
 - dbt glossary terms
 
 This ingestion enriches the Table Entity and **populates the dbt tab on the Table Entity page**, providing a consolidated view of dbt-related context for each table.
 
 <Note>
 
@@ -57,18 +57,18 @@
 
 <img src="/public/images/features/ingestion/workflows/dbt/dbt-features/dbt-query.webp" alt="dbt" />
 
 We can create a workflow that will obtain the dbt information from the dbt files and feed it to Collate. The dbt Ingestion will be in charge of obtaining this data.
 
 ### 1. Add a dbt Ingestion
 
 From the Service Page, go to the Ingestions tab to add a new ingestion and click on Add dbt Ingestion.
 
 <img src="/public/images/features/ingestion/workflows/dbt/add-ingestion.webp" alt="add-ingestion" />
 
 ### 2. Configure the dbt Ingestion
 
 Here you can enter the configuration required for Collate to get the dbt files (manifest.json, catalog.json and run_results.json) required to extract the dbt metadata.
 Select any one of the source from below from where the dbt files can be fetched:
 
 <Tip>
 
@@ -76,29 +76,29 @@
 
 </Tip>
 
 ### dbt Core
 
 #### AWS S3 Buckets
 
 Collate connects to the AWS s3 bucket via the credentials provided and scans the AWS s3 buckets for `manifest.json`, `catalog.json` and `run_results.json` files.
 
 The name of the s3 bucket and prefix path to the folder in which the dbt files are stored can be provided. In the case where these parameters are not provided all the buckets are scanned for the files.
 
 Follow the link [here](/connectors/database/dbt/setup-multiple-dbt-projects) for instructions on setting up multiple dbt projects.
 
 <img src="/public/images/features/ingestion/workflows/dbt/aws-s3.webp" alt="aws-s3-bucket" />
 
 #### Google Cloud Storage Buckets
 
 Collate connects to the GCS bucket via the credentials provided and scans the gcp buckets for `manifest.json`, `catalog.json` and `run_results.json` files.
 
 The name of the GCS bucket and prefix path to the folder in which the dbt files are stored can be provided. In the case where these parameters are not provided all the buckets are scanned for the files.
 
 GCS credentials can be stored in two ways:
 
 **1.** Entering the credentials directly into the form
 
 Follow the link [here](/connectors/database/dbt/setup-multiple-dbt-projects) for instructions on setting up multiple dbt projects.
 
 <img src="/public/images/features/ingestion/workflows/dbt/gcp-bucket-form.webp" alt="gcp-storage-bucket-form" />
 
@@ -114,9 +114,9 @@
 
 Collate connects to Azure Storage using the credentials provided and scans the configured storage containers for `manifest.json`, `catalog.json` and `run_results.json` files.
 
 The Azure Storage account, container name, and optional folder (prefix) path where the dbt files are stored can be provided. If these parameters are not provided, all accessible containers in the storage account are scanned for the files.
 
 Follow the link [here](/connectors/database/dbt/setup-multiple-dbt-projects) for instructions on setting up multiple dbt projects.
 
 <img src="/public/images/features/ingestion/workflows/dbt/azure-config.webp" alt="azure-bucket" />
 
@@ -134,10 +134,10 @@
 
 ### dbt Cloud
 
 Click on the the link [here](https://docs.getdbt.com/guides/getting-started) for getting started with dbt cloud account setup if not done already.
 The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/docs/dbt-cloud-apis/service-tokens) to generate an authentication token for your dbt cloud account.
 
 The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
 
 <Tip>
 
@@ -162,6 +162,6 @@
 
 
 ### 3. Schedule and Deploy
 After clicking Next, you will be redirected to the Scheduling form. This will be the same as the Metadata Ingestion. Select your desired schedule and click on Deploy to find the lineage pipeline being added to the Service Ingestions.
 
 <img src="/public/images/features/ingestion/workflows/dbt/schedule-and-deploy.webp" alt="schedule-and-deploy" />

connectors/database/domo-database/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Domo Database Connector | Collate Integration Guide
 description: Connect Domo Database to Collate with our comprehensive connector guide. Setup instructions, configuration steps, and metadata extraction tips.
 slug: /connectors/database/domo-database
 sidebarTitle: Overview
 ---
@@ -18,18 +18,18 @@
 availableFeatures={["Metadata"]}
 unavailableFeatures={["Query Usage", "Data Profiler", "Data Quality", "Lineage", "Column-level Lineage", "Owners", "Tags", "Stored Procedures", "dbt", "Sample Data", "Auto-Classification"]} />
 In this section, we provide guides and references to use the DomoDatabase connector.
 Configure and schedule DomoDatabase metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
 - [dbt Integration](/connectors/database/dbt)
 - [Troubleshooting](/connectors/database/domo-database/troubleshoot)
 ## Requirements
 For metadata ingestion, make sure to add at least `data` scopes to the clientId provided.
 For questions related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Domo Database"} selectServicePath={"/public/images/connectors/domo-database/select-service.png"} addNewServicePath={"/public/images/connectors/domo-database/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/domo-database/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>

connectors/database/doris/index.mdx

@@ -19,19 +19,19 @@
 availableFeatures={["Metadata", "Data Profiler", "Data Quality", "dbt", "Sample Data", "Auto-Classification"]}
 unavailableFeatures={["Query Usage", "Lineage", "Column-level Lineage", "Owners", "Tags", "Stored Procedures"]} />
 In this section, we provide guides and references to use the Doris connector.
 Configure and schedule Doris metadata and profiler workflows from the Collate UI:
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
 - [Data Quality](/how-to-guides/data-quality-observability/quality)
 - [dbt Integration](/connectors/database/dbt)
 - [Enable Security](#securing-doris-connection-with-ssl-in-openmetadata)
 - [Troubleshooting](/connectors/database/doris/troubleshooting)
 ## Requirements
 Metadata: Doris >= 1.2.0, Data Profiler: Doris >= 2.0.2
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Doris"} selectServicePath={"/public/images/connectors/doris/select-service.png"} addNewServicePath={"/public/images/connectors/doris/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/doris/service-connection.png"} />
-# Connection Details
+## Connection Details
 <Steps>
 <Step title="Connection Details">
 <Tip>