This is an automated email from the ASF dual-hosted git repository.
jedcunningham 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 d8b8202d1f Docs typo and capitalization fixes (#33176)
d8b8202d1f is described below
commit d8b8202d1f3d23d75f8cd362178fae359bd641f0
Author: Laura Zdanski <[email protected]>
AuthorDate: Mon Aug 7 11:09:18 2023 -0500
Docs typo and capitalization fixes (#33176)
---
.../administration-and-deployment/dag-serialization.rst | 2 +-
docs/apache-airflow/howto/add-dag-tags.rst | 4 ++--
docs/apache-airflow/ui.rst | 2 +-
docs/docker-stack/build.rst | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git
a/docs/apache-airflow/administration-and-deployment/dag-serialization.rst
b/docs/apache-airflow/administration-and-deployment/dag-serialization.rst
index 385db66123..ef5f05f4cc 100644
--- a/docs/apache-airflow/administration-and-deployment/dag-serialization.rst
+++ b/docs/apache-airflow/administration-and-deployment/dag-serialization.rst
@@ -102,7 +102,7 @@ Limitations
.. note::
You need Airflow >= 1.10.10 for completely stateless Webserver.
- Airflow 1.10.7 to 1.10.9 needed access to Dag files in some cases.
+ Airflow 1.10.7 to 1.10.9 needed access to DAG files in some cases.
More Information:
https://airflow.apache.org/docs/1.10.9/dag-serialization.html#limitations
Using a different JSON Library
diff --git a/docs/apache-airflow/howto/add-dag-tags.rst
b/docs/apache-airflow/howto/add-dag-tags.rst
index 5b7db76229..9abbc6d995 100644
--- a/docs/apache-airflow/howto/add-dag-tags.rst
+++ b/docs/apache-airflow/howto/add-dag-tags.rst
@@ -28,7 +28,7 @@ The filter is saved in a cookie and can be reset by the reset
button.
For example:
-In your Dag file, pass a list of tags you want to add to DAG object:
+In your DAG file, pass a list of tags you want to add to the DAG object:
.. code-block:: python
@@ -39,6 +39,6 @@ In your Dag file, pass a list of tags you want to add to DAG
object:
.. image:: ../img/add-dag-tags.png
-Tags are registered as part of dag parsing.
+Tags are registered as part of DAG parsing.
In case of stale tags, you can purge old data with the Airflow CLI command
``airflow db clean``.
See :ref:`db clean usage<cli-db-clean>` for more details.
diff --git a/docs/apache-airflow/ui.rst b/docs/apache-airflow/ui.rst
index 6b7e2967a1..87f20d7a88 100644
--- a/docs/apache-airflow/ui.rst
+++ b/docs/apache-airflow/ui.rst
@@ -28,7 +28,7 @@ DAGs View
.........
List of the DAGs in your environment, and a set of shortcuts to useful pages.
You can see exactly how many tasks succeeded, failed, or are currently
-running at a glance. To hide completed tasks set
show_recent_stats_for_completed_runs = False
+running at a glance. To hide completed tasks set
``show_recent_stats_for_completed_runs = False``
In order to filter DAGs (e.g by team), you can add tags in each DAG.
The filter is saved in a cookie and can be reset by the reset button.
diff --git a/docs/docker-stack/build.rst b/docs/docker-stack/build.rst
index 4e7a3d03ea..41a52b0c07 100644
--- a/docs/docker-stack/build.rst
+++ b/docs/docker-stack/build.rst
@@ -349,7 +349,7 @@ You should be aware, about a few things:
The DAGs in production image are in ``/opt/airflow/dags`` folder.
* You can build your image without any need for Airflow sources. It is enough
that you place the
- ``Dockerfile`` and any files that are referred to (such as Dag files) in a
separate directory and run
+ ``Dockerfile`` and any files that are referred to (such as DAG files) in a
separate directory and run
a command ``docker build . --pull --tag my-image:my-tag`` (where
``my-image`` is the name you want to name it
and ``my-tag`` is the tag you want to tag the image with.
