diff --git a/openmetadata-docs/content/openmetadata/ingestion/workflows/profiler/index.md b/openmetadata-docs/content/openmetadata/ingestion/workflows/profiler/index.md
index b001e2b6278..01a7c1ee0c7 100644
--- a/openmetadata-docs/content/openmetadata/ingestion/workflows/profiler/index.md
+++ b/openmetadata-docs/content/openmetadata/ingestion/workflows/profiler/index.md
@@ -92,9 +92,9 @@ This setting allows you exclude or include specific column from the profiler. It
 
 ## YAML Configuration
 
-In the [connectors](/openmetadata/connectors) section we showcase how to run the metadata ingestion from a JSON file using  the Airflow SDK or the CLI via metadata ingest. Running a profiler workflow is also possible using a JSON configuration file. 
+In the [connectors](/openmetadata/connectors) section we showcase how to run the metadata ingestion from a JSON file using the Airflow SDK or the CLI via metadata ingest. Running a profiler workflow is also possible using a JSON configuration file.
 
-This is a good option if you which to execute your workflow via the Airflow SDK or using the CLI. The serviceConnection config will be specific to your connector (you can find more information in the [connectors](/openmetadata/connectors) section), though the sourceConfig for the profiler will be similar across all connectors.
+This is a good option if you which to execute your workflow via the Airflow SDK or using the CLI; if you use the CLI a profile workflow can be triggered with the command `metadata profile -c FILENAME.yaml`. The `serviceConnection` config will be specific to your connector (you can find more information in the [connectors](/openmetadata/connectors) section), though the sourceConfig for the profiler will be similar across all connectors.
 
 ```yaml
 
@@ -115,4 +115,4 @@ This is a good option if you which to execute your workflow via the Airflow SDK
           - orders
           - customers
   [...]
-```
\ No newline at end of file
+```