diff --git a/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/external_workflow.md b/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/external_workflow.md
index fb8be020c30..240ba17ca75 100644
--- a/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/external_workflow.md
+++ b/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/external_workflow.md
@@ -9,7 +9,7 @@ slug: /connectors/ingestion/workflows/profiler/external-workflow
 
 Note that this requires OpenMetadata 1.2.1 or higher.
 
-{% note %}
+{% /note %}
 
 Consider a use case where you have a large database source with multiple databases and schemas which are maintained by 
 different teams within your organization. You have created multiple database services within OpenMetadata depending on 
diff --git a/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/sample_data.md b/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/sample_data.md
index 93ed8b5225b..b16dadc31a7 100644
--- a/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/sample_data.md
+++ b/openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/sample_data.md
@@ -9,7 +9,7 @@ slug: /connectors/ingestion/workflows/profiler/external-sample-data
 
 Note that this requires OpenMetadata 1.2.1 or higher.
 
-{% note %}
+{% /note %}
 
 While running the profiler workflow if you have enabled the `Generate Sample Data` flag in your profiler configuration, 
 sample data will be ingested for all the tables included in the profiler workflow. This data is a randomly sampled