This is an automated email from the ASF dual-hosted git repository. jedcunningham pushed a commit to branch v2-8-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit afd47ae993444ba00319f4fb9149fa531b50f0fb Author: Tamara Janina Fingerlin <[email protected]> AuthorDate: Fri Jan 19 14:16:05 2024 +0100 typo fix (#36900) (cherry picked from commit 03c2bb56c0e71d5fa49292a27e32438a5e0e4567) --- docs/apache-airflow/core-concepts/objectstorage.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/core-concepts/objectstorage.rst b/docs/apache-airflow/core-concepts/objectstorage.rst index f5b113a861..0ec3bf8a34 100644 --- a/docs/apache-airflow/core-concepts/objectstorage.rst +++ b/docs/apache-airflow/core-concepts/objectstorage.rst @@ -33,7 +33,7 @@ of object-name => data. To enable remote access, operations on objects are usual Airflow provides a generic abstraction on top of object stores, like s3, gcs, and azure blob storage. This abstraction allows you to use a variety of object storage systems in your DAGs without having to -change you code to deal with every different object storage system. In addition, it allows you to use +change your code to deal with every different object storage system. In addition, it allows you to use most of the standard Python modules, like ``shutil``, that can work with file-like objects. Support for a particular object storage system depends on the providers you have installed. For
