open-metadata · ayush-shah · Nov 21, 2025 · Nov 12, 2025 · Nov 12, 2025 · Nov 12, 2025
diff --git a/components/CodeWithLanguageSelector/CodeWithLanguageSelector.tsx b/components/CodeWithLanguageSelector/CodeWithLanguageSelector.tsx
@@ -4,7 +4,7 @@ import { useCodeWithLanguageSelectorContext } from "../../context/CodeWithLangua
 import {
   getLanguageIcon,
   getLanguageName,
-} from "../../utils/CodeWithLanugageSelectorUtils";
+} from "../../utils/CodeWithLanguageSelectorUtils";
 import codeStyles from "../common/Code/Code.module.css";
 import styles from "./CodeWithLanguageSelector.module.css";
 

diff --git a/components/ErrorBoundary.tsx b/components/ErrorBoundary.tsx
@@ -23,7 +23,7 @@ class ErrorBoundary extends Component<Props, State> {
 
   public render() {
     if (this.state.hasError) {
-      return <h1>Sorry!! Some Error occured</h1>;
+      return <h1>Sorry!! Some Error occurred</h1>;
     }
 
     return this.props.children;

diff --git a/constants/Roadmap.constants.ts b/constants/Roadmap.constants.ts
@@ -270,7 +270,7 @@ export const ROADMAP_DATA: RoadmapData = {
         {
           label: "Glossary Terms Relations",
           description:
-            "Users can define relationships and associate realtionship between entities and terms. ",
+            "Users can define relationships and associate relationship between entities and terms. ",
         },
       ],
       release: 1.5,
@@ -333,7 +333,7 @@ export const ROADMAP_DATA: RoadmapData = {
         {
           label: "Data Asset Naming Conventions",
           description:
-            "Define Data Asset naming convetions and use this app to enforce and send a report to teams.",
+            "Define Data Asset naming conventions and use this app to enforce and send a report to teams.",
         },
         {
           label: "Reverse Metadata Applications",
@@ -395,7 +395,7 @@ export const ROADMAP_DATA: RoadmapData = {
         {
           label: "Pipeline Dashboard",
           description:
-            "Pipeline Dashboard - Show all ETL pipelines in an organization and how many succesful/failed/aborted/paused.",
+            "Pipeline Dashboard - Show all ETL pipelines in an organization and how many successful/failed/aborted/paused.",
         },
       ],
       release: 1.7,
@@ -450,7 +450,7 @@ export const ROADMAP_DATA: RoadmapData = {
         {
           label: "Pipeline Dashboard",
           description:
-            "Pipeline Dashboard - Show all ETL pipelines in an organization and how many succesful/failed/aborted/paused.",
+            "Pipeline Dashboard - Show all ETL pipelines in an organization and how many successful/failed/aborted/paused.",
         },
       ],
       release: 1.8,

diff --git a/content/partials/v1.10/connectors/dashboard/configure-ingestion.md b/content/partials/v1.10/connectors/dashboard/configure-ingestion.md
@@ -48,6 +48,6 @@ Make sure the regex filter pattern accounts for this fully-qualified format.
 - **Include Tags (toggle)**: Set the 'Include Tags' toggle to control whether to include tags in metadata ingestion.
 - **Include Data Models (toggle)**: Set the 'Include Data Models' toggle to control whether to include tags as part of metadata ingestion.
 - **Mark Deleted Dashboards (toggle)**: Set the 'Mark Deleted Dashboards' toggle to flag dashboards as soft-deleted if they are not present anymore in the source system.
-- **Include Draft Dashboard (toogle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
+- **Include Draft Dashboard (toggle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
 
 {% /extraContent %}
diff --git a/content/partials/v1.10/connectors/yaml/dashboard/source-config-def.md b/content/partials/v1.10/connectors/yaml/dashboard/source-config-def.md
@@ -18,7 +18,7 @@ The `sourceConfig` is defined [here](https://github.com/open-metadata/OpenMetada
 
 - **markDeletedDashboards**: Set the 'Mark Deleted Dashboards' toggle to flag dashboards as soft-deleted if they are not present anymore in the source system.
 
-- **Include Draft Dashboard (toogle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
+- **Include Draft Dashboard (toggle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
 
 - **dataModelFilterPattern**: Regex exclude or include data models that matches the pattern.
 

diff --git a/content/partials/v1.10/deployment/upgrade/upgrade-prerequisites.md b/content/partials/v1.10/deployment/upgrade/upgrade-prerequisites.md
@@ -1,6 +1,6 @@
 # Prerequisites
 
-Everytime that you plan on upgrading OpenMetadata to a newer version, make sure to go over all these steps:
+Every time that you plan on upgrading OpenMetadata to a newer version, make sure to go over all these steps:
 
 ## Backup your Metadata
 

diff --git a/content/partials/v1.10/releases/1.5.7.md b/content/partials/v1.10/releases/1.5.7.md
@@ -43,7 +43,7 @@ You can find the GitHub release [here](https://github.com/open-metadata/OpenMeta
 - Fix: Fix exception in search due to exception in database.displayName and databaseSchema.aggregation.
 - MINOR: Knowledge Center publicationDate mismatch error (Collate)
 - MINOR: Add owner label for knowledge center right panel (Collate)
-- Fix: Automator pagination & improvments (Collate)
+- Fix: Automator pagination & improvements (Collate)
 - Fix: ArchiveLog to FALSE for test connection (Collate)
 - Fix: Knowledge Page deletion is not deleting from the search index (Collate)`,
 

diff --git a/content/partials/v1.10/releases/1.6.2.md b/content/partials/v1.10/releases/1.6.2.md
@@ -33,7 +33,7 @@ You can find the GitHub release [here](https://github.com/open-metadata/OpenMeta
 - Fix: Unable to remove existing values from custom property (enum data type).
 - Fix: Custom DI description getting added with HTML p tag. (Collate)
 - Fix: Knowledge Page hierarchy state doesn't persist on refresh. (Collate)
-- Fix: Reindex Page Entitiy is Missing on Collate. (Collate)
+- Fix: Reindex Page Entity is Missing on Collate. (Collate)
 - Fix: Avoid pluralizing for custom charts. (Collate)
 - Improvement: Ability to sort the DI charts based on date or term.
 - Improvement: Support test connection api cancellation on click of cancel.

diff --git a/content/partials/v1.10/releases/1.9.0.md b/content/partials/v1.10/releases/1.9.0.md
@@ -300,7 +300,7 @@ If you want to allow your assets to belong to multiple domains, you need to go t
 - Improve profile workflow config to allow engine configuration
 - Improve template yml error handling and add ability to trigger it from specific branch
 - Add support of adding tags in test case form
-- Improve react, react-dom, react-router and dependant versions
+- Improve react, react-dom, react-router and dependent versions
 - Improve undici from 5.28.5 to 5.29.0
 - Add Postgres SP and UDF descriptions
 - Add Databricks pipeline lineage

diff --git a/content/partials/v1.11/connectors/dashboard/configure-ingestion.md b/content/partials/v1.11/connectors/dashboard/configure-ingestion.md
@@ -48,6 +48,6 @@ Make sure the regex filter pattern accounts for this fully-qualified format.
 - **Include Tags (toggle)**: Set the 'Include Tags' toggle to control whether to include tags in metadata ingestion.
 - **Include Data Models (toggle)**: Set the 'Include Data Models' toggle to control whether to include tags as part of metadata ingestion.
 - **Mark Deleted Dashboards (toggle)**: Set the 'Mark Deleted Dashboards' toggle to flag dashboards as soft-deleted if they are not present anymore in the source system.
-- **Include Draft Dashboard (toogle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
+- **Include Draft Dashboard (toggle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
 
 {% /extraContent %}
diff --git a/content/partials/v1.11/connectors/yaml/dashboard/source-config-def.md b/content/partials/v1.11/connectors/yaml/dashboard/source-config-def.md
@@ -18,7 +18,7 @@ The `sourceConfig` is defined [here](https://github.com/open-metadata/OpenMetada
 
 - **markDeletedDashboards**: Set the 'Mark Deleted Dashboards' toggle to flag dashboards as soft-deleted if they are not present anymore in the source system.
 
-- **Include Draft Dashboard (toogle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
+- **Include Draft Dashboard (toggle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
 
 - **dataModelFilterPattern**: Regex exclude or include data models that matches the pattern.
 

diff --git a/content/partials/v1.11/deployment/upgrade/upgrade-prerequisites.md b/content/partials/v1.11/deployment/upgrade/upgrade-prerequisites.md
@@ -1,6 +1,6 @@
 # Prerequisites
 
-Everytime that you plan on upgrading OpenMetadata to a newer version, make sure to go over all these steps:
+Every time that you plan on upgrading OpenMetadata to a newer version, make sure to go over all these steps:
 
 ## Backup your Metadata
 

diff --git a/content/partials/v1.11/releases/1.5.7.md b/content/partials/v1.11/releases/1.5.7.md
@@ -43,7 +43,7 @@ You can find the GitHub release [here](https://github.com/open-metadata/OpenMeta
 - Fix: Fix exception in search due to exception in database.displayName and databaseSchema.aggregation.
 - MINOR: Knowledge Center publicationDate mismatch error (Collate)
 - MINOR: Add owner label for knowledge center right panel (Collate)
-- Fix: Automator pagination & improvments (Collate)
+- Fix: Automator pagination & improvements (Collate)
 - Fix: ArchiveLog to FALSE for test connection (Collate)
 - Fix: Knowledge Page deletion is not deleting from the search index (Collate)`,
 

diff --git a/content/partials/v1.11/releases/1.6.2.md b/content/partials/v1.11/releases/1.6.2.md
@@ -33,7 +33,7 @@ You can find the GitHub release [here](https://github.com/open-metadata/OpenMeta
 - Fix: Unable to remove existing values from custom property (enum data type).
 - Fix: Custom DI description getting added with HTML p tag. (Collate)
 - Fix: Knowledge Page hierarchy state doesn't persist on refresh. (Collate)
-- Fix: Reindex Page Entitiy is Missing on Collate. (Collate)
+- Fix: Reindex Page Entity is Missing on Collate. (Collate)
 - Fix: Avoid pluralizing for custom charts. (Collate)
 - Improvement: Ability to sort the DI charts based on date or term.
 - Improvement: Support test connection api cancellation on click of cancel.

diff --git a/content/partials/v1.11/releases/1.9.0.md b/content/partials/v1.11/releases/1.9.0.md
@@ -300,7 +300,7 @@ If you want to allow your assets to belong to multiple domains, you need to go t
 - Improve profile workflow config to allow engine configuration
 - Improve template yml error handling and add ability to trigger it from specific branch
 - Add support of adding tags in test case form
-- Improve react, react-dom, react-router and dependant versions
+- Improve react, react-dom, react-router and dependent versions
 - Improve undici from 5.28.5 to 5.29.0
 - Add Postgres SP and UDF descriptions
 - Add Databricks pipeline lineage

diff --git a/content/partials/v1.9/connectors/dashboard/configure-ingestion.md b/content/partials/v1.9/connectors/dashboard/configure-ingestion.md
@@ -48,6 +48,6 @@ Make sure the regex filter pattern accounts for this fully-qualified format.
 - **Include Tags (toggle)**: Set the 'Include Tags' toggle to control whether to include tags in metadata ingestion.
 - **Include Data Models (toggle)**: Set the 'Include Data Models' toggle to control whether to include tags as part of metadata ingestion.
 - **Mark Deleted Dashboards (toggle)**: Set the 'Mark Deleted Dashboards' toggle to flag dashboards as soft-deleted if they are not present anymore in the source system.
-- **Include Draft Dashboard (toogle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
+- **Include Draft Dashboard (toggle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
 
 {% /extraContent %}
diff --git a/content/partials/v1.9/connectors/yaml/dashboard/source-config-def.md b/content/partials/v1.9/connectors/yaml/dashboard/source-config-def.md
@@ -18,7 +18,7 @@ The `sourceConfig` is defined [here](https://github.com/open-metadata/OpenMetada
 
 - **markDeletedDashboards**: Set the 'Mark Deleted Dashboards' toggle to flag dashboards as soft-deleted if they are not present anymore in the source system.
 
-- **Include Draft Dashboard (toogle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
+- **Include Draft Dashboard (toggle)**: Set the 'Include Draft Dashboard' toggle to include draft dashboards. By default it will include draft dashboards.
 
 - **dataModelFilterPattern**: Regex exclude or include data models that matches the pattern.
 

diff --git a/content/partials/v1.9/deployment/upgrade/upgrade-prerequisites.md b/content/partials/v1.9/deployment/upgrade/upgrade-prerequisites.md
@@ -1,6 +1,6 @@
 # Prerequisites
 
-Everytime that you plan on upgrading OpenMetadata to a newer version, make sure to go over all these steps:
+Every time that you plan on upgrading OpenMetadata to a newer version, make sure to go over all these steps:
 
 ## Backup your Metadata
 

diff --git a/content/partials/v1.9/releases/1.5.7.md b/content/partials/v1.9/releases/1.5.7.md
@@ -43,7 +43,7 @@ You can find the GitHub release [here](https://github.com/open-metadata/OpenMeta
 - Fix: Fix exception in search due to exception in database.displayName and databaseSchema.aggregation.
 - MINOR: Knowledge Center publicationDate mismatch error (Collate)
 - MINOR: Add owner label for knowledge center right panel (Collate)
-- Fix: Automator pagination & improvments (Collate)
+- Fix: Automator pagination & improvements (Collate)
 - Fix: ArchiveLog to FALSE for test connection (Collate)
 - Fix: Knowledge Page deletion is not deleting from the search index (Collate)`,
 

diff --git a/content/partials/v1.9/releases/1.6.2.md b/content/partials/v1.9/releases/1.6.2.md
@@ -33,7 +33,7 @@ You can find the GitHub release [here](https://github.com/open-metadata/OpenMeta
 - Fix: Unable to remove existing values from custom property (enum data type).
 - Fix: Custom DI description getting added with HTML p tag. (Collate)
 - Fix: Knowledge Page hierarchy state doesn't persist on refresh. (Collate)
-- Fix: Reindex Page Entitiy is Missing on Collate. (Collate)
+- Fix: Reindex Page Entity is Missing on Collate. (Collate)
 - Fix: Avoid pluralizing for custom charts. (Collate)
 - Improvement: Ability to sort the DI charts based on date or term.
 - Improvement: Support test connection api cancellation on click of cancel.

diff --git a/content/partials/v1.9/releases/1.9.0.md b/content/partials/v1.9/releases/1.9.0.md
@@ -300,7 +300,7 @@ If you want to allow your assets to belong to multiple domains, you need to go t
 - Improve profile workflow config to allow engine configuration
 - Improve template yml error handling and add ability to trigger it from specific branch
 - Add support of adding tags in test case form
-- Improve react, react-dom, react-router and dependant versions
+- Improve react, react-dom, react-router and dependent versions
 - Improve undici from 5.28.5 to 5.29.0
 - Add Postgres SP and UDF descriptions
 - Add Databricks pipeline lineage

diff --git a/content/v1.10.x/connectors/dashboard/domo-dashboard/yaml.md b/content/v1.10.x/connectors/dashboard/domo-dashboard/yaml.md
@@ -23,7 +23,7 @@ Configure and schedule DomoDashboard metadata and profiler workflows from the Op
 
 ## Requirements
 
-**Note:** For metadata ingestion, kindly make sure add atleast `dashboard` scopes to the clientId provided.
+**Note:** For metadata ingestion, kindly make sure add at least `dashboard` scopes to the clientId provided.
 Question related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
 
 ### Python Requirements

diff --git a/content/v1.10.x/connectors/database/cassandra/index.md b/content/v1.10.x/connectors/database/cassandra/index.md
@@ -48,7 +48,7 @@ To extract metadata using the Cassandra connector, ensure the user in the connec
 #### Connection Details
 
 - **Username**: Username to connect to Cassandra. This user must have the necessary permissions to perform metadata extraction and table queries.
-- **Host Port**: When using the `cassandra` connecion schema, the hostPort parameter specifies the host and port of the Cassandra. This should be specified as a string in the format `hostname:port`. E.g., `localhost:9042`.- **databaseName**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
+- **Host Port**: When using the `cassandra` connection schema, the hostPort parameter specifies the host and port of the Cassandra. This should be specified as a string in the format `hostname:port`. E.g., `localhost:9042`.- **databaseName**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
 
 **Auth Type**: Following authentication types are supported:
 1. **Basic Authentication**:

diff --git a/content/v1.10.x/connectors/database/cassandra/yaml.md b/content/v1.10.x/connectors/database/cassandra/yaml.md
@@ -73,7 +73,7 @@ This is a sample config for Cassandra:
 
 {% codeInfo srNumber=3 %}
 
-**hostPort**: When using the `cassandra` connecion schema, the hostPort parameter specifies the host and port of the Cassandra. This should be specified as a string in the format `hostname:port`. E.g., `localhost:9042`.
+**hostPort**: When using the `cassandra` connection schema, the hostPort parameter specifies the host and port of the Cassandra. This should be specified as a string in the format `hostname:port`. E.g., `localhost:9042`.
 
 {% /codeInfo %}
 

diff --git a/content/v1.10.x/connectors/database/domo-database/yaml.md b/content/v1.10.x/connectors/database/domo-database/yaml.md
@@ -26,7 +26,7 @@ Configure and schedule DomoDatabase metadata and profiler workflows from the Ope
 
 **Note:**
 
-For metadata ingestion, kindly make sure add atleast `data` scopes to the clientId provided.
+For metadata ingestion, kindly make sure add at least `data` scopes to the clientId provided.
 Question related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
 
 

diff --git a/content/v1.10.x/connectors/database/mongodb/index.md b/content/v1.10.x/connectors/database/mongodb/index.md
@@ -65,7 +65,7 @@ For a complete guide on managing secrets in hybrid setups, see the [Hybrid Inges
 
 - **Username**: Username to connect to Mongodb. This user must have access to perform `find` operation on collection and `listCollection` operations on database available in MongoDB.
 - **Password**: Password to connect to MongoDB.
-- **Host Port**: When using the `mongodb` connecion schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname:port`. E.g., `localhost:27017`. When using the `mongodb+srv` connection schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname`. E.g., `cluster0-abcde.mongodb.net`.
+- **Host Port**: When using the `mongodb` connection schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname:port`. E.g., `localhost:27017`. When using the `mongodb+srv` connection schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname`. E.g., `cluster0-abcde.mongodb.net`.
 - **databaseName**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
 
 Using Atlas? Follow [this guide](https://www.mongodb.com/docs/guides/atlas/connection-string/) to get the connection string.

diff --git a/content/v1.10.x/connectors/database/mongodb/yaml.md b/content/v1.10.x/connectors/database/mongodb/yaml.md
@@ -75,7 +75,7 @@ This is a sample config for MongoDB:
 
 {% codeInfo srNumber=3 %}
 
-**hostPort**: When using the `mongodb` connecion schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname:port`. E.g., `localhost:27017`. When using the `mongodb+srv` connection schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname`. E.g., `cluster0-abcde.mongodb.net`.
+**hostPort**: When using the `mongodb` connection schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname:port`. E.g., `localhost:27017`. When using the `mongodb+srv` connection schema, the hostPort parameter specifies the host and port of the MongoDB. This should be specified as a string in the format `hostname`. E.g., `cluster0-abcde.mongodb.net`.
 
 Using Atlas? Follow [this guide](https://www.mongodb.com/docs/guides/atlas/connection-string/) to get the connection string.
 

diff --git a/content/v1.10.x/connectors/database/redshift/index.md b/content/v1.10.x/connectors/database/redshift/index.md
@@ -72,7 +72,7 @@ For the usage and lineage workflow, the user will need `SELECT` privilege on `ST
 } 
 /%}
 
-It is recommmended to exclude the schema "information_schema" from the metadata ingestion as it contains system tables and views.
+It is recommended to exclude the schema "information_schema" from the metadata ingestion as it contains system tables and views.
 
 {% stepsContainer %}
 {% extraContent parentTagName="stepsContainer" %}

diff --git a/content/v1.10.x/connectors/database/redshift/troubleshooting.md b/content/v1.10.x/connectors/database/redshift/troubleshooting.md
@@ -23,7 +23,7 @@ src="/images/v1.10/connectors/redshift/service-connection-arguments.png"
 alt="Configure service connection"
 caption="Configure the service connection by filling the form" /%}
 
-### Metdata Ingestion Failure
+### Metadata Ingestion Failure
 
 If your metadata ingesiton fails and you have errors like:
 

diff --git a/content/v1.10.x/connectors/database/redshift/yaml.md b/content/v1.10.x/connectors/database/redshift/yaml.md
@@ -68,7 +68,7 @@ The workflow is modeled around the following
 
 **Note:** During the metadata ingestion for redshift, the tables in which the distribution style i.e `DISTSTYLE` is not `AUTO` will be marked as partitioned tables
 
-It is recommmended to exclude the schema "information_schema" from the metadata ingestion as it contains system tables and views.
+It is recommended to exclude the schema "information_schema" from the metadata ingestion as it contains system tables and views.
 
 ### 1. Define the YAML Config
 

diff --git a/...v1.10.x/connectors/ingestion/workflows/metadata/incremental-extraction/index.md b/...v1.10.x/connectors/ingestion/workflows/metadata/incremental-extraction/index.md
@@ -14,7 +14,7 @@ The default Metadata Ingestion roughly follows these steps:
 
 While on one hand this is a great simple way of doing things that works for most use cases since at every ingestion pipeline run we get the whole Source state, on other hand this is fetching and comparing a lot of data without need since if there were no structural changes we already know there is nothing to update on OpenMetadata.
 
-We implemented the Incremental Extraction feature to improve the performance by diminishing the extraction and comparison of uneeded data.
+We implemented the Incremental Extraction feature to improve the performance by diminishing the extraction and comparison of unneeded data.
 
 How this is done depends a lot on the Source itself, but the general idea is to follow these steps: