diff --git a/openmetadata-docs/content/v1.2.x/how-to-guides/data-governance/glossary/import.md b/openmetadata-docs/content/v1.2.x/how-to-guides/data-governance/glossary/import.md
index 00b1811b4cc..942e098aa46 100644
--- a/openmetadata-docs/content/v1.2.x/how-to-guides/data-governance/glossary/import.md
+++ b/openmetadata-docs/content/v1.2.x/how-to-guides/data-governance/glossary/import.md
@@ -7,6 +7,8 @@ slug: /how-to-guides/data-governance/glossary/import
 
 OpenMetadata supports **Glossary Bulk Upload** to save time and effort by uploading a CSV with thousands of terms in one go. You can create or update multiple glossary terms simultaneously. When bulk uploading, Owners and Reviewers can be defined, who will be further propagated to every glossary term.
 
+{% youtube videoId="8qfFl-ujZz0" start="0:00" end="6:47" width="560px" height="315px" /%}
+
 To import a glossary into OpenMetadata:
 - Navigate to **Govern > Glossary**
 - Click on the **⋮** icon and **Export** the glossary file. If you have glossary terms in your Glossary, the same will be exported as a CSV file. If you have If there are no terms in the Glossary, then a blank CSV template will be downloaded.
diff --git a/openmetadata-docs/content/v1.3.x-SNAPSHOT/deployment/security/enable-ssl/ssl-troubleshooting.md b/openmetadata-docs/content/v1.3.x-SNAPSHOT/deployment/security/enable-ssl/ssl-troubleshooting.md
index 2fda1d95e6d..8a6020aaa0d 100644
--- a/openmetadata-docs/content/v1.3.x-SNAPSHOT/deployment/security/enable-ssl/ssl-troubleshooting.md
+++ b/openmetadata-docs/content/v1.3.x-SNAPSHOT/deployment/security/enable-ssl/ssl-troubleshooting.md
@@ -148,7 +148,7 @@ please visit our demo repository [here](https://github.com/open-metadata/openmet
 ## Providing a single keystore that has all the cacerts required
 
 This can be achieved using the `OPENMETADATA_OPTS` environment variable configuration across all the deployments.
-However, for Production, we recommend you to bundle your cacerts separately for each components (like ElasticSearch/Opensearch and Airflow) and provide that to each individual configs for [openmetadata.yaml](/conf/openmetadata.yaml).
+However, for Production, we recommend you to bundle your cacerts separately for each components (like ElasticSearch/Opensearch and Airflow) and provide that to each individual configs for [openmetadata.yaml](https://github.com/open-metadata/OpenMetadata/blob/main/conf/openmetadata.yaml). 
 You can use this environment variable to also provide extra JVM parameters to tune the application as per your infrastructure needs.
 
 Below is an example values to be set for the `OPENMETADATA_OPTS` environment variable to use cacerts truststore which is bundled for an organization issued certificates -
diff --git a/openmetadata-docs/content/v1.3.x-SNAPSHOT/how-to-guides/data-governance/glossary/import.md b/openmetadata-docs/content/v1.3.x-SNAPSHOT/how-to-guides/data-governance/glossary/import.md
index ab903c01ee7..d407d59f016 100644
--- a/openmetadata-docs/content/v1.3.x-SNAPSHOT/how-to-guides/data-governance/glossary/import.md
+++ b/openmetadata-docs/content/v1.3.x-SNAPSHOT/how-to-guides/data-governance/glossary/import.md
@@ -7,6 +7,8 @@ slug: /how-to-guides/data-governance/glossary/import
 
 OpenMetadata supports **Glossary Bulk Upload** to save time and effort by uploading a CSV with thousands of terms in one go. You can create or update multiple glossary terms simultaneously. When bulk uploading, Owners and Reviewers can be defined, who will be further propagated to every glossary term.
 
+{% youtube videoId="8qfFl-ujZz0" start="0:00" end="6:47" width="560px" height="315px" /%}
+
 To import a glossary into OpenMetadata:
 - Navigate to **Govern > Glossary**
 - Click on the **⋮** icon and **Export** the glossary file. If you have glossary terms in your Glossary, the same will be exported as a CSV file. If you have If there are no terms in the Glossary, then a blank CSV template will be downloaded.