Docs: Fix Copilot-identified issues in pipeline connectors

- Fix Dagster port typo (300 → 3000)
- Fix KafkaConnect troubleshooting links
- Fix Data Factory typo (DData → Data)
- Fix grammar errors (should be perform → should be performed)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: “Rounak

connectors/pipeline/dagster/hybrid-runner.mdx

@@ -32,7 +32,7 @@ The ingestion framework uses [dagster graphql python client](https://docs.dagste
 ## Connection Details
 <Steps>
 <Step title="Connection Details">
-- **Host**: Host of the dagster eg.`https://localhost:300` or `https://127.0.0.1:3000` or `https://<yourorghere>.dagster.cloud/prod`
+- **Host**: Host of the dagster eg.`https://localhost:3000` or `https://127.0.0.1:3000` or `https://<yourorghere>.dagster.cloud/prod`
 - **Token** : Need pass token if connecting to `dagster cloud` instance
   - Log in to your Dagster account.
   - Click on the "Settings" link in the top navigation bar.

connectors/pipeline/dagster/index.mdx

@@ -32,7 +32,7 @@ The ingestion framework uses [dagster graphql python client](https://docs.dagste
 ## Connection Details
 <Steps>
 <Step title="Connection Details">
-- **Host**: Host of the dagster eg.`https://localhost:300` or `https://127.0.0.1:3000` or `https://<yourorghere>.dagster.cloud/prod`
+- **Host**: Host of the dagster eg.`https://localhost:3000` or `https://127.0.0.1:3000` or `https://<yourorghere>.dagster.cloud/prod`
 - **Token** : Need pass token if connecting to `dagster cloud` instance
   - Log in to your Dagster account.
   - Click on the "Settings" link in the top navigation bar.

connectors/pipeline/datafactory/hybrid-runner.mdx

@@ -72,7 +72,7 @@ Ensure that the service principal or managed identity you’re using has the nec
 ## Displaying Lineage Information
 Steps to retrieve and display the lineage information for a Data Factory service.
 1. Ingest Source and Sink Database Metadata: Identify both the source and sink database used by the Azure Data Factory service for example Redshift. Ingest metadata for these database.
-2. Ingest Data Factory Service Metadata: Finally, Ingest your DData Factory service.
+2. Ingest Data Factory Service Metadata: Finally, Ingest your Data Factory service.
 By successfully completing these steps, the lineage information for the service will be displayed.
 ### Missing Lineage
 If lineage information is not displayed for a Data Factory service, follow these steps to diagnose the issue.

connectors/pipeline/datafactory/index.mdx

@@ -72,7 +72,7 @@ Ensure that the service principal or managed identity you’re using has the nec
 ## Displaying Lineage Information
 Steps to retrieve and display the lineage information for a Data Factory service.
 1. Ingest Source and Sink Database Metadata: Identify both the source and sink database used by the Azure Data Factory service for example Redshift. Ingest metadata for these database.
-2. Ingest Data Factory Service Metadata: Finally, Ingest your DData Factory service.
+2. Ingest Data Factory Service Metadata: Finally, Ingest your Data Factory service.
 By successfully completing these steps, the lineage information for the service will be displayed.
 ### Missing Lineage
 If lineage information is not displayed for a Data Factory service, follow these steps to diagnose the issue.

connectors/pipeline/flink/hybrid-runner.mdx

@@ -39,7 +39,7 @@ The ingestion framework uses flink REST APIs to connect to the instance and perf
         - caCertificate: Authorized certificate for ssl configured server.
         - sslCertificate: SSL certificate for the server.
         - sslKey: Server root key for the connection.
-- **verifySSL** : Whether SSL verification should be perform when authenticating.
+- **verifySSL** : Whether SSL verification should be performed when authenticating.
 </Step>
 <TestConnection />
 <ConfigureIngestion />

connectors/pipeline/flink/index.mdx

@@ -39,7 +39,7 @@ The ingestion framework uses flink REST APIs to connect to the instance and perf
         - caCertificate: Authorized certificate for ssl configured server.
         - sslCertificate: SSL certificate for the server.
         - sslKey: Server root key for the connection.
-- **verifySSL** : Whether SSL verification should be perform when authenticating.
+- **verifySSL** : Whether SSL verification should be performed when authenticating.
 </Step>
 <TestConnection />
 <ConfigureIngestion />

connectors/pipeline/kafkaconnect/hybrid-runner.mdx

@@ -23,7 +23,7 @@ Configure and schedule KafkaConnect metadata workflows from the Collate UI:
 - [Metadata Ingestion](#metadata-ingestion)
     - [Connection Details](#connection-details)
     - [Metadata Ingestion Options](#metadata-ingestion-options)
-- [Troubleshooting](/connectors/pipeline/glue-pipeline/troubleshooting)
+- [Troubleshooting](/connectors/pipeline/kafkaconnect/troubleshooting)
 ## Requirements
 ### KafkaConnect Versions
 OpenMetadata is integrated with kafkaconnect up to version [3.6.1](https://docs.kafkaconnect.io/getting-started) and will continue to work for future kafkaconnect versions.
@@ -38,7 +38,7 @@ The ingestion framework uses [kafkaconnect python client](https://libraries.io/p
     1. Basic Authentication
         - Username: Username to connect to Kafka Connect. This user should be able to send request to the Kafka Connect API and access the [Rest API](https://docs.confluent.io/platform/current/connect/references/restapi.html) GET endpoints.
         - Password: Password to connect to Kafka Connect.
-- **verifySSL** : Whether SSL verification should be perform when authenticating.
+- **verifySSL** : Whether SSL verification should be performed when authenticating.
 - **Kafka Service Name** : The Service Name of the Ingested [Kafka](/connectors/messaging/kafka#4.-name-and-describe-your-service) instance associated with this KafkaConnect instance.
 </Step>
 <TestConnection />

connectors/pipeline/kafkaconnect/index.mdx

@@ -23,7 +23,7 @@ Configure and schedule KafkaConnect metadata workflows from the Collate UI:
 - [Metadata Ingestion](#metadata-ingestion)
     - [Connection Details](#connection-details)
     - [Metadata Ingestion Options](#metadata-ingestion-options)
-- [Troubleshooting](/connectors/pipeline/glue-pipeline/troubleshooting)
+- [Troubleshooting](/connectors/pipeline/kafkaconnect/troubleshooting)
 ## Requirements
 ### KafkaConnect Versions
 OpenMetadata is integrated with kafkaconnect up to version [3.6.1](https://docs.kafkaconnect.io/getting-started) and will continue to work for future kafkaconnect versions.
@@ -38,7 +38,7 @@ The ingestion framework uses [kafkaconnect python client](https://libraries.io/p
     1. Basic Authentication
         - Username: Username to connect to Kafka Connect. This user should be able to send request to the Kafka Connect API and access the [Rest API](https://docs.confluent.io/platform/current/connect/references/restapi.html) GET endpoints.
         - Password: Password to connect to Kafka Connect.
-- **verifySSL** : Whether SSL verification should be perform when authenticating.
+- **verifySSL** : Whether SSL verification should be performed when authenticating.
 - **Kafka Service Name** : The Service Name of the Ingested [Kafka](/connectors/messaging/kafka#4.-name-and-describe-your-service) instance associated with this KafkaConnect instance.
 </Step>
 <TestConnection />

connectors/pipeline/nifi/index.mdx

@@ -45,7 +45,7 @@ For a complete guide on managing secrets in hybrid setups, see the [Hybrid Inges
     1. Basic Authentication
         - Username: Username to connect to NiFi. This user should be able to send request to the Nifi API and access the `Resources` endpoint.
         - Password: Password to connect to NiFi.
-        - Verify SSL: Whether SSL verification should be perform when authenticating.
+        - Verify SSL: Whether SSL verification should be performed when authenticating.
     2. Client Certificate Authentication
         - Certificate Authority Path: Path to the certificate authority (CA) file. This is the certificate used to store and issue your digital certificate. This is an optional parameter. If omitted SSL verification will be skipped; this can present some sever security issue.
         **important**: This file should be accessible from where the ingestion workflow is running. For example, if you are using OpenMetadata Ingestion Docker container, this file should be in this container.

connectors/pipeline/nifi/yaml.mdx

@@ -54,7 +54,7 @@ This is a sample config for NiFi:
   **1.** Using Basic authentication
     - **username**: Username to connect to NiFi. This user should be able to send request to the NiFi API and access the `Resources` endpoint.
     - **password**: Password to connect to NiFi.
-    - **verifySSL**: Whether SSL verification should be perform when authenticating.
+    - **verifySSL**: Whether SSL verification should be performed when authenticating.
   **2.** Using client certificate authentication
     - **certificateAuthorityPath**: Path to the certificate authority (CA) file. This is the certificate used to store and issue your digital certificate. This is an optional parameter. If omitted SSL verification will be skipped; this can present some sever security issue.
     **important**: This file should be accessible from where the ingestion workflow is running. For example, if you are using OpenMetadata Ingestion Docker container, this file should be in this container.