Skip to content

docs: Fix typos and file naming inconsistencies in provider documentation#63683

Merged
potiuk merged 5 commits intoapache:mainfrom
Shrividya:fix-typos-in-documentation
Mar 16, 2026
Merged

docs: Fix typos and file naming inconsistencies in provider documentation#63683
potiuk merged 5 commits intoapache:mainfrom
Shrividya:fix-typos-in-documentation

Conversation

@Shrividya
Copy link
Copy Markdown
Contributor

@Shrividya Shrividya commented Mar 15, 2026

This PR fixes several documentation issues:

  • Fixed typos in documentation_building.rst
  • Renamed pagerdurty.rst to pagerduty.rst in providers/pagerduty/docs/connections/ to fix incorrect naming
  • Fixed duplicate include:: directive for INSTALLING_PROVIDERS_FROM_SOURCES_CONTENT_RST in check_provider_docs.py

Was generative AI tooling used to co-author this PR?
  • Yes - Used for review feedback and wording refinement; content authored by contributor

Generated-by: Cursor(Composer 1.5) following the guidelines


  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pagerduty.rst file was named as pagerdurty in providers/pagerduty/docs/connections/ path.
This commit is to rename it to the consistent naming.
@boring-cyborg
Copy link
Copy Markdown

boring-cyborg bot commented Mar 15, 2026

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

@potiuk potiuk merged commit fb640df into apache:main Mar 16, 2026
71 checks passed
@boring-cyborg
Copy link
Copy Markdown

boring-cyborg bot commented Mar 16, 2026

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

github-actions bot pushed a commit that referenced this pull request Mar 16, 2026
…er documentation (#63683)

* fix typos in documentation_building.rst

* fix typo by renaming the pagerduty.rst file

pagerduty.rst file was named as pagerdurty in providers/pagerduty/docs/connections/ path.
This commit is to rename it to the consistent naming.

* fix double include:: for INSTALLING_PROVIDERS_FROM_SOURCES_CONTENT_RST in check_provider_docs.py

---------
(cherry picked from commit fb640df)

Co-authored-by: Shrividya Hegde <5312302+Shrividya@users.noreply.github.com>
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@github-actions
Copy link
Copy Markdown

Backport successfully created: v3-1-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test PR Link

@Shrividya Shrividya deleted the fix-typos-in-documentation branch March 16, 2026 15:50
fat-catTW pushed a commit to fat-catTW/airflow that referenced this pull request Mar 22, 2026
…tion (apache#63683)

* fix typos in documentation_building.rst

* fix typo by renaming the pagerduty.rst file

pagerduty.rst file was named as pagerdurty in providers/pagerduty/docs/connections/ path.
This commit is to rename it to the consistent naming.

* fix double include:: for INSTALLING_PROVIDERS_FROM_SOURCES_CONTENT_RST in check_provider_docs.py

---------

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@eladkal eladkal removed the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants