This is an automated email from the ASF dual-hosted git repository.
shahar pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-1-test by this push:
new 0748bde2f93 [v3-1-test] docs(contributing-docs): fix some typos and
unmatched parentheses (#60787) (#60790)
0748bde2f93 is described below
commit 0748bde2f9303e745884a8e1f9b2e6c163fc6259
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jan 19 21:21:06 2026 +0200
[v3-1-test] docs(contributing-docs): fix some typos and unmatched
parentheses (#60787) (#60790)
(cherry picked from commit f2f1a0826cc50c5525af3add9bf55539dcf319cd)
Co-authored-by: Tim Hsiung <[email protected]>
---
contributing-docs/03_contributors_quick_start.rst | 4 ++--
contributing-docs/05_pull_requests.rst | 2 +-
contributing-docs/11_documentation_building.rst | 2 +-
contributing-docs/12_provider_distributions.rst | 2 +-
contributing-docs/13_airflow_dependencies_and_extras.rst | 6 +++---
5 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/contributing-docs/03_contributors_quick_start.rst
b/contributing-docs/03_contributors_quick_start.rst
index c0ef2f91fce..b331b1dc610 100644
--- a/contributing-docs/03_contributors_quick_start.rst
+++ b/contributing-docs/03_contributors_quick_start.rst
@@ -224,7 +224,7 @@ Forking and cloning Project
3. Follow `Cloning a repository
<https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository>`_
to clone the repo locally (you can also do it in your IDE - see the `Using
your IDE`_
- chapter below
+ chapter below)
.. note::
For windows based machines, on cloning, the Git line endings may be
different from unix based systems
@@ -401,7 +401,7 @@ see in CI in your local environment.
It is important to install version of pipx >= 1.2.1 to workaround
``packaging`` breaking change introduced
in September 2023
-2. Run ``uv tool install -e ./dev/breeze`` (or ``pipx install -e
./dev/breeze`` in your checked-out
+2. Run ``uv tool install -e ./dev/breeze`` (or ``pipx install -e
./dev/breeze``) in your checked-out
repository. Make sure to follow any instructions printed during the
installation - this is needed
to make sure that the ``breeze`` command is available in your PATH
diff --git a/contributing-docs/05_pull_requests.rst
b/contributing-docs/05_pull_requests.rst
index e865b284a27..d493d5a2c51 100644
--- a/contributing-docs/05_pull_requests.rst
+++ b/contributing-docs/05_pull_requests.rst
@@ -151,7 +151,7 @@ Gen-AI Assisted contributions
Generally, it's fine to use Gen-AI tools to help you create Pull Requests for
Apache Airflow as long as you
adhere to the following guidelines:
-* Follow the `Apache Software Foundation (ASF) Generative Tooling guideliens
<https://www.apache.org/legal/generative-tooling.html>`__.
+* Follow the `Apache Software Foundation (ASF) Generative Tooling guidelines
<https://www.apache.org/legal/generative-tooling.html>`__.
* Ensure that you review and understand all code generated by Gen-AI tools
before including it in your PR -
do not blindly trust the generated code.
* Make sure that the generated code adheres to the project's coding standards
and best practices described
diff --git a/contributing-docs/11_documentation_building.rst
b/contributing-docs/11_documentation_building.rst
index 12d87a1df31..b7dfe3abf52 100644
--- a/contributing-docs/11_documentation_building.rst
+++ b/contributing-docs/11_documentation_building.rst
@@ -116,7 +116,7 @@ Building the documentation
..........................
In Airflow 3 the documentation is placed closely to where source code is
placed (in most distribution
-packages it is in the ``doc`` subfolder of a distribution you want to build
the documentation for.
+packages, its documentation is in the ``doc`` subfolder).
Some distributions do not have ``docs`` subfolder - when they are
``doc-only``. The ``build-doc`` script
is installed automatically from ``devel-common`` distribution and available to
run using ``uv run``
command (or directly ``build-docs`` inside the ``breeze`` container). This
script will automatically
diff --git a/contributing-docs/12_provider_distributions.rst
b/contributing-docs/12_provider_distributions.rst
index dcd9f072b28..7573fd98427 100644
--- a/contributing-docs/12_provider_distributions.rst
+++ b/contributing-docs/12_provider_distributions.rst
@@ -314,7 +314,7 @@ providers.
not only "green path"
* Integration tests where 'local' integration with a component is possible
(for example tests with
- MySQL/Postgres DB/Trino/Kerberos all have integration tests which run with
real, dockerized components
+ MySQL/Postgres DB/Trino/Kerberos all have integration tests which run with
real, dockerized components)
* System Tests which provide end-to-end testing, usually testing together
several operators, sensors,
transfers connecting to a real external system
diff --git a/contributing-docs/13_airflow_dependencies_and_extras.rst
b/contributing-docs/13_airflow_dependencies_and_extras.rst
index 28ebdb67ba5..a27e0c42b14 100644
--- a/contributing-docs/13_airflow_dependencies_and_extras.rst
+++ b/contributing-docs/13_airflow_dependencies_and_extras.rst
@@ -41,7 +41,7 @@ We have big number (currently more than 100) python
distributions in Apache Airf
``apache-airflow-task-sdk`` package, ``apache-airflow-ctl`` package, and
several other packages.
They are all connected together via ``uv`` workspace feature (workspace is
defined in the root ``pyproject.toml``
-file of the repository in the ``apache-airflow`` distribution definition. The
workspace feature allows us to
+file of the repository in the ``apache-airflow`` distribution definition). The
workspace feature allows us to
run ``uv sync`` at the top of the repository to install all packages in
editable mode in the development
environment from all the distributions and resolve the dependencies together,
so that we know that
the dependencies have no conflicting requirements. Also the distributions are
referring to each other via
@@ -49,7 +49,7 @@ name - which means that when you run locally ``uv sync``, the
local version of t
ones released on PyPI, which means that you can develop and test changes that
span multiple packages at the
same time. This is a very powerful feature that allows us to maintain the
complex ecosystem of Apache Airflow
distributions in a single monorepo, and allows us - for example to add new
feature to common distributions used
-by multiple providers and test them all together before releasing new versions
of either of those pacckages
+by multiple providers and test them all together before releasing new versions
of either of those packages.
Managing dependencies in ``pyproject.toml`` files
.................................................
@@ -80,7 +80,7 @@ When you add a new dependency, you should make sure that:
development dependencies)
* Some parts of those dependencies might be automatically generated (and
overwritten) by our ``prek``
- hooks. Those are the necessary dependencies that ``prek`` hoks can figure
out automatically by
+ hooks. Those are the necessary dependencies that ``prek`` hooks can figure
out automatically by
analyzing the imports in the sources and structure of the project. We also
have special case of
shared dependencies (described in `shared dependencies document
<../shared/README.md>`__) where we
effectively "static-link" some libraries into multiple distributions, to
avoid unnecessary coupling and
