MINOR: docs links fix (#17125)

* alation link fix

* dbt yaml config source link fix

* bigquery doc fix

openmetadata-docs/content/v1.3.x/connectors/ingestion/workflows/dbt/ingest-dbt-yaml.md

@@ -22,12 +22,12 @@ We can create a workflow that will obtain the dbt information from the dbt files
 ## 1. Define the YAML Config
 
 Select the yaml config from one of the below sources:
-- [AWS S3 Buckets](#1.aws-s3-buckets)
-- [Google Cloud Storage Buckets](#2.google-cloud-storage-buckets)
-- [Azure Storage Buckets](#3.azure-storage-buckets)
-- [Local Storage](#4.local-storage)
-- [File Server](#5.file-server)
-- [dbt Cloud](#6.dbt-cloud)
+- [AWS S3 Buckets](#1.-aws-s3-buckets)
+- [Google Cloud Storage Buckets](#2.-google-cloud-storage-buckets)
+- [Azure Storage Buckets](#3.-azure-storage-buckets)
+- [Local Storage](#4.-local-storage)
+- [File Server](#5.-file-server)
+- [dbt Cloud](#6.-dbt-cloud)
 
 
 The dbt files should be present on the source mentioned and should have the necessary permissions to be able to access the files.

openmetadata-docs/content/v1.3.x/connectors/metadata/alation/index.md

@@ -34,7 +34,7 @@ Check the following docs to run the Ingestion Framework in any orchestrator exte
 
 ## Requirements
 
-Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis)
+Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token)
 
 ## Data Mapping and Assumptions
 

openmetadata-docs/content/v1.3.x/connectors/metadata/alation/yaml.md

@@ -23,7 +23,7 @@ Configure and schedule Alation metadata and profiler workflows from the OpenMeta
 
 ## Requirements
 
-Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis)
+Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token)
 
 ## Data Mapping and Assumptions
 
@@ -99,7 +99,7 @@ We'll use the user credentials to generate the access token required to authenti
 - password: Password of the user.
 
 2. Access Token Authentication:
-The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-via-ui) can directly be entered. We'll use that directly to authenticate the Alation APIs
+The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token) can directly be entered. We'll use that directly to authenticate the Alation APIs
 - accessToken: Generated access token
 
 {% /codeInfo %}

openmetadata-docs/content/v1.4.x/connectors/database/bigquery/create-credentials.md

@@ -95,7 +95,7 @@ src="/images/v1.4/connectors/bigquery/bq-create-service-account-1.png"
 alt="Create Service Accounts"
 caption="Create Service Accounts" /%}
 
-Grant a role to service account which has all the required permission to ingest BigQuery metadata in OpenMetadata checkout [this](/connectors/database/bigquery/roles) documentation for details on how to create a custom role with required permissions.
+Grant a role to service account which has all the required permission to ingest BigQuery metadata in OpenMetadata.
 
 {% image
 src="/images/v1.4/connectors/bigquery/bq-service-account-grant-role.png"

openmetadata-docs/content/v1.4.x/connectors/database/bigquery/yaml.md

@@ -71,7 +71,7 @@ If the user has `External Tables`, please attach relevant permissions needed for
 icon="manage_accounts"
 title="Create Custom GCP Role"
 description="Checkout this documentation on how to create a custom role and assign it to the service account."
-link="/connectors/database/bigquery/roles"
+link="/connectors/database/bigquery/create-credentials"
   / %}
 {% /tilesContainer %}
 

openmetadata-docs/content/v1.4.x/connectors/ingestion/workflows/dbt/ingest-dbt-yaml.md

@@ -22,12 +22,12 @@ We can create a workflow that will obtain the dbt information from the dbt files
 ## 1. Define the YAML Config
 
 Select the yaml config from one of the below sources:
-- [AWS S3 Buckets](#1.aws-s3-buckets)
-- [Google Cloud Storage Buckets](#2.google-cloud-storage-buckets)
-- [Azure Storage Buckets](#3.azure-storage-buckets)
-- [Local Storage](#4.local-storage)
-- [File Server](#5.file-server)
-- [dbt Cloud](#6.dbt-cloud)
+- [AWS S3 Buckets](#1.-aws-s3-buckets)
+- [Google Cloud Storage Buckets](#2.-google-cloud-storage-buckets)
+- [Azure Storage Buckets](#3.-azure-storage-buckets)
+- [Local Storage](#4.-local-storage)
+- [File Server](#5.-file-server)
+- [dbt Cloud](#6.-dbt-cloud)
 
 
 The dbt files should be present on the source mentioned and should have the necessary permissions to be able to access the files.

openmetadata-docs/content/v1.4.x/connectors/metadata/alation/index.md

@@ -26,7 +26,7 @@ Configure and schedule Alation metadata workflow from the OpenMetadata UI:
 
 ## Requirements
 
-Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis)
+Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token)
 
 ## Data Mapping and Assumptions
 
@@ -84,7 +84,7 @@ We'll use the user credentials to generate the access token required to authenti
 - **password**: Password of the user.
 
 2. **Access Token Authentication**:
-The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-via-ui) can directly be entered. We'll use that directly to authenticate the Alation APIs
+The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token) can directly be entered. We'll use that directly to authenticate the Alation APIs
 - **accessToken**: Generated access token
 
 #### For Alation backend database Connection:

openmetadata-docs/content/v1.4.x/connectors/metadata/alation/yaml.md

@@ -23,7 +23,7 @@ Configure and schedule Alation metadata and profiler workflows from the OpenMeta
 
 ## Requirements
 
-Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis)
+Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token)
 
 ## Data Mapping and Assumptions
 
@@ -99,7 +99,7 @@ We'll use the user credentials to generate the access token required to authenti
 - password: Password of the user.
 
 2. Access Token Authentication:
-The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-via-ui) can directly be entered. We'll use that directly to authenticate the Alation APIs
+The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token) can directly be entered. We'll use that directly to authenticate the Alation APIs
 - accessToken: Generated access token
 
 {% /codeInfo %}

openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/database/bigquery/create-credentials.md

@@ -95,7 +95,7 @@ src="/images/v1.5/connectors/bigquery/bq-create-service-account-1.png"
 alt="Create Service Accounts"
 caption="Create Service Accounts" /%}
 
-Grant a role to service account which has all the required permission to ingest BigQuery metadata in OpenMetadata checkout [this](/connectors/database/bigquery/roles) documentation for details on how to create a custom role with required permissions.
+Grant a role to service account which has all the required permission to ingest BigQuery metadata in OpenMetadata.
 
 {% image
 src="/images/v1.5/connectors/bigquery/bq-service-account-grant-role.png"

openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/database/bigquery/index.md

@@ -38,7 +38,7 @@ You need to create an service account in order to ingest metadata from bigquery
 icon="manage_accounts"
 title="Create Custom GCP Role"
 description="Check out this documentation on how to create a custom role and assign it to the service account."
-link="/connectors/database/bigquery/roles"
+link="/connectors/database/bigquery/create-credentials"
   / %}
 {% /tilesContainer %}
 

openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/database/bigquery/yaml.md

@@ -71,7 +71,7 @@ If the user has `External Tables`, please attach relevant permissions needed for
 icon="manage_accounts"
 title="Create Custom GCP Role"
 description="Checkout this documentation on how to create a custom role and assign it to the service account."
-link="/connectors/database/bigquery/roles"
+link="/connectors/database/bigquery/create-credentials"
   / %}
 {% /tilesContainer %}
 

openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-yaml.md

@@ -22,12 +22,12 @@ We can create a workflow that will obtain the dbt information from the dbt files
 ## 1. Define the YAML Config
 
 Select the yaml config from one of the below sources:
-- [AWS S3 Buckets](#1.aws-s3-buckets)
-- [Google Cloud Storage Buckets](#2.google-cloud-storage-buckets)
-- [Azure Storage Buckets](#3.azure-storage-buckets)
-- [Local Storage](#4.local-storage)
-- [File Server](#5.file-server)
-- [dbt Cloud](#6.dbt-cloud)
+- [AWS S3 Buckets](#1.-aws-s3-buckets)
+- [Google Cloud Storage Buckets](#2.-google-cloud-storage-buckets)
+- [Azure Storage Buckets](#3.-azure-storage-buckets)
+- [Local Storage](#4.-local-storage)
+- [File Server](#5.-file-server)
+- [dbt Cloud](#6.-dbt-cloud)
 
 
 The dbt files should be present on the source mentioned and should have the necessary permissions to be able to access the files.

openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/metadata/alation/index.md

@@ -26,7 +26,7 @@ Configure and schedule Alation metadata workflow from the OpenMetadata UI:
 
 ## Requirements
 
-Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis)
+Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token)
 
 ## Data Mapping and Assumptions
 
@@ -84,7 +84,7 @@ We'll use the user credentials to generate the access token required to authenti
 - **password**: Password of the user.
 
 2. **Access Token Authentication**:
-The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-via-ui) can directly be entered. We'll use that directly to authenticate the Alation APIs
+The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token) can directly be entered. We'll use that directly to authenticate the Alation APIs
 - **accessToken**: Generated access token
 
 #### For Alation backend database Connection:

openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/metadata/alation/yaml.md

@@ -23,7 +23,7 @@ Configure and schedule Alation metadata and profiler workflows from the OpenMeta
 
 ## Requirements
 
-Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis)
+Follow the official documentation to generate a API Access Token from [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token)
 
 ## Data Mapping and Assumptions
 
@@ -99,7 +99,7 @@ We'll use the user credentials to generate the access token required to authenti
 - password: Password of the user.
 
 2. Access Token Authentication:
-The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-via-ui) can directly be entered. We'll use that directly to authenticate the Alation APIs
+The access token created using the steps mentioned [here](https://developer.alation.com/dev/docs/authentication-into-alation-apis#create-an-api-access-token) can directly be entered. We'll use that directly to authenticate the Alation APIs
 - accessToken: Generated access token
 
 {% /codeInfo %}