This is an automated email from the ASF dual-hosted git repository.
henry3260 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 9a0d1d3334e Fix duplicated and incorrect words in documentation
(#70868)
9a0d1d3334e is described below
commit 9a0d1d3334e8e79c61e44ead645ff81698a5317a
Author: Saumyaranjan Nayak <[email protected]>
AuthorDate: Sat Aug 1 19:42:23 2026 +0530
Fix duplicated and incorrect words in documentation (#70868)
---
ISSUE_TRIAGE_PROCESS.rst | 2 +-
contributing-docs/18_contribution_workflow.rst | 2 +-
providers/common/io/docs/xcom_backend.rst | 4 ++--
providers/weaviate/docs/connections.rst | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index 0e9a85b6f1d..8decb928c4e 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -115,7 +115,7 @@ There are several actions an issue triager might take:
* Assigning the issue to a milestone, if the issue seems important enough that
it should likely be looked
at before the next release but there is not enough information or doubts on
why and what can be fixed.
- Usually we assign to the the next bugfix release - then, no matter what the
issue will be looked at
+ Usually we assign to the next bugfix release - then, no matter what the
issue will be looked at
by the release manager and it might trigger additional actions during the
release preparation.
This is usually followed by one of the actions below.
diff --git a/contributing-docs/18_contribution_workflow.rst
b/contributing-docs/18_contribution_workflow.rst
index e217154e950..86181a11043 100644
--- a/contributing-docs/18_contribution_workflow.rst
+++ b/contributing-docs/18_contribution_workflow.rst
@@ -276,7 +276,7 @@ The reviewers might leave several types of responses:
the comment, you can ask for clarifications. Generally assume good intention
of the person who is reviewing
your code and resolve conversations also having good intentions. Understand
that it's not a person that
is criticised or argued with, but rather the code and the approach. The
important thing is to take care
- about quality of the the code and the project and want to make sure that the
code is good.
+ about quality of the code and the project and want to make sure that the
code is good.
It's ok to mark the conversation resolved by anyone who can do it - it could
be the author, who thinks
the arguments are changes implemented make the conversation resolved, or the
maintainer/person who
diff --git a/providers/common/io/docs/xcom_backend.rst
b/providers/common/io/docs/xcom_backend.rst
index ae2a8bc3673..47c1bd8a869 100644
--- a/providers/common/io/docs/xcom_backend.rst
+++ b/providers/common/io/docs/xcom_backend.rst
@@ -21,8 +21,8 @@ Object Storage XCom Backend
The default XCom backend is the :class:`~airflow.models.xcom.BaseXCom` class,
which stores XComs in the Airflow database. This is fine for small values, but
can be problematic for large values, or for large numbers of XComs.
To enable storing XComs in an object store, you can set the ``xcom_backend``
configuration option to
``airflow.providers.common.io.xcom.backend.XComObjectStorageBackend``. You will
also need to set ``xcom_objectstorage_path`` to the desired location. The
connection
-id is obtained from the user part of the url the you will provide, e.g.
``xcom_objectstorage_path = s3://conn_id@mybucket/key``. Furthermore,
``xcom_objectstorage_threshold`` is required
-to be something larger than -1. Any object smaller than the threshold in bytes
will be stored in the database and anything larger will be be
+id is obtained from the user part of the url that you will provide, e.g.
``xcom_objectstorage_path = s3://conn_id@mybucket/key``. Furthermore,
``xcom_objectstorage_threshold`` is required
+to be something larger than -1. Any object smaller than the threshold in bytes
will be stored in the database and anything larger will be
put in object storage. This will allow a hybrid setup. If an xcom is stored on
object storage a reference will be
saved in the database. Finally, you can set ``xcom_objectstorage_compression``
to fsspec supported compression methods like ``zip`` or ``snappy`` to
compress the data before storing it in object storage.
diff --git a/providers/weaviate/docs/connections.rst
b/providers/weaviate/docs/connections.rst
index 428d058d3e9..5206b1ce9a4 100644
--- a/providers/weaviate/docs/connections.rst
+++ b/providers/weaviate/docs/connections.rst
@@ -66,7 +66,7 @@ gRPC port (optional)
The port to use for the Weaviate cluster gRPC API.
Use a secure channel for the underlying gRPC API (optional)
- Whether to use a secure channel for the the Weaviate cluster gRPC API.
+ Whether to use a secure channel for the Weaviate cluster gRPC API.
Supported Authentication Methods
