Skip to content

Conversation

@RounakDhillon
Copy link
Collaborator

I worked on Python Requirement Removal and Captilization Correction.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves documentation quality by standardizing product name capitalization and removing redundant Python Requirements sections. The changes correct capitalization of technical terms (Databricks, AWS S3, Unity Catalog, Spline, API, URL) across multiple connector documentation files and removes Python Requirements sections from Unity Catalog and Databricks connectors.

  • Standardized capitalization for product/service names (Databricks, AWS S3, Unity Catalog, Spline)
  • Corrected acronym capitalization (API, APIs, URL)
  • Removed Python Requirements sections from Databricks and Unity Catalog connector documentation

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
connectors/pipeline/spline/yaml.mdx Capitalized Databricks, AWS S3, and Spline references
connectors/pipeline/spline/index.mdx Capitalized Databricks, AWS S3, and Spline references
connectors/database/unity-catalog/index.mdx Removed Python Requirements section and import statement
connectors/database/sap-erp/index.mdx Capitalized API and APIs acronyms
connectors/database/databricks/yaml.mdx Capitalized Databricks reference
connectors/database/databricks/index.mdx Capitalized Databricks and Unity Catalog references, removed Python Requirements section
connectors/api/rest/yaml.mdx Capitalized URL acronym
connectors/api/rest/index.mdx Capitalized URL acronym

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

<ExternalIngestionDeployment />
## Requirements
The Spline connector support lineage of data source of type `jdbc` or `dbfs` i.e. The spline connector would be able to extract lineage if the data source is either a jdbc connection or the data source is databricks instance.
The Spline connector support lineage of data source of type `jdbc` or `dbfs` i.e. The Spline connector would be able to extract lineage if the data source is either a jdbc connection or the data source is Databricks instance.
Copy link

Copilot AI Dec 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The verb "support" should be "supports" to agree with the singular subject "The Spline connector".

Suggested change
The Spline connector support lineage of data source of type `jdbc` or `dbfs` i.e. The Spline connector would be able to extract lineage if the data source is either a jdbc connection or the data source is Databricks instance.
The Spline connector supports lineage of data source of type `jdbc` or `dbfs` i.e. The Spline connector would be able to extract lineage if the data source is either a jdbc connection or the data source is Databricks instance.

Copilot uses AI. Check for mistakes.
ayush-shah
ayush-shah previously approved these changes Dec 30, 2025
@ayush-shah ayush-shah merged commit 1d8b9d2 into open-metadata:main Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants