You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2022/05/02 10:00:01 UTC

[airflow-site] branch refresh-docs-with-kubernetes-clarification updated (5fd2ee24f -> 326c61e73)

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a change to branch refresh-docs-with-kubernetes-clarification
in repository https://gitbox.apache.org/repos/asf/airflow-site.git


 discard 5fd2ee24f Refresh the documentation with K8S library clarification
     new 326c61e73 Refresh the documentation with K8S library clarification

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (5fd2ee24f)
            \
             N -- N -- N   refs/heads/refresh-docs-with-kubernetes-clarification (326c61e73)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../2.3.0/_api/airflow/exceptions/index.html       |  22 +-
 .../airflow/executors/base_executor/index.html     |  32 +-
 .../airflow/executors/celery_executor/index.html   |  20 +-
 .../celery_kubernetes_executor/index.html          |   4 +-
 .../airflow/executors/dask_executor/index.html     |   8 +-
 .../airflow/executors/debug_executor/index.html    |  10 +-
 .../executors/kubernetes_executor/index.html       |  18 +-
 .../airflow/executors/local_executor/index.html    |  38 +-
 .../executors/local_kubernetes_executor/index.html |   6 +-
 .../executors/sequential_executor/index.html       |  10 +-
 .../2.3.0/_api/airflow/hooks/base/index.html       |  18 +-
 .../2.3.0/_api/airflow/hooks/dbapi/index.html      |  54 +-
 .../2.3.0/_api/airflow/hooks/filesystem/index.html |   2 +-
 .../2.3.0/_api/airflow/hooks/subprocess/index.html |   8 +-
 .../airflow/models/abstractoperator/index.html     |  16 +-
 .../_api/airflow/models/baseoperator/index.html    | 128 ++--
 .../_api/airflow/models/connection/index.html      |  22 +-
 .../2.3.0/_api/airflow/models/crypto/index.html    |   4 +-
 .../2.3.0/_api/airflow/models/dag/index.html       | 280 +++----
 .../2.3.0/_api/airflow/models/dagbag/index.html    |  12 +-
 .../2.3.0/_api/airflow/models/dagcode/index.html   |  18 +-
 .../2.3.0/_api/airflow/models/dagpickle/index.html |   2 +-
 .../2.3.0/_api/airflow/models/dagrun/index.html    |  56 +-
 .../_api/airflow/models/mappedoperator/index.html  |  12 +-
 .../2.3.0/_api/airflow/models/param/index.html     |  38 +-
 .../2.3.0/_api/airflow/models/pool/index.html      |  24 +-
 .../airflow/models/renderedtifields/index.html     |  20 +-
 .../_api/airflow/models/sensorinstance/index.html  |  12 +-
 .../_api/airflow/models/serialized_dag/index.html  |  36 +-
 .../2.3.0/_api/airflow/models/skipmixin/index.html |   8 +-
 .../_api/airflow/models/taskinstance/index.html    | 138 ++--
 .../2.3.0/_api/airflow/models/tasklog/index.html   |   2 +-
 .../2.3.0/_api/airflow/models/taskmap/index.html   |   2 +-
 .../2.3.0/_api/airflow/models/taskmixin/index.html |  26 +-
 .../_api/airflow/models/taskreschedule/index.html  |  14 +-
 .../2.3.0/_api/airflow/models/trigger/index.html   |   4 +-
 .../2.3.0/_api/airflow/models/variable/index.html  |  42 +-
 .../2.3.0/_api/airflow/models/xcom/index.html      |  10 +-
 .../2.3.0/_api/airflow/models/xcom_arg/index.html  |  10 +-
 .../2.3.0/_api/airflow/operators/bash/index.html   |  22 +-
 .../2.3.0/_api/airflow/operators/branch/index.html |   2 +-
 .../_api/airflow/operators/datetime/index.html     |  14 +-
 .../2.3.0/_api/airflow/operators/email/index.html  |  18 +-
 .../airflow/operators/generic_transfer/index.html  |  12 +-
 .../_api/airflow/operators/latest_only/index.html  |   2 +-
 .../2.3.0/_api/airflow/operators/python/index.html |  64 +-
 .../2.3.0/_api/airflow/operators/smooth/index.html |   2 +-
 .../2.3.0/_api/airflow/operators/sql/index.html    |  60 +-
 .../2.3.0/_api/airflow/operators/subdag/index.html |  14 +-
 .../airflow/operators/trigger_dagrun/index.html    |  22 +-
 .../_api/airflow/operators/weekday/index.html      |  12 +-
 .../_api/airflow/secrets/base_secrets/index.html   |  22 +-
 .../secrets/environment_variables/index.html       |   4 +-
 .../airflow/secrets/local_filesystem/index.html    |  14 +-
 .../_api/airflow/secrets/metastore/index.html      |   6 +-
 .../2.3.0/_api/airflow/sensors/base/index.html     |  26 +-
 .../2.3.0/_api/airflow/sensors/bash/index.html     |   8 +-
 .../_api/airflow/sensors/date_time/index.html      |   4 +-
 .../_api/airflow/sensors/external_task/index.html  |  36 +-
 .../_api/airflow/sensors/filesystem/index.html     |   6 +-
 .../2.3.0/_api/airflow/sensors/python/index.html   |  10 +-
 .../_api/airflow/sensors/smart_sensor/index.html   |  18 +-
 .../2.3.0/_api/airflow/sensors/sql/index.html      |  16 +-
 .../_api/airflow/sensors/time_delta/index.html     |   6 +-
 .../_api/airflow/sensors/time_sensor/index.html    |   4 +-
 .../2.3.0/_api/airflow/sensors/weekday/index.html  |  10 +-
 .../2.3.0/_api/airflow/timetables/base/index.html  |  18 +-
 .../_api/airflow/timetables/events/index.html      |  18 +-
 .../_api/airflow/timetables/interval/index.html    |   6 +-
 .../_api/airflow/timetables/simple/index.html      |  16 +-
 .../apache-airflow/2.3.0/_static/_gen/js/docs.js   |   2 +-
 .../apache-airflow/2.3.0/best-practices.html       |  50 +-
 .../2.3.0/cli-and-env-variables-ref.html           | 274 +++----
 .../2.3.0/concepts/cluster-policies.html           |   8 +-
 .../apache-airflow/2.3.0/concepts/connections.html |   4 +-
 .../apache-airflow/2.3.0/concepts/dags.html        |  66 +-
 .../apache-airflow/2.3.0/concepts/deferring.html   |  34 +-
 .../2.3.0/concepts/dynamic-task-mapping.html       |  16 +-
 .../apache-airflow/2.3.0/concepts/index.html       |   2 +-
 .../apache-airflow/2.3.0/concepts/operators.html   |  14 +-
 .../apache-airflow/2.3.0/concepts/overview.html    |  18 +-
 .../apache-airflow/2.3.0/concepts/params.html      |  14 +-
 .../apache-airflow/2.3.0/concepts/pools.html       |   2 +-
 .../2.3.0/concepts/priority-weight.html            |   2 +-
 .../apache-airflow/2.3.0/concepts/scheduler.html   |  70 +-
 .../2.3.0/concepts/smart-sensors.html              |   6 +-
 .../apache-airflow/2.3.0/concepts/taskflow.html    |   4 +-
 .../apache-airflow/2.3.0/concepts/tasks.html       |  24 +-
 .../apache-airflow/2.3.0/concepts/timetable.html   |   8 +-
 .../apache-airflow/2.3.0/concepts/variables.html   |   2 +-
 .../apache-airflow/2.3.0/concepts/xcoms.html       |   8 +-
 .../apache-airflow/2.3.0/configurations-ref.html   |  82 +--
 docs-archive/apache-airflow/2.3.0/dag-run.html     |  24 +-
 .../apache-airflow/2.3.0/dag-serialization.html    |   2 +-
 .../2.3.0/deprecated-rest-api-ref.html             |  10 +-
 .../apache-airflow/2.3.0/executor/celery.html      |  26 +-
 .../2.3.0/executor/celery_kubernetes.html          |   2 +-
 .../apache-airflow/2.3.0/executor/index.html       |   6 +-
 .../apache-airflow/2.3.0/executor/kubernetes.html  |  12 +-
 .../2.3.0/executor/local_kubernetes.html           |   2 +-
 .../apache-airflow/2.3.0/executor/sequential.html  |   2 +-
 .../apache-airflow/2.3.0/extra-packages-ref.html   |   4 +-
 docs-archive/apache-airflow/2.3.0/faq.html         |  72 +-
 .../apache-airflow/2.3.0/howto/connection.html     |  24 +-
 .../2.3.0/howto/create-custom-decorator.html       |  10 +-
 .../2.3.0/howto/custom-operator.html               |  10 +-
 .../2.3.0/howto/define_extra_link.html             |   2 +-
 .../2.3.0/howto/dynamic-dag-generation.html        |   8 +-
 .../apache-airflow/2.3.0/howto/email-config.html   |  10 +-
 docs-archive/apache-airflow/2.3.0/howto/index.html |   2 +-
 .../apache-airflow/2.3.0/howto/operator/bash.html  |   6 +-
 .../2.3.0/howto/operator/external_task_sensor.html |   2 +-
 .../2.3.0/howto/operator/python.html               |  12 +-
 .../apache-airflow/2.3.0/howto/set-config.html     |   8 +-
 .../2.3.0/howto/set-up-database.html               |  16 +-
 .../apache-airflow/2.3.0/howto/timetable.html      |  46 +-
 .../2.3.0/howto/use-test-config.html               |   4 +-
 .../2.3.0/installation/dependencies.html           |  14 +-
 .../2.3.0/installation/installing-from-pypi.html   |  18 +-
 .../installation/installing-from-sources.html      |   8 +-
 .../2.3.0/installation/prerequisites.html          |   4 +-
 .../installation/setting-up-the-database.html      |   4 +-
 .../2.3.0/installation/supported-versions.html     |   6 +-
 .../2.3.0/installation/upgrading.html              |   6 +-
 docs-archive/apache-airflow/2.3.0/lineage.html     |   4 +-
 .../2.3.0/logging-monitoring/check-health.html     |   2 +-
 .../2.3.0/logging-monitoring/metrics.html          |   4 +-
 .../logging-monitoring/tracking-user-activity.html |   2 +-
 .../apache-airflow/2.3.0/migrations-ref.html       |   6 +-
 .../apache-airflow/2.3.0/modules_management.html   |  20 +-
 docs-archive/apache-airflow/2.3.0/objects.inv      | Bin 27449 -> 27431 bytes
 .../2.3.0/operators-and-hooks-ref.html             |   2 +-
 docs-archive/apache-airflow/2.3.0/plugins.html     |  12 +-
 .../apache-airflow/2.3.0/privacy_notice.html       |   2 +-
 .../2.3.0/production-deployment.html               |  10 +-
 docs-archive/apache-airflow/2.3.0/project.html     |  12 +-
 .../apache-airflow/2.3.0/python-api-ref.html       |   6 +-
 .../apache-airflow/2.3.0/release-process.html      |  22 +-
 .../apache-airflow/2.3.0/release_notes.html        | 813 +++++++++++----------
 docs-archive/apache-airflow/2.3.0/searchindex.js   |   2 +-
 .../2.3.0/security/access-control.html             |   2 +-
 .../apache-airflow/2.3.0/security/index.html       |   2 +-
 .../security/secrets/mask-sensitive-values.html    |  10 +-
 .../apache-airflow/2.3.0/security/webserver.html   |  12 +-
 .../apache-airflow/2.3.0/security/workload.html    |   4 +-
 .../apache-airflow/2.3.0/start/docker.html         |  20 +-
 docs-archive/apache-airflow/2.3.0/start/local.html |  12 +-
 .../apache-airflow/2.3.0/templates-ref.html        |  66 +-
 docs-archive/apache-airflow/2.3.0/timezone.html    |   6 +-
 docs-archive/apache-airflow/2.3.0/tutorial.html    |  72 +-
 .../2.3.0/tutorial_taskflow_api.html               |  36 +-
 docs-archive/apache-airflow/2.3.0/ui.html          |  10 +-
 .../2.3.0/upgrading-from-1-10/index.html           |  22 +-
 .../2.3.0/upgrading-from-1-10/upgrade-check.html   |   4 +-
 docs-archive/apache-airflow/2.3.0/usage-cli.html   |  12 +-
 docs-archive/docker-stack/build-arg-ref.html       |  18 +-
 docs-archive/docker-stack/build.html               |  78 +-
 docs-archive/docker-stack/changelog.html           |   4 +-
 docs-archive/docker-stack/entrypoint.html          |  38 +-
 docs-archive/docker-stack/index.html               |  10 +-
 docs-archive/docker-stack/searchindex.js           |   2 +-
 161 files changed, 2067 insertions(+), 2062 deletions(-)


[airflow-site] 01/01: Refresh the documentation with K8S library clarification

Posted by po...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch refresh-docs-with-kubernetes-clarification
in repository https://gitbox.apache.org/repos/asf/airflow-site.git

commit 326c61e73bfc5ea655404241fe214d95c908fb81
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Mon May 2 11:46:13 2022 +0200

    Refresh the documentation with K8S library clarification
---
 .../2.3.0/_api/airflow/exceptions/index.html       |  22 +-
 .../airflow/executors/base_executor/index.html     |  32 +-
 .../airflow/executors/celery_executor/index.html   |  20 +-
 .../celery_kubernetes_executor/index.html          |   4 +-
 .../airflow/executors/dask_executor/index.html     |   8 +-
 .../airflow/executors/debug_executor/index.html    |  10 +-
 .../executors/kubernetes_executor/index.html       |  18 +-
 .../airflow/executors/local_executor/index.html    |  38 +-
 .../executors/local_kubernetes_executor/index.html |   6 +-
 .../executors/sequential_executor/index.html       |  10 +-
 .../2.3.0/_api/airflow/hooks/base/index.html       |  18 +-
 .../2.3.0/_api/airflow/hooks/dbapi/index.html      |  54 +-
 .../2.3.0/_api/airflow/hooks/filesystem/index.html |   2 +-
 .../2.3.0/_api/airflow/hooks/subprocess/index.html |   8 +-
 .../airflow/models/abstractoperator/index.html     |  16 +-
 .../_api/airflow/models/baseoperator/index.html    | 128 ++--
 .../_api/airflow/models/connection/index.html      |  22 +-
 .../2.3.0/_api/airflow/models/crypto/index.html    |   4 +-
 .../2.3.0/_api/airflow/models/dag/index.html       | 280 +++----
 .../2.3.0/_api/airflow/models/dagbag/index.html    |  12 +-
 .../2.3.0/_api/airflow/models/dagcode/index.html   |  18 +-
 .../2.3.0/_api/airflow/models/dagpickle/index.html |   2 +-
 .../2.3.0/_api/airflow/models/dagrun/index.html    |  56 +-
 .../_api/airflow/models/mappedoperator/index.html  |  12 +-
 .../2.3.0/_api/airflow/models/param/index.html     |  38 +-
 .../2.3.0/_api/airflow/models/pool/index.html      |  24 +-
 .../airflow/models/renderedtifields/index.html     |  20 +-
 .../_api/airflow/models/sensorinstance/index.html  |  12 +-
 .../_api/airflow/models/serialized_dag/index.html  |  36 +-
 .../2.3.0/_api/airflow/models/skipmixin/index.html |   8 +-
 .../_api/airflow/models/taskinstance/index.html    | 138 ++--
 .../2.3.0/_api/airflow/models/tasklog/index.html   |   2 +-
 .../2.3.0/_api/airflow/models/taskmap/index.html   |   2 +-
 .../2.3.0/_api/airflow/models/taskmixin/index.html |  26 +-
 .../_api/airflow/models/taskreschedule/index.html  |  14 +-
 .../2.3.0/_api/airflow/models/trigger/index.html   |   4 +-
 .../2.3.0/_api/airflow/models/variable/index.html  |  42 +-
 .../2.3.0/_api/airflow/models/xcom/index.html      |  10 +-
 .../2.3.0/_api/airflow/models/xcom_arg/index.html  |  10 +-
 .../2.3.0/_api/airflow/operators/bash/index.html   |  22 +-
 .../2.3.0/_api/airflow/operators/branch/index.html |   2 +-
 .../_api/airflow/operators/datetime/index.html     |  14 +-
 .../2.3.0/_api/airflow/operators/email/index.html  |  18 +-
 .../airflow/operators/generic_transfer/index.html  |  12 +-
 .../_api/airflow/operators/latest_only/index.html  |   2 +-
 .../2.3.0/_api/airflow/operators/python/index.html |  64 +-
 .../2.3.0/_api/airflow/operators/smooth/index.html |   2 +-
 .../2.3.0/_api/airflow/operators/sql/index.html    |  60 +-
 .../2.3.0/_api/airflow/operators/subdag/index.html |  14 +-
 .../airflow/operators/trigger_dagrun/index.html    |  22 +-
 .../_api/airflow/operators/weekday/index.html      |  12 +-
 .../_api/airflow/secrets/base_secrets/index.html   |  22 +-
 .../secrets/environment_variables/index.html       |   4 +-
 .../airflow/secrets/local_filesystem/index.html    |  14 +-
 .../_api/airflow/secrets/metastore/index.html      |   6 +-
 .../2.3.0/_api/airflow/sensors/base/index.html     |  26 +-
 .../2.3.0/_api/airflow/sensors/bash/index.html     |   8 +-
 .../_api/airflow/sensors/date_time/index.html      |   4 +-
 .../_api/airflow/sensors/external_task/index.html  |  36 +-
 .../_api/airflow/sensors/filesystem/index.html     |   6 +-
 .../2.3.0/_api/airflow/sensors/python/index.html   |  10 +-
 .../_api/airflow/sensors/smart_sensor/index.html   |  18 +-
 .../2.3.0/_api/airflow/sensors/sql/index.html      |  16 +-
 .../_api/airflow/sensors/time_delta/index.html     |   6 +-
 .../_api/airflow/sensors/time_sensor/index.html    |   4 +-
 .../2.3.0/_api/airflow/sensors/weekday/index.html  |  10 +-
 .../2.3.0/_api/airflow/timetables/base/index.html  |  18 +-
 .../_api/airflow/timetables/events/index.html      |  18 +-
 .../_api/airflow/timetables/interval/index.html    |   6 +-
 .../_api/airflow/timetables/simple/index.html      |  16 +-
 .../apache-airflow/2.3.0/_static/_gen/js/docs.js   |   2 +-
 .../apache-airflow/2.3.0/best-practices.html       |  50 +-
 .../2.3.0/cli-and-env-variables-ref.html           | 274 +++----
 .../2.3.0/concepts/cluster-policies.html           |   8 +-
 .../apache-airflow/2.3.0/concepts/connections.html |   4 +-
 .../apache-airflow/2.3.0/concepts/dags.html        |  66 +-
 .../apache-airflow/2.3.0/concepts/deferring.html   |  34 +-
 .../2.3.0/concepts/dynamic-task-mapping.html       |  16 +-
 .../apache-airflow/2.3.0/concepts/index.html       |   2 +-
 .../apache-airflow/2.3.0/concepts/operators.html   |  14 +-
 .../apache-airflow/2.3.0/concepts/overview.html    |  18 +-
 .../apache-airflow/2.3.0/concepts/params.html      |  14 +-
 .../apache-airflow/2.3.0/concepts/pools.html       |   2 +-
 .../2.3.0/concepts/priority-weight.html            |   2 +-
 .../apache-airflow/2.3.0/concepts/scheduler.html   |  70 +-
 .../2.3.0/concepts/smart-sensors.html              |   6 +-
 .../apache-airflow/2.3.0/concepts/taskflow.html    |   4 +-
 .../apache-airflow/2.3.0/concepts/tasks.html       |  24 +-
 .../apache-airflow/2.3.0/concepts/timetable.html   |   8 +-
 .../apache-airflow/2.3.0/concepts/variables.html   |   2 +-
 .../apache-airflow/2.3.0/concepts/xcoms.html       |   8 +-
 .../apache-airflow/2.3.0/configurations-ref.html   |  82 +--
 docs-archive/apache-airflow/2.3.0/dag-run.html     |  24 +-
 .../apache-airflow/2.3.0/dag-serialization.html    |   2 +-
 .../2.3.0/deprecated-rest-api-ref.html             |  10 +-
 .../apache-airflow/2.3.0/executor/celery.html      |  26 +-
 .../2.3.0/executor/celery_kubernetes.html          |   2 +-
 .../apache-airflow/2.3.0/executor/index.html       |   6 +-
 .../apache-airflow/2.3.0/executor/kubernetes.html  |  12 +-
 .../2.3.0/executor/local_kubernetes.html           |   2 +-
 .../apache-airflow/2.3.0/executor/sequential.html  |   2 +-
 .../apache-airflow/2.3.0/extra-packages-ref.html   |   4 +-
 docs-archive/apache-airflow/2.3.0/faq.html         |  72 +-
 .../apache-airflow/2.3.0/howto/connection.html     |  24 +-
 .../2.3.0/howto/create-custom-decorator.html       |  10 +-
 .../2.3.0/howto/custom-operator.html               |  10 +-
 .../2.3.0/howto/define_extra_link.html             |   2 +-
 .../2.3.0/howto/dynamic-dag-generation.html        |   8 +-
 .../apache-airflow/2.3.0/howto/email-config.html   |  10 +-
 docs-archive/apache-airflow/2.3.0/howto/index.html |   2 +-
 .../apache-airflow/2.3.0/howto/operator/bash.html  |   6 +-
 .../2.3.0/howto/operator/external_task_sensor.html |   2 +-
 .../2.3.0/howto/operator/python.html               |  12 +-
 .../apache-airflow/2.3.0/howto/set-config.html     |   8 +-
 .../2.3.0/howto/set-up-database.html               |  16 +-
 .../apache-airflow/2.3.0/howto/timetable.html      |  46 +-
 .../2.3.0/howto/use-test-config.html               |   4 +-
 .../2.3.0/installation/dependencies.html           |  14 +-
 .../2.3.0/installation/installing-from-pypi.html   |  18 +-
 .../installation/installing-from-sources.html      |   8 +-
 .../2.3.0/installation/prerequisites.html          |   4 +-
 .../installation/setting-up-the-database.html      |   4 +-
 .../2.3.0/installation/supported-versions.html     |   6 +-
 .../2.3.0/installation/upgrading.html              |   6 +-
 docs-archive/apache-airflow/2.3.0/lineage.html     |   4 +-
 .../2.3.0/logging-monitoring/check-health.html     |   2 +-
 .../2.3.0/logging-monitoring/metrics.html          |   4 +-
 .../logging-monitoring/tracking-user-activity.html |   2 +-
 .../apache-airflow/2.3.0/migrations-ref.html       |   6 +-
 .../apache-airflow/2.3.0/modules_management.html   |  20 +-
 docs-archive/apache-airflow/2.3.0/objects.inv      | Bin 27449 -> 27431 bytes
 .../2.3.0/operators-and-hooks-ref.html             |   2 +-
 docs-archive/apache-airflow/2.3.0/plugins.html     |  12 +-
 .../apache-airflow/2.3.0/privacy_notice.html       |   2 +-
 .../2.3.0/production-deployment.html               |  10 +-
 docs-archive/apache-airflow/2.3.0/project.html     |  12 +-
 .../apache-airflow/2.3.0/python-api-ref.html       |   6 +-
 .../apache-airflow/2.3.0/release-process.html      |  22 +-
 .../apache-airflow/2.3.0/release_notes.html        | 813 +++++++++++----------
 docs-archive/apache-airflow/2.3.0/searchindex.js   |   2 +-
 .../2.3.0/security/access-control.html             |   2 +-
 .../apache-airflow/2.3.0/security/index.html       |   2 +-
 .../security/secrets/mask-sensitive-values.html    |  10 +-
 .../apache-airflow/2.3.0/security/webserver.html   |  12 +-
 .../apache-airflow/2.3.0/security/workload.html    |   4 +-
 .../apache-airflow/2.3.0/start/docker.html         |  20 +-
 docs-archive/apache-airflow/2.3.0/start/local.html |  12 +-
 .../apache-airflow/2.3.0/templates-ref.html        |  66 +-
 docs-archive/apache-airflow/2.3.0/timezone.html    |   6 +-
 docs-archive/apache-airflow/2.3.0/tutorial.html    |  72 +-
 .../2.3.0/tutorial_taskflow_api.html               |  36 +-
 docs-archive/apache-airflow/2.3.0/ui.html          |  10 +-
 .../2.3.0/upgrading-from-1-10/index.html           |  22 +-
 .../2.3.0/upgrading-from-1-10/upgrade-check.html   |   4 +-
 docs-archive/apache-airflow/2.3.0/usage-cli.html   |  12 +-
 docs-archive/docker-stack/_static/_gen/js/docs.js  |   2 +-
 docs-archive/docker-stack/build.html               |   2 +-
 docs-archive/docker-stack/entrypoint.html          |   2 +-
 docs-archive/docker-stack/index.html               |   6 +-
 159 files changed, 1998 insertions(+), 1993 deletions(-)

diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/exceptions/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/exceptions/index.html
index 129d4c2c8..3bb192e75 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/exceptions/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/exceptions/index.html
@@ -850,7 +850,7 @@
 <dt class="sig sig-object py" id="airflow.exceptions.AirflowException">
 <em class="property"><span class="pre">exception</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.exceptions.</span></span><span class="sig-name descname"><span class="pre">AirflowException</span></span><a class="reference internal" href="../../../_modules/airflow/exceptions.html#AirflowException"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.exceptions.AirflowException" tit [...]
 <dd><p>Bases: <a class="reference external" href="https://docs.python.org/3/library/exceptions.html#Exception" title="(in Python v3.10)"><code class="xref py py-obj docutils literal notranslate"><span class="pre">Exception</span></code></a></p>
-<p>Base class for all Airflow’s errors.</p>
+<p>Base class for all Airflow's errors.</p>
 <p>Each custom exception should be derived from this class.</p>
 <dl class="py attribute">
 <dt class="sig sig-object py" id="airflow.exceptions.AirflowException.status_code">
@@ -904,7 +904,7 @@
 <p>Raise when the task should be re-scheduled at a later time.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>reschedule_date</strong> – The date when the task should be rescheduled</p>
+<dd class="field-odd"><p><strong>reschedule_date</strong> -- The date when the task should be rescheduled</p>
 </dd>
 </dl>
 </dd></dl>
@@ -970,7 +970,7 @@
 <dt class="sig sig-object py" id="airflow.exceptions.XComForMappingNotPushed">
 <em class="property"><span class="pre">exception</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.exceptions.</span></span><span class="sig-name descname"><span class="pre">XComForMappingNotPushed</span></span><a class="reference internal" href="../../../_modules/airflow/exceptions.html#XComForMappingNotPushed"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.exceptions.XComFor [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.exceptions.AirflowException" title="airflow.exceptions.AirflowException"><code class="xref py py-obj docutils literal notranslate"><span class="pre">AirflowException</span></code></a></p>
-<p>Raise when a mapped downstream’s dependency fails to push XCom for task mapping.</p>
+<p>Raise when a mapped downstream's dependency fails to push XCom for task mapping.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.exceptions.XComForMappingNotPushed.__str__">
 <span class="sig-name descname"><span class="pre">__str__</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../_modules/airflow/exceptions.html#XComForMappingNotPushed.__str__"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.exceptions.XComForMappingNotPushed.__str__" title="Permali [...]
@@ -985,7 +985,7 @@
 <dt class="sig sig-object py" id="airflow.exceptions.UnmappableXComTypePushed">
 <em class="property"><span class="pre">exception</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.exceptions.</span></span><span class="sig-name descname"><span class="pre">UnmappableXComTypePushed</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">value</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../_modules/airflow/exceptions.html#Unmappa [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.exceptions.AirflowException" title="airflow.exceptions.AirflowException"><code class="xref py py-obj docutils literal notranslate"><span class="pre">AirflowException</span></code></a></p>
-<p>Raise when an unmappable type is pushed as a mapped downstream’s dependency.</p>
+<p>Raise when an unmappable type is pushed as a mapped downstream's dependency.</p>
 <dl class="field-list simple">
 </dl>
 <dl class="py method">
@@ -1002,7 +1002,7 @@
 <dt class="sig sig-object py" id="airflow.exceptions.UnmappableXComLengthPushed">
 <em class="property"><span class="pre">exception</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.exceptions.</span></span><span class="sig-name descname"><span class="pre">UnmappableXComLengthPushed</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">value</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">max_length</span></span></em><span class="sig-paren">)</s [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.exceptions.AirflowException" title="airflow.exceptions.AirflowException"><code class="xref py py-obj docutils literal notranslate"><span class="pre">AirflowException</span></code></a></p>
-<p>Raise when the pushed value is too large to map as a downstream’s dependency.</p>
+<p>Raise when the pushed value is too large to map as a downstream's dependency.</p>
 <dl class="field-list simple">
 </dl>
 <dl class="py method">
@@ -1026,7 +1026,7 @@
 <dt class="sig sig-object py" id="airflow.exceptions.AirflowDagDuplicatedIdException">
 <em class="property"><span class="pre">exception</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.exceptions.</span></span><span class="sig-name descname"><span class="pre">AirflowDagDuplicatedIdException</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">dag_id</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">incoming</span></span></em>, <em class="sig-param"> [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.exceptions.AirflowException" title="airflow.exceptions.AirflowException"><code class="xref py py-obj docutils literal notranslate"><span class="pre">AirflowException</span></code></a></p>
-<p>Raise when a DAG’s ID is already used by another DAG.</p>
+<p>Raise when a DAG's ID is already used by another DAG.</p>
 <dl class="field-list simple">
 </dl>
 <dl class="py method">
@@ -1159,8 +1159,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>message</strong> – The human-readable description of the exception</p></li>
-<li><p><strong>ti_status</strong> – The information about all task statuses</p></li>
+<li><p><strong>message</strong> -- The human-readable description of the exception</p></li>
+<li><p><strong>ti_status</strong> -- The information about all task statuses</p></li>
 </ul>
 </dd>
 </dl>
@@ -1197,9 +1197,9 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>msg</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The human-readable description of the exception</p></li>
-<li><p><strong>file_path</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – A processed file that contains errors</p></li>
-<li><p><strong>parse_errors</strong> (<em>List</em><em>[</em><a class="reference internal" href="#airflow.exceptions.FileSyntaxError" title="airflow.exceptions.FileSyntaxError"><em>FileSyntaxError</em></a><em>]</em>) – File syntax errors</p></li>
+<li><p><strong>msg</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The human-readable description of the exception</p></li>
+<li><p><strong>file_path</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- A processed file that contains errors</p></li>
+<li><p><strong>parse_errors</strong> (<em>List</em><em>[</em><a class="reference internal" href="#airflow.exceptions.FileSyntaxError" title="airflow.exceptions.FileSyntaxError"><em>FileSyntaxError</em></a><em>]</em>) -- File syntax errors</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/base_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/base_executor/index.html
index b509e26ff..3e0c1824b 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/base_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/base_executor/index.html
@@ -883,7 +883,7 @@
 like Celery, Kubernetes, Local, Sequential and the likes.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>parallelism</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – how many jobs should run at one time. Set to
+<dd class="field-odd"><p><strong>parallelism</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- how many jobs should run at one time. Set to
 <code class="docutils literal notranslate"><span class="pre">0</span></code> for infinity</p>
 </dd>
 </dl>
@@ -931,7 +931,7 @@ like Celery, Kubernetes, Local, Sequential and the likes.</p>
 <dd><p>Checks if a task is either queued or running in this executor.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>task_instance</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) – TaskInstance</p>
+<dd class="field-odd"><p><strong>task_instance</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) -- TaskInstance</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>True if the task is known to this executor</p>
@@ -979,7 +979,7 @@ Executors should override this to perform gather statuses.</p>
 <dd><p>Initiates async execution of the queued tasks, up to the number of available slots.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>open_slots</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – Number of open slots</p>
+<dd class="field-odd"><p><strong>open_slots</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- Number of open slots</p>
 </dd>
 </dl>
 </dd></dl>
@@ -991,9 +991,9 @@ Executors should override this to perform gather statuses.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>info</strong> – Executor information for the task instance</p></li>
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
-<li><p><strong>state</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – State to set for the task.</p></li>
+<li><p><strong>info</strong> -- Executor information for the task instance</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
+<li><p><strong>state</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- State to set for the task.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1006,8 +1006,8 @@ Executors should override this to perform gather statuses.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>info</strong> – Executor information for the task instance</p></li>
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
+<li><p><strong>info</strong> -- Executor information for the task instance</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
 </ul>
 </dd>
 </dl>
@@ -1020,8 +1020,8 @@ Executors should override this to perform gather statuses.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>info</strong> – Executor information for the task instance</p></li>
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
+<li><p><strong>info</strong> -- Executor information for the task instance</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
 </ul>
 </dd>
 </dl>
@@ -1035,7 +1035,7 @@ it will only return and flush events for the given dag_ids. Otherwise
 it returns and flushes all events.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>dag_ids</strong> – the dag_ids to return events for; returns all if given <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p>
+<dd class="field-odd"><p><strong>dag_ids</strong> -- the dag_ids to return events for; returns all if given <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>a dict of events</p>
@@ -1053,10 +1053,10 @@ it returns and flushes all events.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
-<li><p><strong>command</strong> (<em>CommandType</em>) – Command to run</p></li>
-<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of the queue</p></li>
-<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) – Configuration passed to the executor.</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
+<li><p><strong>command</strong> (<em>CommandType</em>) -- Command to run</p></li>
+<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of the queue</p></li>
+<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) -- Configuration passed to the executor.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1121,7 +1121,7 @@ re-scheduling)</p>
 <p>Provides a default implementation which sends the callback to the <cite>callback_sink</cite> object.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>request</strong> (<em>airflow.callbacks.callback_requests.CallbackRequest</em>) – Callback request to be executed.</p>
+<dd class="field-odd"><p><strong>request</strong> (<em>airflow.callbacks.callback_requests.CallbackRequest</em>) -- Callback request to be executed.</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_executor/index.html
index cc897d11e..8aa3c8837 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_executor/index.html
@@ -915,8 +915,8 @@ airflow celery worker</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>exception</strong> (<a class="reference external" href="https://docs.python.org/3/library/exceptions.html#Exception" title="(in Python v3.10)"><em>Exception</em></a>) – The exception to wrap</p></li>
-<li><p><strong>exception_traceback</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The stacktrace to wrap</p></li>
+<li><p><strong>exception</strong> (<a class="reference external" href="https://docs.python.org/3/library/exceptions.html#Exception" title="(in Python v3.10)"><em>Exception</em></a>) -- The exception to wrap</p></li>
+<li><p><strong>exception_traceback</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The stacktrace to wrap</p></li>
 </ul>
 </dd>
 </dl>
@@ -938,10 +938,10 @@ airflow celery worker</p>
 <dl class="py function">
 <dt class="sig sig-object py" id="airflow.executors.celery_executor.on_celery_import_modules">
 <span class="sig-prename descclassname"><span class="pre">airflow.executors.celery_executor.</span></span><span class="sig-name descname"><span class="pre">on_celery_import_modules</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span><span class="n"><span class="pre">args</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">**</span></span><span class="n"><span class="pre">kwargs</span></span></em><span [...]
-<dd><p>Preload some “expensive” airflow modules so that every task process doesn’t have to import it again and
+<dd><p>Preload some &quot;expensive&quot; airflow modules so that every task process doesn't have to import it again and
 again.</p>
 <p>Loading these for each task adds 0.3-0.5s <em>per task</em> before the task can run. For long running tasks this
-doesn’t matter, but for short tasks this starts to be a noticeable impact.</p>
+doesn't matter, but for short tasks this starts to be a noticeable impact.</p>
 </dd></dl>
 
 <dl class="py class">
@@ -998,9 +998,9 @@ Executors should override this to perform gather statuses.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>info</strong> – Executor information for the task instance</p></li>
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
-<li><p><strong>state</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – State to set for the task.</p></li>
+<li><p><strong>info</strong> -- Executor information for the task instance</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
+<li><p><strong>state</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- State to set for the task.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1055,8 +1055,8 @@ re-scheduling)</p>
 global so that it can be called by subprocesses in the pool.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>async_result</strong> (<a class="reference external" href="https://docs.celeryq.dev/en/stable//reference/celery.result.html#celery.result.AsyncResult" title="(in Celery v5.2)"><em>celery.result.AsyncResult</em></a>) – a tuple of the Celery task key and the async Celery object used
-to fetch the task’s state</p>
+<dd class="field-odd"><p><strong>async_result</strong> (<a class="reference external" href="https://docs.celeryq.dev/en/stable//reference/celery.result.html#celery.result.AsyncResult" title="(in Celery v5.2)"><em>celery.result.AsyncResult</em></a>) -- a tuple of the Celery task key and the async Celery object used
+to fetch the task's state</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>a tuple of the Celery task key and the Celery state and the celery info
@@ -1074,7 +1074,7 @@ of the task</p>
 <dd><p>Bases: <code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.utils.log.logging_mixin.LoggingMixin</span></code></p>
 <p>Gets status for many Celery tasks using the best method available</p>
 <p>If BaseKeyValueStoreBackend is used as result backend, the mget method is used.
-If DatabaseBackend is used as result backend, the SELECT …WHERE task_id IN (…) query is used
+If DatabaseBackend is used as result backend, the SELECT ...WHERE task_id IN (...) query is used
 Otherwise, multiprocessing.Pool will be used. Each task status will be downloaded individually.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.executors.celery_executor.BulkStateFetcher.get_many">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_kubernetes_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_kubernetes_executor/index.html
index 4b19905c6..dfa63d7c4 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_kubernetes_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/celery_kubernetes_executor/index.html
@@ -861,7 +861,7 @@ of executors we implement as property so we can have custom setter.</p>
 <dd><p>Checks if a task is either queued or running in either celery or kubernetes executor.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>task_instance</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) – TaskInstance</p>
+<dd class="field-odd"><p><strong>task_instance</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) -- TaskInstance</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>True if the task is known to this executor</p>
@@ -886,7 +886,7 @@ of executors we implement as property so we can have custom setter.</p>
 <dd><p>Returns and flush the event buffer from celery and kubernetes executor</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>dag_ids</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – dag_ids to return events for, if None returns all</p>
+<dd class="field-odd"><p><strong>dag_ids</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- dag_ids to return events for, if None returns all</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>a dict of events</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/dask_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/dask_executor/index.html
index ca06907c3..5b3569ec5 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/dask_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/dask_executor/index.html
@@ -781,10 +781,10 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
-<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) – Command to run</p></li>
-<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of the queue</p></li>
-<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) – Configuration passed to the executor.</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
+<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) -- Command to run</p></li>
+<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of the queue</p></li>
+<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) -- Configuration passed to the executor.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/debug_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/debug_executor/index.html
index 377b22c47..5e215eb0e 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/debug_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/debug_executor/index.html
@@ -771,7 +771,7 @@
 <dd><p>Bases: <a class="reference internal" href="../base_executor/index.html#airflow.executors.base_executor.BaseExecutor" title="airflow.executors.base_executor.BaseExecutor"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.executors.base_executor.BaseExecutor</span></code></a></p>
 <p>This executor is meant for debugging purposes. It can be used with SQLite.</p>
 <p>It executes one task instance at time. Additionally to support working
-with sensors, all sensors <code class="docutils literal notranslate"><span class="pre">mode</span></code> will be automatically set to “reschedule”.</p>
+with sensors, all sensors <code class="docutils literal notranslate"><span class="pre">mode</span></code> will be automatically set to &quot;reschedule&quot;.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.executors.debug_executor.DebugExecutor.execute_async">
 <span class="sig-name descname"><span class="pre">execute_async</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">*</span></span><span class="n"><span class="pre">args</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">**</span></span><span class="n"><span class="pre">kwargs</span></span></em><span class="sig-paren">)</span><a class= [...]
@@ -804,7 +804,7 @@ Executors should override this to perform gather statuses.</p>
 add task instance to tasks_to_run queue.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>open_slots</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – Number of open slots</p>
+<dd class="field-odd"><p><strong>open_slots</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- Number of open slots</p>
 </dd>
 </dl>
 </dd></dl>
@@ -833,9 +833,9 @@ to UPSTREAM_FAILED marking them as not executed.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>info</strong> – Executor information for the task instance</p></li>
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
-<li><p><strong>state</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – State to set for the task.</p></li>
+<li><p><strong>info</strong> -- Executor information for the task instance</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
+<li><p><strong>state</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- State to set for the task.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/kubernetes_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/kubernetes_executor/index.html
index 459301aaf..30c4292c9 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/kubernetes_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/kubernetes_executor/index.html
@@ -941,7 +941,7 @@
 <span class="sig-name descname"><span class="pre">run_next</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">next_job</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/executors/kubernetes_executor.html#AirflowKubernetesScheduler.run_next"><span class="viewcode-link"><span class="pre">[source]< [...]
 <dd><p>The run_next command will check the task_queue for any un-run jobs.
 It will then create a unique job-id, launch that job in the cluster,
-and store relevant info in the current_jobs map so we can track the job’s
+and store relevant info in the current_jobs map so we can track the job's
 status</p>
 <dl class="field-list simple">
 </dl>
@@ -993,12 +993,12 @@ be sent back to the scheduler.</p>
 <dt class="sig sig-object py" id="airflow.executors.kubernetes_executor.get_base_pod_from_template">
 <span class="sig-prename descclassname"><span class="pre">airflow.executors.kubernetes_executor.</span></span><span class="sig-name descname"><span class="pre">get_base_pod_from_template</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">pod_template_file</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">kube_config</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../ [...]
 <dd><p>Reads either the pod_template_file set in the executor_config or the base pod_template_file
-set in the airflow.cfg to craft a “base pod” that will be used by the KubernetesExecutor</p>
+set in the airflow.cfg to craft a &quot;base pod&quot; that will be used by the KubernetesExecutor</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>pod_template_file</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – absolute path to a pod_template_file.yaml or None</p></li>
-<li><p><strong>kube_config</strong> (<em>Any</em>) – The KubeConfig class generated by airflow that contains all kube metadata</p></li>
+<li><p><strong>pod_template_file</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- absolute path to a pod_template_file.yaml or None</p></li>
+<li><p><strong>kube_config</strong> (<em>Any</em>) -- The KubeConfig class generated by airflow that contains all kube metadata</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1023,13 +1023,13 @@ set in the airflow.cfg to craft a “base pod” that will be used by the Kubern
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.executors.kubernetes_executor.KubernetesExecutor.clear_not_launched_queued_tasks">
 <span class="sig-name descname"><span class="pre">clear_not_launched_queued_tasks</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/ [...]
-<dd><p>Tasks can end up in a “Queued” state through either the executor being
+<dd><p>Tasks can end up in a &quot;Queued&quot; state through either the executor being
 abruptly shut down (leaving a non-empty task_queue on this executor)
 or when a rescheduled/deferred operator comes back up for execution
 (with the same try_number) before the pod of its previous incarnation
 has been fully removed (we think).</p>
 <p>This method checks each of those tasks to see if the corresponding pod
-is around, and if not, and there’s no matching entry in our own
+is around, and if not, and there's no matching entry in our own
 task_queue, marks it for re-execution.</p>
 <dl class="field-list simple">
 </dl>
@@ -1082,9 +1082,9 @@ re-scheduling)</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>kube_client</strong> (<em>kubernetes.client.CoreV1Api</em>) – kubernetes client for speaking to kube API</p></li>
-<li><p><strong>pod</strong> (<em>kubernetes.client.models.V1Pod</em>) – V1Pod spec that we will patch with new label</p></li>
-<li><p><strong>pod_ids</strong> (<em>Dict</em><em>[</em><a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a><em>, </em><em>kubernetes.client.models.V1Pod</em><em>]</em>) – pod_ids we expect to patch.</p></li>
+<li><p><strong>kube_client</strong> (<em>kubernetes.client.CoreV1Api</em>) -- kubernetes client for speaking to kube API</p></li>
+<li><p><strong>pod</strong> (<em>kubernetes.client.models.V1Pod</em>) -- V1Pod spec that we will patch with new label</p></li>
+<li><p><strong>pod_ids</strong> (<em>Dict</em><em>[</em><a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a><em>, </em><em>kubernetes.client.models.V1Pod</em><em>]</em>) -- pod_ids we expect to patch.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_executor/index.html
index f33d13826..9191bffd1 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_executor/index.html
@@ -857,7 +857,7 @@
 command and puts the result into a result queue when done, terminating execution.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>result_queue</strong> (<em>Queue</em><em>[</em><em>TaskInstanceStateType</em><em>]</em>) – the queue to store result state</p>
+<dd class="field-odd"><p><strong>result_queue</strong> (<em>Queue</em><em>[</em><em>TaskInstanceStateType</em><em>]</em>) -- the queue to store result state</p>
 </dd>
 </dl>
 <dl class="py method">
@@ -873,8 +873,8 @@ command and puts the result into a result queue when done, terminating execution
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – the key to identify the task instance</p></li>
-<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) – the command to execute</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- the key to identify the task instance</p></li>
+<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) -- the command to execute</p></li>
 </ul>
 </dd>
 </dl>
@@ -896,9 +896,9 @@ command and puts the result into a result queue when done, terminating execution
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>result_queue</strong> (<em>Queue</em><em>[</em><em>TaskInstanceStateType</em><em>]</em>) – queue where results of the tasks are put.</p></li>
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – key identifying task instance</p></li>
-<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) – Command to execute</p></li>
+<li><p><strong>result_queue</strong> (<em>Queue</em><em>[</em><em>TaskInstanceStateType</em><em>]</em>) -- queue where results of the tasks are put.</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- key identifying task instance</p></li>
+<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) -- Command to execute</p></li>
 </ul>
 </dd>
 </dl>
@@ -922,8 +922,8 @@ It will terminate execution once the poison token is found.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_queue</strong> (<em>Queue</em><em>[</em><em>ExecutorWorkType</em><em>]</em>) – queue from which worker reads tasks</p></li>
-<li><p><strong>result_queue</strong> (<em>Queue</em><em>[</em><em>TaskInstanceStateType</em><em>]</em>) – queue where worker puts results after finishing tasks</p></li>
+<li><p><strong>task_queue</strong> (<em>Queue</em><em>[</em><em>ExecutorWorkType</em><em>]</em>) -- queue from which worker reads tasks</p></li>
+<li><p><strong>result_queue</strong> (<em>Queue</em><em>[</em><em>TaskInstanceStateType</em><em>]</em>) -- queue where worker puts results after finishing tasks</p></li>
 </ul>
 </dd>
 </dl>
@@ -946,7 +946,7 @@ It uses the multiprocessing Python library and queues to parallelize the executi
 of tasks.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>parallelism</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – how many parallel processes are run in the executor</p>
+<dd class="field-odd"><p><strong>parallelism</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- how many parallel processes are run in the executor</p>
 </dd>
 </dl>
 <dl class="py class">
@@ -956,7 +956,7 @@ of tasks.</p>
 per each command to execute.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>executor</strong> (<a class="reference internal" href="#airflow.executors.local_executor.LocalExecutor" title="airflow.executors.local_executor.LocalExecutor"><em>LocalExecutor</em></a>) – the executor instance to implement.</p>
+<dd class="field-odd"><p><strong>executor</strong> (<a class="reference internal" href="#airflow.executors.local_executor.LocalExecutor" title="airflow.executors.local_executor.LocalExecutor"><em>LocalExecutor</em></a>) -- the executor instance to implement.</p>
 </dd>
 </dl>
 <dl class="py method">
@@ -974,10 +974,10 @@ per each command to execute.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – the key to identify the task instance</p></li>
-<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) – the command to execute</p></li>
-<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Name of the queue</p></li>
-<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) – configuration for the executor</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- the key to identify the task instance</p></li>
+<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) -- the command to execute</p></li>
+<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Name of the queue</p></li>
+<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) -- configuration for the executor</p></li>
 </ul>
 </dd>
 </dl>
@@ -1010,7 +1010,7 @@ all done.</p>
 coordinate work distribution.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>executor</strong> (<a class="reference internal" href="#airflow.executors.local_executor.LocalExecutor" title="airflow.executors.local_executor.LocalExecutor"><em>LocalExecutor</em></a>) – the executor instance to implement.</p>
+<dd class="field-odd"><p><strong>executor</strong> (<a class="reference internal" href="#airflow.executors.local_executor.LocalExecutor" title="airflow.executors.local_executor.LocalExecutor"><em>LocalExecutor</em></a>) -- the executor instance to implement.</p>
 </dd>
 </dl>
 <dl class="py method">
@@ -1028,10 +1028,10 @@ coordinate work distribution.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – the key to identify the task instance</p></li>
-<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) – the command to execute</p></li>
-<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of the queue</p></li>
-<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) – configuration for the executor</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- the key to identify the task instance</p></li>
+<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) -- the command to execute</p></li>
+<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of the queue</p></li>
+<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) -- configuration for the executor</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_kubernetes_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_kubernetes_executor/index.html
index 07c1be524..4f9c2041a 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_kubernetes_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/local_kubernetes_executor/index.html
@@ -783,7 +783,7 @@
 <dd><p>Bases: <code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.utils.log.logging_mixin.LoggingMixin</span></code></p>
 <p>LocalKubernetesExecutor consists of LocalExecutor and KubernetesExecutor.
 It chooses the executor to use based on the queue defined on the task.
-When the task’s queue is the value of <code class="docutils literal notranslate"><span class="pre">kubernetes_queue</span></code> in section <code class="docutils literal notranslate"><span class="pre">[local_kubernetes_executor]</span></code>
+When the task's queue is the value of <code class="docutils literal notranslate"><span class="pre">kubernetes_queue</span></code> in section <code class="docutils literal notranslate"><span class="pre">[local_kubernetes_executor]</span></code>
 of the configuration (default value: <cite>kubernetes</cite>), KubernetesExecutor is selected to run the task,
 otherwise, LocalExecutor is used.</p>
 <dl class="field-list simple">
@@ -860,7 +860,7 @@ of executors we implement as property so we can have custom setter.</p>
 <dd><p>Checks if a task is either queued or running in either local or kubernetes executor.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>task_instance</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) – TaskInstance</p>
+<dd class="field-odd"><p><strong>task_instance</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) -- TaskInstance</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>True if the task is known to this executor</p>
@@ -885,7 +885,7 @@ of executors we implement as property so we can have custom setter.</p>
 <dd><p>Returns and flush the event buffer from local and kubernetes executor</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>dag_ids</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – dag_ids to return events for, if None returns all</p>
+<dd class="field-odd"><p><strong>dag_ids</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- dag_ids to return events for, if None returns all</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>a dict of events</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/sequential_executor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/sequential_executor/index.html
index d963eda92..91ad38732 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/sequential_executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/executors/sequential_executor/index.html
@@ -765,7 +765,7 @@
 <dd><p>Bases: <a class="reference internal" href="../base_executor/index.html#airflow.executors.base_executor.BaseExecutor" title="airflow.executors.base_executor.BaseExecutor"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.executors.base_executor.BaseExecutor</span></code></a></p>
 <p>This executor will only run one task instance at a time, can be used
 for debugging. It is also the only executor that can be used with sqlite
-since sqlite doesn’t support multiple connections.</p>
+since sqlite doesn't support multiple connections.</p>
 <p>Since we want airflow to work out of the box, it defaults to this
 SequentialExecutor alongside sqlite as you first install it.</p>
 <dl class="py method">
@@ -775,10 +775,10 @@ SequentialExecutor alongside sqlite as you first install it.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – Unique key for the task instance</p></li>
-<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) – Command to run</p></li>
-<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of the queue</p></li>
-<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) – Configuration passed to the executor.</p></li>
+<li><p><strong>key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- Unique key for the task instance</p></li>
+<li><p><strong>command</strong> (<em>airflow.executors.base_executor.CommandType</em>) -- Command to run</p></li>
+<li><p><strong>queue</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of the queue</p></li>
+<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Any</em><em>]</em>) -- Configuration passed to the executor.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/base/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/base/index.html
index 451ad1d29..37ff205d7 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/base/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/base/index.html
@@ -843,7 +843,7 @@ with them.</p>
 <dd><p>Get all connections as an iterable, given the connection id.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>array of connections</p>
@@ -860,7 +860,7 @@ with them.</p>
 <dd><p>Get connection, given connection id.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>connection</p>
@@ -877,7 +877,7 @@ with them.</p>
 <dd><p>Returns default hook for this connection id.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>default hook for this connection</p>
@@ -918,17 +918,17 @@ with them.</p>
 <dd><p>Bases: <code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.typing_compat.Protocol</span></code></p>
 <p>Interface that providers <em>can</em> implement to be discovered by ProvidersManager.</p>
 <p>It is not used by any of the Hooks, but simply methods and class fields described here are
-implemented by those Hooks. Each method is optional – only implement the ones you need.</p>
+implemented by those Hooks. Each method is optional -- only implement the ones you need.</p>
 <p>The conn_name_attr, default_conn_name, conn_type should be implemented by those
 Hooks that want to be automatically mapped from the connection_type -&gt; Hook when get_hook method
 is called with connection_type.</p>
 <p>Additionally hook_name should be set when you want the hook to have a custom name in the UI selection
 Name. If not specified, conn_name will be used.</p>
-<p>The “get_ui_field_behaviour” and “get_connection_form_widgets” are optional - override them if you want
+<p>The &quot;get_ui_field_behaviour&quot; and &quot;get_connection_form_widgets&quot; are optional - override them if you want
 to customize the Connection Form screen. You can add extra widgets to parse your extra fields via the
 get_connection_form_widgets method as well as hide or relabel the fields or pre-fill
 them with placeholders via get_ui_field_behaviour method.</p>
-<p>Note that the “get_ui_field_behaviour” and “get_connection_form_widgets” need to be set by each class
+<p>Note that the &quot;get_ui_field_behaviour&quot; and &quot;get_connection_form_widgets&quot; need to be set by each class
 in the class hierarchy in order to apply widget customizations.</p>
 <p>For example, even if you want to use the fields from your parent class, you must explicitly
 have a method on <em>your</em> class:</p>
@@ -937,7 +937,7 @@ have a method on <em>your</em> class:</p>
     <span class="k">return</span> <span class="nb">super</span><span class="p">()</span><span class="o">.</span><span class="n">get_ui_field_behaviour</span><span class="p">()</span>
 </pre></div>
 </div>
-<p>You also need to add the Hook class name to list ‘hook_class_names’ in provider.yaml in case you
+<p>You also need to add the Hook class name to list 'hook_class_names' in provider.yaml in case you
 build an internal provider or to return it in dictionary returned by provider_info entrypoint in the
 package you prepare.</p>
 <p>You can see some examples in airflow/providers/jdbc/hooks/jdbc.py.</p>
@@ -969,7 +969,7 @@ package you prepare.</p>
 added by the base class, so there is no need to implement this method. It might
 actually result in warning in the logs if you try to add widgets that have already
 been added by the base class.</p>
-<p>Note that values of Dict should be of wtforms.Field type. It’s not added here
+<p>Note that values of Dict should be of wtforms.Field type. It's not added here
 for the efficiency of imports.</p>
 <dl class="field-list simple">
 </dl>
@@ -979,7 +979,7 @@ for the efficiency of imports.</p>
 <dt class="sig sig-object py" id="airflow.hooks.base.DiscoverableHook.get_ui_field_behaviour">
 <em class="property"><span class="pre">static</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">get_ui_field_behaviour</span></span><span class="sig-paren">(</span><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/hooks/base.html#DiscoverableHook.get_ui_field_behaviour"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.hooks.base.DiscoverableHook.ge [...]
 <dd><p>Returns dictionary describing customizations to implement in javascript handling the
-connection form. Should be compliant with airflow/customized_form_field_behaviours.schema.json’</p>
+connection form. Should be compliant with airflow/customized_form_field_behaviours.schema.json'</p>
 <p>If you change conn_type in a derived class, you should also
 implement this method and return field customizations appropriate to your Hook. This
 is because the child hook will have usually different conn_type and the customizations
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/dbapi/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/dbapi/index.html
index f88935562..e68d56542 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/dbapi/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/dbapi/index.html
@@ -830,10 +830,10 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>host</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The database host to connect to.</p></li>
-<li><p><strong>port</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – The database port to connect to.</p></li>
-<li><p><strong>username</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The database username used for the authentication.</p></li>
-<li><p><strong>schema</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The database schema to connect to.</p></li>
+<li><p><strong>host</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The database host to connect to.</p></li>
+<li><p><strong>port</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- The database port to connect to.</p></li>
+<li><p><strong>username</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The database username used for the authentication.</p></li>
+<li><p><strong>schema</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The database schema to connect to.</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -854,7 +854,7 @@
 <p>Abstract base class for sql hooks.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>schema</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Optional DB schema that overrides the schema specified in the connection. Make sure that
+<dd class="field-odd"><p><strong>schema</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Optional DB schema that overrides the schema specified in the connection. Make sure that
 if you change the schema parameter value in the constructor of the derived Hook, such change
 should be done before calling the <code class="docutils literal notranslate"><span class="pre">DBApiHook.__init__()</span></code>.</p>
 </dd>
@@ -905,7 +905,7 @@ should be done before calling the <code class="docutils literal notranslate"><sp
 <dd><p>Get an sqlalchemy_engine object.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>engine_kwargs</strong> – Kwargs used in <a class="reference external" href="https://docs.sqlalchemy.org/en/latest/core/engines.html#sqlalchemy.create_engine" title="(in SQLAlchemy v1.4)"><code class="xref py py-func docutils literal notranslate"><span class="pre">create_engine()</span></code></a>.</p>
+<dd class="field-odd"><p><strong>engine_kwargs</strong> -- Kwargs used in <a class="reference external" href="https://docs.sqlalchemy.org/en/latest/core/engines.html#sqlalchemy.create_engine" title="(in SQLAlchemy v1.4)"><code class="xref py py-func docutils literal notranslate"><span class="pre">create_engine()</span></code></a>.</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>the created engine.</p>
@@ -920,10 +920,10 @@ should be done before calling the <code class="docutils literal notranslate"><sp
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> – the sql statement to be executed (str) or a list of
+<li><p><strong>sql</strong> -- the sql statement to be executed (str) or a list of
 sql statements to execute</p></li>
-<li><p><strong>parameters</strong> – The parameters to render the SQL query with.</p></li>
-<li><p><strong>kwargs</strong> – (optional) passed into pandas.io.sql.read_sql method</p></li>
+<li><p><strong>parameters</strong> -- The parameters to render the SQL query with.</p></li>
+<li><p><strong>kwargs</strong> -- (optional) passed into pandas.io.sql.read_sql method</p></li>
 </ul>
 </dd>
 </dl>
@@ -936,9 +936,9 @@ sql statements to execute</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> – the sql statement to be executed (str) or a list of
+<li><p><strong>sql</strong> -- the sql statement to be executed (str) or a list of
 sql statements to execute</p></li>
-<li><p><strong>parameters</strong> – The parameters to render the SQL query with.</p></li>
+<li><p><strong>parameters</strong> -- The parameters to render the SQL query with.</p></li>
 </ul>
 </dd>
 </dl>
@@ -951,9 +951,9 @@ sql statements to execute</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> – the sql statement to be executed (str) or a list of
+<li><p><strong>sql</strong> -- the sql statement to be executed (str) or a list of
 sql statements to execute</p></li>
-<li><p><strong>parameters</strong> – The parameters to render the SQL query with.</p></li>
+<li><p><strong>parameters</strong> -- The parameters to render the SQL query with.</p></li>
 </ul>
 </dd>
 </dl>
@@ -968,12 +968,12 @@ sequentially</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> – the sql statement to be executed (str) or a list of
+<li><p><strong>sql</strong> -- the sql statement to be executed (str) or a list of
 sql statements to execute</p></li>
-<li><p><strong>autocommit</strong> – What to set the connection’s autocommit setting to
+<li><p><strong>autocommit</strong> -- What to set the connection's autocommit setting to
 before executing the query.</p></li>
-<li><p><strong>parameters</strong> – The parameters to render the SQL query with.</p></li>
-<li><p><strong>handler</strong> – The result handler which is called with the result of each statement.</p></li>
+<li><p><strong>parameters</strong> -- The parameters to render the SQL query with.</p></li>
+<li><p><strong>handler</strong> -- The result handler which is called with the result of each statement.</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -997,7 +997,7 @@ Return False if conn.autocommit is not set or set to False or conn
 does not support autocommit.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn</strong> – Connection to get autocommit setting from.</p>
+<dd class="field-odd"><p><strong>conn</strong> -- Connection to get autocommit setting from.</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>connection autocommit setting.</p>
@@ -1022,12 +1022,12 @@ a new transaction is created every commit_every rows</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>table</strong> – Name of the target table</p></li>
-<li><p><strong>rows</strong> – The rows to insert into the table</p></li>
-<li><p><strong>target_fields</strong> – The names of the columns to fill in the table</p></li>
-<li><p><strong>commit_every</strong> – The maximum number of rows to insert in one
+<li><p><strong>table</strong> -- Name of the target table</p></li>
+<li><p><strong>rows</strong> -- The rows to insert into the table</p></li>
+<li><p><strong>target_fields</strong> -- The names of the columns to fill in the table</p></li>
+<li><p><strong>commit_every</strong> -- The maximum number of rows to insert in one
 transaction. Set to 0 to insert all rows in one transaction.</p></li>
-<li><p><strong>replace</strong> – Whether to replace instead of insert</p></li>
+<li><p><strong>replace</strong> -- Whether to replace instead of insert</p></li>
 </ul>
 </dd>
 </dl>
@@ -1040,8 +1040,8 @@ transaction. Set to 0 to insert all rows in one transaction.</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>table</strong> – The name of the source table</p></li>
-<li><p><strong>tmp_file</strong> – The path of the target file</p></li>
+<li><p><strong>table</strong> -- The name of the source table</p></li>
+<li><p><strong>tmp_file</strong> -- The path of the target file</p></li>
 </ul>
 </dd>
 </dl>
@@ -1054,8 +1054,8 @@ transaction. Set to 0 to insert all rows in one transaction.</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>table</strong> – The name of the target table</p></li>
-<li><p><strong>tmp_file</strong> – The path of the file to load into the table</p></li>
+<li><p><strong>table</strong> -- The name of the target table</p></li>
+<li><p><strong>tmp_file</strong> -- The path of the file to load into the table</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/filesystem/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/filesystem/index.html
index fc5088391..c16754ec4 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/filesystem/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/filesystem/index.html
@@ -785,7 +785,7 @@
 Connection Id: fs_test
 Connection Type: File (path)
 Host, Schema, Login, Password, Port: empty
-Extra: {“path”: “/tmp”}</p>
+Extra: {&quot;path&quot;: &quot;/tmp&quot;}</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.hooks.filesystem.FSHook.get_conn">
 <span class="sig-name descname"><span class="pre">get_conn</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/hooks/filesystem.html#FSHook.get_conn"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.hooks.filesystem.FSHook.get_conn" title="Permalink to this defin [...]
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/subprocess/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/subprocess/index.html
index 3ad7a65c9..4c19dd0c2 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/subprocess/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/hooks/subprocess/index.html
@@ -812,14 +812,14 @@ If <code class="docutils literal notranslate"><span class="pre">env</span></code
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>command</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the command to run</p></li>
-<li><p><strong>env</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – Optional dict containing environment variables to be made available to the shell
+<li><p><strong>command</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the command to run</p></li>
+<li><p><strong>env</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- Optional dict containing environment variables to be made available to the shell
 environment in which <code class="docutils literal notranslate"><span class="pre">command</span></code> will be executed.  If omitted, <code class="docutils literal notranslate"><span class="pre">os.environ</span></code> will be used.
 Note, that in case you have Sentry configured, original variables from the environment
 will also be passed to the subprocess with <code class="docutils literal notranslate"><span class="pre">SUBPROCESS_</span></code> prefix. See
 <a class="reference internal" href="../../../../logging-monitoring/errors.html"><span class="doc">Error Tracking</span></a> for details.</p></li>
-<li><p><strong>output_encoding</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – encoding to use for decoding stdout</p></li>
-<li><p><strong>cwd</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Working directory to run the command in.
+<li><p><strong>output_encoding</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- encoding to use for decoding stdout</p></li>
+<li><p><strong>cwd</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Working directory to run the command in.
 If None (default), the command is run in a temporary directory.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/abstractoperator/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/abstractoperator/index.html
index 1c527690f..7652e92a2 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/abstractoperator/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/abstractoperator/index.html
@@ -958,7 +958,7 @@
 <dd><p>Bases: <code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.utils.log.logging_mixin.LoggingMixin</span></code>, <a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DAGNode" title="airflow.models.taskmixin.DAGNode"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.taskmixin.DAGNode</span></code></a></p>
 <p>Common implementation for operators, including unmapped and mapped.</p>
 <p>This base class is more about sharing implementations, not defining a common
-interface. Unfortunately it’s difficult to use this as the common base class
+interface. Unfortunately it's difficult to use this as the common base class
 for typing due to BaseOperator carrying too much historical baggage.</p>
 <p>The union type <code class="docutils literal notranslate"><span class="pre">from</span> <span class="pre">airflow.models.operator</span> <span class="pre">import</span> <span class="pre">Operator</span></code> is easier
 to use for typing purposes.</p>
@@ -1138,13 +1138,13 @@ template is rendered, it should override this method to do so.</p>
 <dd><p>For an operator, gets the URLs that the <code class="docutils literal notranslate"><span class="pre">extra_links</span></code> entry points to.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Raises</dt>
-<dd class="field-odd"><p><a class="reference external" href="https://docs.python.org/3/library/exceptions.html#ValueError" title="(in Python v3.10)"><strong>ValueError</strong></a> – The error message of a ValueError will be passed on through to
+<dd class="field-odd"><p><a class="reference external" href="https://docs.python.org/3/library/exceptions.html#ValueError" title="(in Python v3.10)"><strong>ValueError</strong></a> -- The error message of a ValueError will be passed on through to
 the fronted to show up as a tooltip on the disabled link.</p>
 </dd>
 <dt class="field-even">Parameters</dt>
 <dd class="field-even"><ul class="simple">
-<li><p><strong>ti</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) – The TaskInstance for the URL being searched for.</p></li>
-<li><p><strong>link_name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The name of the link we’re looking for the URL for. Should be
+<li><p><strong>ti</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) -- The TaskInstance for the URL being searched for.</p></li>
+<li><p><strong>link_name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The name of the link we're looking for the URL for. Should be
 one of the options specified in <code class="docutils literal notranslate"><span class="pre">extra_links</span></code>.</p></li>
 </ul>
 </dd>
@@ -1173,12 +1173,12 @@ in the collection will be templated recursively.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>content</strong> (<em>Any</em>) – Content to template. Only strings can be templated (may
+<li><p><strong>content</strong> (<em>Any</em>) -- Content to template. Only strings can be templated (may
 be inside a collection).</p></li>
-<li><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Dict with values to apply on templated content</p></li>
-<li><p><strong>jinja_env</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment" title="(in Jinja v2.11.x)"><em>jinja2.Environment</em></a><em>]</em>) – Jinja environment. Can be provided to avoid
+<li><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Dict with values to apply on templated content</p></li>
+<li><p><strong>jinja_env</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment" title="(in Jinja v2.11.x)"><em>jinja2.Environment</em></a><em>]</em>) -- Jinja environment. Can be provided to avoid
 re-creating Jinja environments during recursion.</p></li>
-<li><p><strong>seen_oids</strong> (<em>Optional</em><em>[</em><em>Set</em><em>]</em>) – template fields already rendered (to avoid
+<li><p><strong>seen_oids</strong> (<em>Optional</em><em>[</em><em>Set</em><em>]</em>) -- template fields already rendered (to avoid
 <em>RecursionError</em> on circular dependencies)</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/baseoperator/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/baseoperator/index.html
index 726c4e067..5ce7e2854 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/baseoperator/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/baseoperator/index.html
@@ -1093,7 +1093,7 @@
 <p>Abstract base class for all operators. Since operators create objects that
 become nodes in the dag, BaseOperator contains many recursive methods for
 dag crawling behavior. To derive this class, you are expected to override
-the constructor as well as the ‘execute’ method.</p>
+the constructor as well as the 'execute' method.</p>
 <p>Operators derived from this class should perform or trigger certain tasks
 synchronously (wait for completion). Example of operators could be an
 operator that runs a Pig job (PigOperator), a sensor operator that
@@ -1101,54 +1101,54 @@ waits for a partition to land in Hive (HiveSensorOperator), or one that
 moves data from Hive to MySQL (Hive2MySqlOperator). Instances of these
 operators (tasks) target specific operations, running specific scripts,
 functions or data transfers.</p>
-<p>This class is abstract and shouldn’t be instantiated. Instantiating a
+<p>This class is abstract and shouldn't be instantiated. Instantiating a
 class derived from this one results in the creation of a task object,
 which ultimately becomes a node in DAG objects. Task dependencies should
 be set by using the set_upstream and/or set_downstream methods.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – a unique, meaningful id for the task</p></li>
-<li><p><strong>owner</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the owner of the task. Using a meaningful description
+<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- a unique, meaningful id for the task</p></li>
+<li><p><strong>owner</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the owner of the task. Using a meaningful description
 (e.g. user/person/team/role name) to clarify ownership is recommended.</p></li>
-<li><p><strong>email</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) – the ‘to’ email address(es) used in email alerts. This can be a
+<li><p><strong>email</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) -- the 'to' email address(es) used in email alerts. This can be a
 single email or multiple ones. Multiple addresses can be specified as a
 comma or semi-colon separated string or by passing a list of strings.</p></li>
-<li><p><strong>email_on_retry</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Indicates whether email alerts should be sent when a
+<li><p><strong>email_on_retry</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Indicates whether email alerts should be sent when a
 task is retried</p></li>
-<li><p><strong>email_on_failure</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Indicates whether email alerts should be sent when
+<li><p><strong>email_on_failure</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Indicates whether email alerts should be sent when
 a task failed</p></li>
-<li><p><strong>retries</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – the number of retries that should be performed before
+<li><p><strong>retries</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- the number of retries that should be performed before
 failing the task</p></li>
-<li><p><strong>retry_delay</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a><em>]</em>) – delay between retries, can be set as <code class="docutils literal notranslate"><span class="pre">timedelta</ [...]
+<li><p><strong>retry_delay</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a><em>]</em>) -- delay between retries, can be set as <code class="docutils literal notranslate"><span class="pre">timedelta< [...]
 <code class="docutils literal notranslate"><span class="pre">float</span></code> seconds, which will be converted into <code class="docutils literal notranslate"><span class="pre">timedelta</span></code>,
 the default is <code class="docutils literal notranslate"><span class="pre">timedelta(seconds=300)</span></code>.</p></li>
-<li><p><strong>retry_exponential_backoff</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – allow progressively longer waits between
+<li><p><strong>retry_exponential_backoff</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- allow progressively longer waits between
 retries by using exponential backoff algorithm on retry delay (delay
 will be converted into seconds)</p></li>
-<li><p><strong>max_retry_delay</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a><em>]</em><em>]</em>) – maximum delay interval between retries, can be set as
+<li><p><strong>max_retry_delay</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a><em>]</em><em>]</em>) -- maximum delay interval between retries, can be set as
 <code class="docutils literal notranslate"><span class="pre">timedelta</span></code> or <code class="docutils literal notranslate"><span class="pre">float</span></code> seconds, which will be converted into <code class="docutils literal notranslate"><span class="pre">timedelta</span></code>.</p></li>
-<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – The <code class="docutils literal notranslate"><span class="pre">start_date</span></code> for the task, determines
+<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- The <code class="docutils literal notranslate"><span class="pre">start_date</span></code> for the task, determines
 the <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> for the first task instance. The best practice
 is to have the start_date rounded
-to your DAG’s <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>. Daily jobs have their start_date
+to your DAG's <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>. Daily jobs have their start_date
 some day at 00:00:00, hourly jobs have their start_date at 00:00
 of a specific hour. Note that Airflow simply looks at the latest
 <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> and adds the <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> to determine
 the next <code class="docutils literal notranslate"><span class="pre">execution_date</span></code>. It is also very important
-to note that different tasks’ dependencies
+to note that different tasks' dependencies
 need to line up in time. If task A depends on task B and their
-start_date are offset in a way that their execution_date don’t line
-up, A’s dependencies will never be met. If you are looking to delay
+start_date are offset in a way that their execution_date don't line
+up, A's dependencies will never be met. If you are looking to delay
 a task, for example running a daily task at 2AM, look into the
 <code class="docutils literal notranslate"><span class="pre">TimeSensor</span></code> and <code class="docutils literal notranslate"><span class="pre">TimeDeltaSensor</span></code>. We advise against using
 dynamic <code class="docutils literal notranslate"><span class="pre">start_date</span></code> and recommend using fixed ones. Read the
 FAQ entry about start_date for more information.</p></li>
-<li><p><strong>end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – if specified, the scheduler won’t go beyond this date</p></li>
-<li><p><strong>depends_on_past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – when set to true, task instances will run
+<li><p><strong>end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- if specified, the scheduler won't go beyond this date</p></li>
+<li><p><strong>depends_on_past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- when set to true, task instances will run
 sequentially and only if the previous instance has succeeded or has been skipped.
 The task instance for the start_date is allowed to run.</p></li>
-<li><p><strong>wait_for_downstream</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – when set to true, an instance of task
+<li><p><strong>wait_for_downstream</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- when set to true, an instance of task
 X will wait for tasks immediately downstream of the previous instance
 of task X to finish successfully or be skipped before it runs. This is useful if the
 different instances of a task X alter the same asset, and this asset
@@ -1156,12 +1156,12 @@ is used by tasks downstream of task X. Note that depends_on_past
 is forced to True wherever wait_for_downstream is used. Also note that
 only tasks <em>immediately</em> downstream of the previous task instance are waited
 for; the statuses of any tasks further downstream are ignored.</p></li>
-<li><p><strong>dag</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a><em>]</em>) – a reference to the dag the task is attached to (if any)</p></li>
-<li><p><strong>priority_weight</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – priority weight of this task against other task.
+<li><p><strong>dag</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a><em>]</em>) -- a reference to the dag the task is attached to (if any)</p></li>
+<li><p><strong>priority_weight</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- priority weight of this task against other task.
 This allows the executor to trigger higher priority tasks before
 others when things get backed up. Set priority_weight as a higher
 number for more important tasks.</p></li>
-<li><p><strong>weight_rule</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – weighting method used for the effective total
+<li><p><strong>weight_rule</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- weighting method used for the effective total
 priority weight of the task. Options are:
 <code class="docutils literal notranslate"><span class="pre">{</span> <span class="pre">downstream</span> <span class="pre">|</span> <span class="pre">upstream</span> <span class="pre">|</span> <span class="pre">absolute</span> <span class="pre">}</span></code> default is <code class="docutils literal notranslate"><span class="pre">downstream</span></code>
 When set to <code class="docutils literal notranslate"><span class="pre">downstream</span></code> the effective weight of the task is the
@@ -1183,14 +1183,14 @@ Additionally, when set to <code class="docutils literal notranslate"><span class
 significantly speeding up the task creation process as for very large
 DAGs. Options can be set as string or using the constants defined in
 the static class <code class="docutils literal notranslate"><span class="pre">airflow.utils.WeightRule</span></code></p></li>
-<li><p><strong>queue</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – which queue to target when running this job. Not
+<li><p><strong>queue</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- which queue to target when running this job. Not
 all executors implement queue management, the CeleryExecutor
 does support targeting specific queues.</p></li>
-<li><p><strong>pool</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the slot pool this task should run in, slot pools are a
+<li><p><strong>pool</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the slot pool this task should run in, slot pools are a
 way to limit concurrency for certain tasks</p></li>
-<li><p><strong>pool_slots</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – the number of pool slots this task should use (&gt;= 1)
+<li><p><strong>pool_slots</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- the number of pool slots this task should use (&gt;= 1)
 Values less than 1 are not allowed.</p></li>
-<li><p><strong>sla</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) – time by which the job is expected to succeed. Note that
+<li><p><strong>sla</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) -- time by which the job is expected to succeed. Note that
 this represents the <code class="docutils literal notranslate"><span class="pre">timedelta</span></code> after the period is closed. For
 example if you set an SLA of 1 hour, the scheduler would send an email
 soon after 1:00AM on the <code class="docutils literal notranslate"><span class="pre">2016-01-02</span></code> if the <code class="docutils literal notranslate"><span class="pre">2016-01-01</span></code> instance
@@ -1201,42 +1201,42 @@ emails for SLA misses. SLA misses are also recorded in the database
 for future reference. All tasks that share the same SLA time
 get bundled in a single email, sent soon after that time. SLA
 notification are sent once and only once for each task instance.</p></li>
-<li><p><strong>execution_timeout</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) – max time allowed for the execution of
+<li><p><strong>execution_timeout</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) -- max time allowed for the execution of
 this task instance, if it goes beyond it will raise and fail.</p></li>
-<li><p><strong>on_failure_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) – a function to be called when a task instance
+<li><p><strong>on_failure_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) -- a function to be called when a task instance
 of this task fails. a context dictionary is passed as a single
 parameter to this function. Context contains references to related
 objects to the task instance and is documented under the macros
 section of the API.</p></li>
-<li><p><strong>on_execute_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) – much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
+<li><p><strong>on_execute_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) -- much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
 that it is executed right before the task is executed.</p></li>
-<li><p><strong>on_retry_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) – much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
+<li><p><strong>on_retry_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) -- much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
 that it is executed when retries occur.</p></li>
-<li><p><strong>on_success_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) – much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
+<li><p><strong>on_success_callback</strong> (<em>Optional</em><em>[</em><em>airflow.models.abstractoperator.TaskStateChangeCallback</em><em>]</em>) -- much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
 that it is executed when the task succeeds.</p></li>
-<li><p><strong>pre_execute</strong> (<em>Optional</em><em>[</em><em>TaskPreExecuteHook</em><em>]</em>) – <p>a function to be called immediately before task
+<li><p><strong>pre_execute</strong> (<em>Optional</em><em>[</em><em>TaskPreExecuteHook</em><em>]</em>) -- <p>a function to be called immediately before task
 execution, receiving a context dictionary; raising an exception will
 prevent the task from being executed.</p>
 <p>This is an <a class="reference internal" href="../../../../release-process.html#experimental"><span class="std std-ref">experimental feature</span></a>.</p>
 </p></li>
-<li><p><strong>post_execute</strong> (<em>Optional</em><em>[</em><em>TaskPostExecuteHook</em><em>]</em>) – <p>a function to be called immediately after task
+<li><p><strong>post_execute</strong> (<em>Optional</em><em>[</em><em>TaskPostExecuteHook</em><em>]</em>) -- <p>a function to be called immediately after task
 execution, receiving a context dictionary and task result; raising an
 exception will prevent the task from succeeding.</p>
 <p>This is an <a class="reference internal" href="../../../../release-process.html#experimental"><span class="std std-ref">experimental feature</span></a>.</p>
 </p></li>
-<li><p><strong>trigger_rule</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – defines the rule by which dependencies are applied
+<li><p><strong>trigger_rule</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- defines the rule by which dependencies are applied
 for the task to get triggered. Options are:
 <code class="docutils literal notranslate"><span class="pre">{</span> <span class="pre">all_success</span> <span class="pre">|</span> <span class="pre">all_failed</span> <span class="pre">|</span> <span class="pre">all_done</span> <span class="pre">|</span> <span class="pre">all_skipped</span> <span class="pre">|</span> <span class="pre">one_success</span> <span class="pre">|</span>
 <span class="pre">one_failed</span> <span class="pre">|</span> <span class="pre">none_failed</span> <span class="pre">|</span> <span class="pre">none_failed_min_one_success</span> <span class="pre">|</span> <span class="pre">none_skipped</span> <span class="pre">|</span> <span class="pre">always}</span></code>
 default is <code class="docutils literal notranslate"><span class="pre">all_success</span></code>. Options can be set as string or
 using the constants defined in the static class
 <code class="docutils literal notranslate"><span class="pre">airflow.utils.TriggerRule</span></code></p></li>
-<li><p><strong>resources</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – A map of resource parameter names (the argument names of the
+<li><p><strong>resources</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- A map of resource parameter names (the argument names of the
 Resources constructor) to their values.</p></li>
-<li><p><strong>run_as_user</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – unix username to impersonate while running the task</p></li>
-<li><p><strong>max_active_tis_per_dag</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – When set, a task will be able to limit the concurrent
+<li><p><strong>run_as_user</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- unix username to impersonate while running the task</p></li>
+<li><p><strong>max_active_tis_per_dag</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- When set, a task will be able to limit the concurrent
 runs across execution_dates.</p></li>
-<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – <p>Additional task-level configuration parameters that are
+<li><p><strong>executor_config</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- <p>Additional task-level configuration parameters that are
 interpreted by a specific executor. Parameters are namespaced by the name of
 executor.</p>
 <p><strong>Example</strong>: to run this task in a specific docker container through
@@ -1250,19 +1250,19 @@ the KubernetesExecutor</p>
 </pre></div>
 </div>
 </p></li>
-<li><p><strong>do_xcom_push</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – if True, an XCom is pushed containing the Operator’s
+<li><p><strong>do_xcom_push</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- if True, an XCom is pushed containing the Operator's
 result</p></li>
-<li><p><strong>task_group</strong> (<em>Optional</em><em>[</em><em>airflow.utils.task_group.TaskGroup</em><em>]</em>) – The TaskGroup to which the task should belong. This is typically provided when not
+<li><p><strong>task_group</strong> (<em>Optional</em><em>[</em><em>airflow.utils.task_group.TaskGroup</em><em>]</em>) -- The TaskGroup to which the task should belong. This is typically provided when not
 using a TaskGroup as a context manager.</p></li>
-<li><p><strong>doc</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Add documentation or notes to your Task objects that is visible in
+<li><p><strong>doc</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Add documentation or notes to your Task objects that is visible in
 Task Instance details View in the Webserver</p></li>
-<li><p><strong>doc_md</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Add documentation (in Markdown format) or notes to your Task objects
+<li><p><strong>doc_md</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Add documentation (in Markdown format) or notes to your Task objects
 that is visible in Task Instance details View in the Webserver</p></li>
-<li><p><strong>doc_rst</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Add documentation (in RST format) or notes to your Task objects
+<li><p><strong>doc_rst</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Add documentation (in RST format) or notes to your Task objects
 that is visible in Task Instance details View in the Webserver</p></li>
-<li><p><strong>doc_json</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Add documentation (in JSON format) or notes to your Task objects
+<li><p><strong>doc_json</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Add documentation (in JSON format) or notes to your Task objects
 that is visible in Task Instance details View in the Webserver</p></li>
-<li><p><strong>doc_yaml</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Add documentation (in YAML format) or notes to your Task objects
+<li><p><strong>doc_yaml</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Add documentation (in YAML format) or notes to your Task objects
 that is visible in Task Instance details View in the Webserver</p></li>
 </ul>
 </dd>
@@ -1447,7 +1447,7 @@ an attr annotated object it is set as an inlet to this operator</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.baseoperator.BaseOperator.dag">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">dag</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/baseoperator.html#BaseOperator.dag"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlin [...]
-<dd><p>Returns the Operator’s DAG if set, otherwise raises an error</p>
+<dd><p>Returns the Operator's DAG if set, otherwise raises an error</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -1555,8 +1555,8 @@ max_depth on deepcopy operations.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Dict with values to apply on content</p></li>
-<li><p><strong>jinja_env</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment" title="(in Jinja v2.11.x)"><em>jinja2.Environment</em></a><em>]</em>) – Jinja environment</p></li>
+<li><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Dict with values to apply on content</p></li>
+<li><p><strong>jinja_env</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment" title="(in Jinja v2.11.x)"><em>jinja2.Environment</em></a><em>]</em>) -- Jinja environment</p></li>
 </ul>
 </dd>
 </dl>
@@ -1654,11 +1654,11 @@ downstream.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>context</strong> (<em>Any</em>) – Execution Context Dictionary</p></li>
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – A key for the XCom</p></li>
-<li><p><strong>value</strong> (<em>Any</em>) – A value for the XCom. The value is pickled and stored
+<li><p><strong>context</strong> (<em>Any</em>) -- Execution Context Dictionary</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- A key for the XCom</p></li>
+<li><p><strong>value</strong> (<em>Any</em>) -- A value for the XCom. The value is pickled and stored
 in the database.</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – if provided, the XCom will not be visible until
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- if provided, the XCom will not be visible until
 this date. This can be used, for example, to send a message to a
 task on a future date without it being immediately visible.</p></li>
 </ul>
@@ -1680,17 +1680,17 @@ whenever no matches are found.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>context</strong> (<em>Any</em>) – Execution Context Dictionary</p></li>
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – A key for the XCom. If provided, only XComs with matching
-keys will be returned. The default key is ‘return_value’, also
+<li><p><strong>context</strong> (<em>Any</em>) -- Execution Context Dictionary</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- A key for the XCom. If provided, only XComs with matching
+keys will be returned. The default key is 'return_value', also
 available as a constant XCOM_RETURN_KEY. This key is automatically
 given to XComs returned by tasks (as opposed to being pushed
 manually). To remove the filter, pass key=None.</p></li>
-<li><p><strong>task_ids</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) – Only XComs from tasks with matching ids will be
+<li><p><strong>task_ids</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) -- Only XComs from tasks with matching ids will be
 pulled. Can pass None to remove the filter.</p></li>
-<li><p><strong>dag_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – If provided, only pulls XComs from this DAG.
+<li><p><strong>dag_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- If provided, only pulls XComs from this DAG.
 If None (default), the DAG of the calling task is used.</p></li>
-<li><p><strong>include_prior_dates</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) – If False, only XComs from the current
+<li><p><strong>include_prior_dates</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) -- If False, only XComs from the current
 execution_date are returned. If True, XComs from previous dates
 are returned as well.</p></li>
 </ul>
@@ -1727,7 +1727,7 @@ are returned as well.</p></li>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.baseoperator.BaseOperator.defer">
 <span class="sig-name descname"><span class="pre">defer</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">trigger</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">method_name</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">kwar [...]
-<dd><p>Marks this Operator as being “deferred” - that is, suspending its
+<dd><p>Marks this Operator as being &quot;deferred&quot; - that is, suspending its
 execution until the provided trigger fires an event.</p>
 <p>This is achieved by raising a special exception (TaskDeferred)
 which is caught in the main _execute_task wrapper.</p>
@@ -1851,7 +1851,7 @@ lists you must ensure they have the same length.</p>
 </div>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>tasks</strong> (<em>Union</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMixin</em></a><em>, </em><em>Sequence</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmix [...]
+<dd class="field-odd"><p><strong>tasks</strong> (<em>Union</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMixin</em></a><em>, </em><em>Sequence</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmix [...]
 </dd>
 </dl>
 </dd></dl>
@@ -1941,8 +1941,8 @@ lists you must ensure they have the same length.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>from_tasks</strong> (<em>Sequence</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMixin</em></a><em>]</em>) – List of tasks or XComArgs to start from.</p></li>
-<li><p><strong>to_tasks</strong> (<em>Union</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMixin</em></a><em>, </em><em>Sequence</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMi [...]
+<li><p><strong>from_tasks</strong> (<em>Sequence</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMixin</em></a><em>]</em>) -- List of tasks or XComArgs to start from.</p></li>
+<li><p><strong>to_tasks</strong> (<em>Union</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMixin</em></a><em>, </em><em>Sequence</em><em>[</em><a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><em>airflow.models.taskmixin.DependencyMi [...]
 </ul>
 </dd>
 </dl>
@@ -1987,8 +1987,8 @@ supported at runtime but is deprecated.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>operator</strong> (<a class="reference internal" href="../abstractoperator/index.html#airflow.models.abstractoperator.AbstractOperator" title="airflow.models.abstractoperator.AbstractOperator"><em>airflow.models.abstractoperator.AbstractOperator</em></a>) – airflow operator</p></li>
-<li><p><strong>ti_key</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – TaskInstance ID to return link for</p></li>
+<li><p><strong>operator</strong> (<a class="reference internal" href="../abstractoperator/index.html#airflow.models.abstractoperator.AbstractOperator" title="airflow.models.abstractoperator.AbstractOperator"><em>airflow.models.abstractoperator.AbstractOperator</em></a>) -- airflow operator</p></li>
+<li><p><strong>ti_key</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- TaskInstance ID to return link for</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/connection/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/connection/index.html
index 4cda77c4c..ad71857e5 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/connection/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/connection/index.html
@@ -907,17 +907,17 @@ passwords when using operators or hooks.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The connection ID.</p></li>
-<li><p><strong>conn_type</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The connection type.</p></li>
-<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The connection description.</p></li>
-<li><p><strong>host</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The host.</p></li>
-<li><p><strong>login</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The login.</p></li>
-<li><p><strong>password</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The password.</p></li>
-<li><p><strong>schema</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The schema.</p></li>
-<li><p><strong>port</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – The port number.</p></li>
-<li><p><strong>extra</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#dict" title="(in Python v3.10)"><em>dict</em></a><em>]</em><em>]</em>) – Extra metadata. Non-standard data such as private/SSH keys can be saved here. JSON
+<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The connection ID.</p></li>
+<li><p><strong>conn_type</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The connection type.</p></li>
+<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The connection description.</p></li>
+<li><p><strong>host</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The host.</p></li>
+<li><p><strong>login</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The login.</p></li>
+<li><p><strong>password</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The password.</p></li>
+<li><p><strong>schema</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The schema.</p></li>
+<li><p><strong>port</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- The port number.</p></li>
+<li><p><strong>extra</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#dict" title="(in Python v3.10)"><em>dict</em></a><em>]</em><em>]</em>) -- Extra metadata. Non-standard data such as private/SSH keys can be saved here. JSON
 encoded object.</p></li>
-<li><p><strong>uri</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – URI address describing connection parameters.</p></li>
+<li><p><strong>uri</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- URI address describing connection parameters.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1096,7 +1096,7 @@ default representation (<cite>__repr__</cite>).</p>
 <dd><p>Get connection by conn_id.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>connection</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/crypto/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/crypto/index.html
index 12eebb497..59fdec34d 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/crypto/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/crypto/index.html
@@ -867,7 +867,7 @@
 <dl class="py class">
 <dt class="sig sig-object py" id="airflow.models.crypto.NullFernet">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.models.crypto.</span></span><span class="sig-name descname"><span class="pre">NullFernet</span></span><a class="reference internal" href="../../../../_modules/airflow/models/crypto.html#NullFernet"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.crypto.NullFernet" title="Permal [...]
-<dd><p>A “Null” encryptor class that doesn’t encrypt or decrypt but that presents
+<dd><p>A &quot;Null&quot; encryptor class that doesn't encrypt or decrypt but that presents
 a similar interface to Fernet.</p>
 <p>The purpose of this is to make the rest of the code not have to know the
 difference, and to only display the message once, not 20 times when
@@ -902,7 +902,7 @@ or because the Fernet key is invalid.</p>
 <dd class="field-odd"><p>Fernet object</p>
 </dd>
 <dt class="field-even">Raises</dt>
-<dd class="field-even"><p>airflow.exceptions.AirflowException if there’s a problem trying to load Fernet</p>
+<dd class="field-even"><p>airflow.exceptions.AirflowException if there's a problem trying to load Fernet</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dag/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dag/index.html
index 69eca6952..4a72c080f 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dag/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dag/index.html
@@ -1263,7 +1263,7 @@ Overridden DagRuns are ignored.</p>
 dependencies. A dag also has a schedule, a start date and an end date
 (optional). For each schedule, (say daily or hourly), the DAG needs to run
 each individual tasks as their dependencies are met. Certain tasks have
-the property of depending on their own past, meaning that they can’t run
+the property of depending on their own past, meaning that they can't run
 until their previous schedule (and upstream tasks) are completed.</p>
 <p>DAGs essentially act as namespaces for tasks. A task_id can only be
 added once to a DAG.</p>
@@ -1272,68 +1272,68 @@ dates. See <a class="reference internal" href="../../../../timezone.html#timezon
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The id of the DAG; must consist exclusively of alphanumeric
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The id of the DAG; must consist exclusively of alphanumeric
 characters, dashes, dots and underscores (all ASCII)</p></li>
-<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The description for the DAG to e.g. be shown on the webserver</p></li>
-<li><p><strong>schedule_interval</strong> (<em>ScheduleIntervalArg</em>) – Defines how often that DAG runs, this
-timedelta object gets added to your latest task instance’s
+<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The description for the DAG to e.g. be shown on the webserver</p></li>
+<li><p><strong>schedule_interval</strong> (<em>ScheduleIntervalArg</em>) -- Defines how often that DAG runs, this
+timedelta object gets added to your latest task instance's
 execution_date to figure out the next schedule</p></li>
-<li><p><strong>timetable</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../../timetables/base/index.html#airflow.timetables.base.Timetable" title="airflow.timetables.base.Timetable"><em>airflow.timetables.base.Timetable</em></a><em>]</em>) – Specify which timetable to use (in which case schedule_interval
+<li><p><strong>timetable</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../../timetables/base/index.html#airflow.timetables.base.Timetable" title="airflow.timetables.base.Timetable"><em>airflow.timetables.base.Timetable</em></a><em>]</em>) -- Specify which timetable to use (in which case schedule_interval
 must not be set). See <a class="reference internal" href="../../../../howto/timetable.html"><span class="doc">Customizing DAG Scheduling with Timetables</span></a> for more information</p></li>
-<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – The timestamp from which the scheduler will
+<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- The timestamp from which the scheduler will
 attempt to backfill</p></li>
-<li><p><strong>end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – A date beyond which your DAG won’t run, leave to None
+<li><p><strong>end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- A date beyond which your DAG won't run, leave to None
 for open ended scheduling</p></li>
-<li><p><strong>template_searchpath</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) – This list of folders (non relative)
+<li><p><strong>template_searchpath</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) -- This list of folders (non relative)
 defines where jinja will look for your templates. Order matters.
 Note that jinja/airflow includes the path of your DAG file by
 default</p></li>
-<li><p><strong>template_undefined</strong> (<em>Type</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.StrictUndefined" title="(in Jinja v2.11.x)"><em>jinja2.StrictUndefined</em></a><em>]</em>) – Template undefined type.</p></li>
-<li><p><strong>user_defined_macros</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – a dictionary of macros that will be exposed
+<li><p><strong>template_undefined</strong> (<em>Type</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.StrictUndefined" title="(in Jinja v2.11.x)"><em>jinja2.StrictUndefined</em></a><em>]</em>) -- Template undefined type.</p></li>
+<li><p><strong>user_defined_macros</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- a dictionary of macros that will be exposed
 in your jinja templates. For example, passing <code class="docutils literal notranslate"><span class="pre">dict(foo='bar')</span></code>
 to this argument allows you to <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">foo</span> <span class="pre">}}</span></code> in all jinja
 templates related to this DAG. Note that you can pass any
 type of object here.</p></li>
-<li><p><strong>user_defined_filters</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – a dictionary of filters that will be exposed
+<li><p><strong>user_defined_filters</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- a dictionary of filters that will be exposed
 in your jinja templates. For example, passing
 <code class="docutils literal notranslate"><span class="pre">dict(hello=lambda</span> <span class="pre">name:</span> <span class="pre">'Hello</span> <span class="pre">%s'</span> <span class="pre">%</span> <span class="pre">name)</span></code> to this argument allows
 you to <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">'world'</span> <span class="pre">|</span> <span class="pre">hello</span> <span class="pre">}}</span></code> in all jinja templates related to
 this DAG.</p></li>
-<li><p><strong>default_args</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – A dictionary of default parameters to be used
+<li><p><strong>default_args</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- A dictionary of default parameters to be used
 as constructor keyword parameters when initialising operators.
 Note that operators have the same hook, and precede those defined
-here, meaning that if your dict contains <cite>‘depends_on_past’: True</cite>
-here and <cite>‘depends_on_past’: False</cite> in the operator’s call
+here, meaning that if your dict contains <cite>'depends_on_past': True</cite>
+here and <cite>'depends_on_past': False</cite> in the operator's call
 <cite>default_args</cite>, the actual value will be <cite>False</cite>.</p></li>
-<li><p><strong>params</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – a dictionary of DAG level parameters that are made
+<li><p><strong>params</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- a dictionary of DAG level parameters that are made
 accessible in templates, namespaced under <cite>params</cite>. These
 params can be overridden at the task level.</p></li>
-<li><p><strong>max_active_tasks</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – the number of task instances allowed to run
+<li><p><strong>max_active_tasks</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- the number of task instances allowed to run
 concurrently</p></li>
-<li><p><strong>max_active_runs</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – maximum number of active DAG runs, beyond this
-number of DAG runs in a running state, the scheduler won’t create
+<li><p><strong>max_active_runs</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- maximum number of active DAG runs, beyond this
+number of DAG runs in a running state, the scheduler won't create
 new active DAG runs</p></li>
-<li><p><strong>dagrun_timeout</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) – specify how long a DagRun should be up before
+<li><p><strong>dagrun_timeout</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) -- specify how long a DagRun should be up before
 timing out / failing, so that new DagRuns can be created. The timeout
 is only enforced for scheduled DagRuns.</p></li>
-<li><p><strong>sla_miss_callback</strong> (<em>Optional</em><em>[</em><em>Callable</em><em>[</em><em>[</em><a class="reference internal" href="#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>DAG</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</ [...]
+<li><p><strong>sla_miss_callback</strong> (<em>Optional</em><em>[</em><em>Callable</em><em>[</em><em>[</em><a class="reference internal" href="#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>DAG</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</ [...]
 timeouts. See <a class="reference internal" href="../../../../concepts/tasks.html#concepts-sla-miss-callback"><span class="std std-ref">sla_miss_callback</span></a> for
 more information about the function signature and parameters that are
 passed to the callback.</p></li>
-<li><p><strong>default_view</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Specify DAG default view (grid, graph, duration,
+<li><p><strong>default_view</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Specify DAG default view (grid, graph, duration,
 gantt, landing_times), default grid</p></li>
-<li><p><strong>orientation</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Specify DAG orientation in graph view (LR, TB, RL, BT), default LR</p></li>
-<li><p><strong>catchup</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Perform scheduler catchup (or only run latest)? Defaults to True</p></li>
-<li><p><strong>on_failure_callback</strong> (<em>Optional</em><em>[</em><em>DagStateChangeCallback</em><em>]</em>) – A function to be called when a DagRun of this dag fails.
+<li><p><strong>orientation</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Specify DAG orientation in graph view (LR, TB, RL, BT), default LR</p></li>
+<li><p><strong>catchup</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Perform scheduler catchup (or only run latest)? Defaults to True</p></li>
+<li><p><strong>on_failure_callback</strong> (<em>Optional</em><em>[</em><em>DagStateChangeCallback</em><em>]</em>) -- A function to be called when a DagRun of this dag fails.
 A context dictionary is passed as a single parameter to this function.</p></li>
-<li><p><strong>on_success_callback</strong> (<em>Optional</em><em>[</em><em>DagStateChangeCallback</em><em>]</em>) – Much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
+<li><p><strong>on_success_callback</strong> (<em>Optional</em><em>[</em><em>DagStateChangeCallback</em><em>]</em>) -- Much like the <code class="docutils literal notranslate"><span class="pre">on_failure_callback</span></code> except
 that it is executed when the dag succeeds.</p></li>
-<li><p><strong>access_control</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – Specify optional DAG-level actions, e.g.,
-“{‘role1’: {‘can_read’}, ‘role2’: {‘can_read’, ‘can_edit’, ‘can_delete’}}”</p></li>
-<li><p><strong>is_paused_upon_creation</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) – Specifies if the dag is paused when created for the first time.
+<li><p><strong>access_control</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- Specify optional DAG-level actions, e.g.,
+&quot;{'role1': {'can_read'}, 'role2': {'can_read', 'can_edit', 'can_delete'}}&quot;</p></li>
+<li><p><strong>is_paused_upon_creation</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) -- Specifies if the dag is paused when created for the first time.
 If the dag exists already, this flag will be ignored. If this optional parameter
 is not specified, the global config setting will be used.</p></li>
-<li><p><strong>jinja_environment_kwargs</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – <p>additional configuration options to be passed to Jinja
+<li><p><strong>jinja_environment_kwargs</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- <p>additional configuration options to be passed to Jinja
 <code class="docutils literal notranslate"><span class="pre">Environment</span></code> for template rendering</p>
 <p><strong>Example</strong>: to avoid Jinja from removing a trailing newline from template strings</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">DAG</span><span class="p">(</span><span class="n">dag_id</span><span class="o">=</span><span class="s1">&#39;my-dag&#39;</span><span class="p">,</span>
@@ -1346,10 +1346,10 @@ is not specified, the global config setting will be used.</p></li>
 </div>
 <p><strong>See</strong>: <a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment">Jinja Environment documentation</a></p>
 </p></li>
-<li><p><strong>render_template_as_native_obj</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If True, uses a Jinja <code class="docutils literal notranslate"><span class="pre">NativeEnvironment</span></code>
+<li><p><strong>render_template_as_native_obj</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If True, uses a Jinja <code class="docutils literal notranslate"><span class="pre">NativeEnvironment</span></code>
 to render templates as native Python types. If False, a Jinja
 <code class="docutils literal notranslate"><span class="pre">Environment</span></code> is used to render templates as string values.</p></li>
-<li><p><strong>tags</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – List of tags to help filtering DAGs in the UI.</p></li>
+<li><p><strong>tags</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- List of tags to help filtering DAGs in the UI.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1424,7 +1424,7 @@ from a ZIP file or other DAG distribution format.</p>
 <dd><p>Calculates the following schedule for this dag in UTC.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>dttm</strong> – utc datetime</p>
+<dd class="field-odd"><p><strong>dttm</strong> -- utc datetime</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>utc datetime</p>
@@ -1441,7 +1441,7 @@ from a ZIP file or other DAG distribution format.</p>
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.get_next_data_interval">
 <span class="sig-name descname"><span class="pre">get_next_data_interval</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">dag_model</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dag.html#DAG.get_next_data_interval"><span class="viewcode-link"><span class="pre">[source]</span></span> [...]
 <dd><p>Get the data interval of the next scheduled run.</p>
-<p>For compatibility, this method infers the data interval from the DAG’s
+<p>For compatibility, this method infers the data interval from the DAG's
 schedule if the run does not have an explicit one set, which is possible
 for runs created prior to AIP-39.</p>
 <p>This function is private to Airflow core and should not be depended as a
@@ -1454,7 +1454,7 @@ part of the Python API.</p>
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.get_run_data_interval">
 <span class="sig-name descname"><span class="pre">get_run_data_interval</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">run</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dag.html#DAG.get_run_data_interval"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a c [...]
 <dd><p>Get the data interval of this run.</p>
-<p>For compatibility, this method infers the data interval from the DAG’s
+<p>For compatibility, this method infers the data interval from the DAG's
 schedule if the run does not have an explicit one set, which is possible for
 runs created prior to AIP-39.</p>
 <p>This function is private to Airflow core and should not be depended as a
@@ -1482,17 +1482,17 @@ Airflow 2.2.</p>
 <dd><p>Get information about the next DagRun of this dag after <code class="docutils literal notranslate"><span class="pre">date_last_automated_dagrun</span></code>.</p>
 <p>This calculates what time interval the next DagRun should operate on
 (its execution date) and when it can be scheduled, according to the
-dag’s timetable, start_date, end_date, etc. This doesn’t check max
-active run or any other “max_active_tasks” type limits, but only
+dag's timetable, start_date, end_date, etc. This doesn't check max
+active run or any other &quot;max_active_tasks&quot; type limits, but only
 performs calculations based on the various date and interval fields of
 this dag and its tasks.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>last_automated_dagrun</strong> (<em>Union</em><em>[</em><em>None</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference internal" href="../../timetables/base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) – The <code cl [...]
-existing “automated” DagRuns for this dag (scheduled or backfill,
+<li><p><strong>last_automated_dagrun</strong> (<em>Union</em><em>[</em><em>None</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference internal" href="../../timetables/base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) -- The <code c [...]
+existing &quot;automated&quot; DagRuns for this dag (scheduled or backfill,
 but not manual).</p></li>
-<li><p><strong>restricted</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If set to <em>False</em> (default is <em>True</em>), ignore
+<li><p><strong>restricted</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If set to <em>False</em> (default is <em>True</em>), ignore
 <code class="docutils literal notranslate"><span class="pre">start_date</span></code>, <code class="docutils literal notranslate"><span class="pre">end_date</span></code>, and <code class="docutils literal notranslate"><span class="pre">catchup</span></code> specified on the DAG
 or tasks.</p></li>
 </ul>
@@ -1517,7 +1517,7 @@ going to be scheduled.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.iter_dagrun_infos_between">
 <span class="sig-name descname"><span class="pre">iter_dagrun_infos_between</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">earliest</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">latest</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span  [...]
-<dd><p>Yield DagRunInfo using this DAG’s timetable between given interval.</p>
+<dd><p>Yield DagRunInfo using this DAG's timetable between given interval.</p>
 <p>DagRunInfo instances yielded if their <code class="docutils literal notranslate"><span class="pre">logical_date</span></code> is not earlier
 than <code class="docutils literal notranslate"><span class="pre">earliest</span></code>, nor later than <code class="docutils literal notranslate"><span class="pre">latest</span></code>. The instances are ordered
 by their <code class="docutils literal notranslate"><span class="pre">logical_date</span></code> from earliest to latest.</p>
@@ -1537,16 +1537,16 @@ if <code class="docutils literal notranslate"><span class="pre">align=True</span
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.get_run_dates">
 <span class="sig-name descname"><span class="pre">get_run_dates</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">start_date</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">end_date</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em><span class="sig-pa [...]
 <dd><p>Returns a list of dates between the interval received as parameter using this
-dag’s schedule interval. Returned dates can be used for execution dates.</p>
+dag's schedule interval. Returned dates can be used for execution dates.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>start_date</strong> – The start date of the interval.</p></li>
-<li><p><strong>end_date</strong> – The end date of the interval. Defaults to <code class="docutils literal notranslate"><span class="pre">timezone.utcnow()</span></code>.</p></li>
+<li><p><strong>start_date</strong> -- The start date of the interval.</p></li>
+<li><p><strong>end_date</strong> -- The end date of the interval. Defaults to <code class="docutils literal notranslate"><span class="pre">timezone.utcnow()</span></code>.</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
-<dd class="field-even"><p>A list of dates within the interval following the dag’s schedule.</p>
+<dd class="field-even"><p>A list of dates within the interval following the dag's schedule.</p>
 </dd>
 <dt class="field-odd">Return type</dt>
 <dd class="field-odd"><p><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#list" title="(in Python v3.10)">list</a></p>
@@ -1639,8 +1639,8 @@ dag’s schedule interval. Returned dates can be used for execution dates.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – dag parameter name.</p></li>
-<li><p><strong>default</strong> (<em>Any</em>) – fallback value for dag parameter.</p></li>
+<li><p><strong>name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- dag parameter name.</p></li>
+<li><p><strong>default</strong> (<em>Any</em>) -- fallback value for dag parameter.</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1683,7 +1683,7 @@ dag’s schedule interval. Returned dates can be used for execution dates.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.relative_fileloc">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">relative_fileloc</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dag.html#DAG.relative_fileloc"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="h [...]
-<dd><p>File location of the importable dag ‘file’ relative to the configured DAGs folder.</p>
+<dd><p>File location of the importable dag 'file' relative to the configured DAGs folder.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -1767,14 +1767,14 @@ has been reached</p>
 <dd><p>Triggers the appropriate callback depending on the value of success, namely the
 on_failure_callback or on_success_callback. This method gets the context of a
 single TaskInstance part of this DagRun and passes that to the callable along
-with a ‘reason’, primarily to differentiate DagRun failures.</p>
+with a 'reason', primarily to differentiate DagRun failures.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dagrun</strong> – DagRun object</p></li>
-<li><p><strong>success</strong> – Flag to specify if failure or success callback should be called</p></li>
-<li><p><strong>reason</strong> – Completion reason</p></li>
-<li><p><strong>session</strong> – Database session</p></li>
+<li><p><strong>dagrun</strong> -- DagRun object</p></li>
+<li><p><strong>success</strong> -- Flag to specify if failure or success callback should be called</p></li>
+<li><p><strong>reason</strong> -- Completion reason</p></li>
+<li><p><strong>session</strong> -- Database session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1794,12 +1794,12 @@ with a ‘reason’, primarily to differentiate DagRun failures.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.get_num_active_runs">
 <span class="sig-name descname"><span class="pre">get_num_active_runs</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">external_trigger</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">only_running</span></span><span cl [...]
-<dd><p>Returns the number of active “running” dag runs</p>
+<dd><p>Returns the number of active &quot;running&quot; dag runs</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>external_trigger</strong> – True for externally triggered active dag runs</p></li>
-<li><p><strong>session</strong> – </p></li>
+<li><p><strong>external_trigger</strong> -- True for externally triggered active dag runs</p></li>
+<li><p><strong>session</strong> -- </p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1816,9 +1816,9 @@ none.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – The execution date of the DagRun to find.</p></li>
-<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The run_id of the DagRun to find.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – </p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- The execution date of the DagRun to find.</p></li>
+<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The run_id of the DagRun to find.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- </p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1834,9 +1834,9 @@ none.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>start_date</strong> – The starting execution date of the DagRun to find.</p></li>
-<li><p><strong>end_date</strong> – The ending execution date of the DagRun to find.</p></li>
-<li><p><strong>session</strong> – </p></li>
+<li><p><strong>start_date</strong> -- The starting execution date of the DagRun to find.</p></li>
+<li><p><strong>end_date</strong> -- The ending execution date of the DagRun to find.</p></li>
+<li><p><strong>session</strong> -- </p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1912,17 +1912,17 @@ in failed or upstream_failed state.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Task ID of the TaskInstance</p></li>
-<li><p><strong>map_indexes</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em><em>]</em>) – Only set TaskInstance if its map_index matches.
+<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Task ID of the TaskInstance</p></li>
+<li><p><strong>map_indexes</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em><em>]</em>) -- Only set TaskInstance if its map_index matches.
 If None (default), all mapped TaskInstances of the task are set.</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – Execution date of the TaskInstance</p></li>
-<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The run_id of the TaskInstance</p></li>
-<li><p><strong>state</strong> (<em>airflow.utils.state.TaskInstanceState</em>) – State to set the TaskInstance to</p></li>
-<li><p><strong>upstream</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Include all upstream tasks of the given task_id</p></li>
-<li><p><strong>downstream</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Include all downstream tasks of the given task_id</p></li>
-<li><p><strong>future</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Include all future TaskInstances of the given task_id</p></li>
-<li><p><strong>commit</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Commit changes</p></li>
-<li><p><strong>past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Include all past TaskInstances of the given task_id</p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- Execution date of the TaskInstance</p></li>
+<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The run_id of the TaskInstance</p></li>
+<li><p><strong>state</strong> (<em>airflow.utils.state.TaskInstanceState</em>) -- State to set the TaskInstance to</p></li>
+<li><p><strong>upstream</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Include all upstream tasks of the given task_id</p></li>
+<li><p><strong>downstream</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Include all downstream tasks of the given task_id</p></li>
+<li><p><strong>future</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Include all future TaskInstances of the given task_id</p></li>
+<li><p><strong>commit</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Commit changes</p></li>
+<li><p><strong>past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Include all past TaskInstances of the given task_id</p></li>
 </ul>
 </dd>
 </dl>
@@ -1969,21 +1969,21 @@ a specified date range.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_ids</strong> (<em>Union</em><em>[</em><em>Collection</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><em>Collection</em><em>[</em><em>Tuple</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.or [...]
-<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – The minimum execution_date to clear</p></li>
-<li><p><strong>end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – The maximum execution_date to clear</p></li>
-<li><p><strong>only_failed</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Only clear failed tasks</p></li>
-<li><p><strong>only_running</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Only clear running tasks.</p></li>
-<li><p><strong>confirm_prompt</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ask for confirmation</p></li>
-<li><p><strong>include_subdags</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Clear tasks in subdags and clear external tasks
+<li><p><strong>task_ids</strong> (<em>Union</em><em>[</em><em>Collection</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><em>Collection</em><em>[</em><em>Tuple</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.or [...]
+<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- The minimum execution_date to clear</p></li>
+<li><p><strong>end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- The maximum execution_date to clear</p></li>
+<li><p><strong>only_failed</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Only clear failed tasks</p></li>
+<li><p><strong>only_running</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Only clear running tasks.</p></li>
+<li><p><strong>confirm_prompt</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ask for confirmation</p></li>
+<li><p><strong>include_subdags</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Clear tasks in subdags and clear external tasks
 indicated by ExternalTaskMarker</p></li>
-<li><p><strong>include_parentdag</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Clear tasks in the parent dag of the subdag.</p></li>
-<li><p><strong>dag_run_state</strong> (<em>airflow.utils.state.DagRunState</em>) – state to set DagRun to. If set to False, dagrun state will not
+<li><p><strong>include_parentdag</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Clear tasks in the parent dag of the subdag.</p></li>
+<li><p><strong>dag_run_state</strong> (<em>airflow.utils.state.DagRunState</em>) -- state to set DagRun to. If set to False, dagrun state will not
 be changed.</p></li>
-<li><p><strong>dry_run</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Find the tasks to clear but don’t clear them.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – The sqlalchemy session to use</p></li>
-<li><p><strong>dag_bag</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../dagbag/index.html#airflow.models.dagbag.DagBag" title="airflow.models.dagbag.DagBag"><em>airflow.models.dagbag.DagBag</em></a><em>]</em>) – The DagBag used to find the dags subdags (Optional)</p></li>
-<li><p><strong>exclude_task_ids</strong> (<em>Union</em><em>[</em><em>FrozenSet</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><em>FrozenSet</em><em>[</em><em>Tuple</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.pyt [...]
+<li><p><strong>dry_run</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Find the tasks to clear but don't clear them.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- The sqlalchemy session to use</p></li>
+<li><p><strong>dag_bag</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../dagbag/index.html#airflow.models.dagbag.DagBag" title="airflow.models.dagbag.DagBag"><em>airflow.models.dagbag.DagBag</em></a><em>]</em>) -- The DagBag used to find the dags subdags (Optional)</p></li>
+<li><p><strong>exclude_task_ids</strong> (<em>Union</em><em>[</em><em>FrozenSet</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><em>FrozenSet</em><em>[</em><em>Tuple</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.pyt [...]
 tuples that should not be cleared</p></li>
 </ul>
 </dd>
@@ -2015,13 +2015,13 @@ upstream and downstream neighbours based on the flag passed.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_ids_or_regex</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>airflow.typing_compat.RePatternType</em><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – Either a list of task_ids, or a regex to
+<li><p><strong>task_ids_or_regex</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>airflow.typing_compat.RePatternType</em><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- Either a list of task_ids, or a regex to
 match against task ids (as a string, or compiled regex pattern).</p></li>
-<li><p><strong>include_downstream</strong> – Include all downstream tasks of matched
+<li><p><strong>include_downstream</strong> -- Include all downstream tasks of matched
 tasks, in addition to matched tasks.</p></li>
-<li><p><strong>include_upstream</strong> – Include all upstream tasks of matched tasks,
+<li><p><strong>include_upstream</strong> -- Include all upstream tasks of matched tasks,
 in addition to matched tasks.</p></li>
-<li><p><strong>include_direct_upstream</strong> – Include all tasks directly upstream of matched
+<li><p><strong>include_direct_upstream</strong> -- Include all tasks directly upstream of matched
 and downstream (if include_downstream = True) tasks</p></li>
 </ul>
 </dd>
@@ -2075,7 +2075,7 @@ and downstream (if include_downstream = True) tasks</p></li>
 <dd><p>Add a task to the DAG</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>task</strong> (<em>airflow.models.operator.Operator</em>) – the task you want to add</p>
+<dd class="field-odd"><p><strong>task</strong> (<em>airflow.models.operator.Operator</em>) -- the task you want to add</p>
 </dd>
 </dl>
 </dd></dl>
@@ -2086,7 +2086,7 @@ and downstream (if include_downstream = True) tasks</p></li>
 <dd><p>Add a list of tasks to the DAG</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>tasks</strong> (<em>Iterable</em><em>[</em><em>airflow.models.operator.Operator</em><em>]</em>) – a lit of tasks you want to add</p>
+<dd class="field-odd"><p><strong>tasks</strong> (<em>Iterable</em><em>[</em><em>airflow.models.operator.Operator</em><em>]</em>) -- a lit of tasks you want to add</p>
 </dd>
 </dl>
 </dd></dl>
@@ -2098,23 +2098,23 @@ and downstream (if include_downstream = True) tasks</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>start_date</strong> – the start date of the range to run</p></li>
-<li><p><strong>end_date</strong> – the end date of the range to run</p></li>
-<li><p><strong>mark_success</strong> – True to mark jobs as succeeded without running them</p></li>
-<li><p><strong>local</strong> – True to run the tasks using the LocalExecutor</p></li>
-<li><p><strong>executor</strong> – The executor instance to run the tasks</p></li>
-<li><p><strong>donot_pickle</strong> – True to avoid pickling DAG object and send to workers</p></li>
-<li><p><strong>ignore_task_deps</strong> – True to skip upstream tasks</p></li>
-<li><p><strong>ignore_first_depends_on_past</strong> – True to ignore depends_on_past
+<li><p><strong>start_date</strong> -- the start date of the range to run</p></li>
+<li><p><strong>end_date</strong> -- the end date of the range to run</p></li>
+<li><p><strong>mark_success</strong> -- True to mark jobs as succeeded without running them</p></li>
+<li><p><strong>local</strong> -- True to run the tasks using the LocalExecutor</p></li>
+<li><p><strong>executor</strong> -- The executor instance to run the tasks</p></li>
+<li><p><strong>donot_pickle</strong> -- True to avoid pickling DAG object and send to workers</p></li>
+<li><p><strong>ignore_task_deps</strong> -- True to skip upstream tasks</p></li>
+<li><p><strong>ignore_first_depends_on_past</strong> -- True to ignore depends_on_past
 dependencies for the first set of tasks only</p></li>
-<li><p><strong>pool</strong> – Resource pool to use</p></li>
-<li><p><strong>delay_on_limit_secs</strong> – Time in seconds to wait before next attempt to run
+<li><p><strong>pool</strong> -- Resource pool to use</p></li>
+<li><p><strong>delay_on_limit_secs</strong> -- Time in seconds to wait before next attempt to run
 dag run when max_active_runs limit has been reached</p></li>
-<li><p><strong>verbose</strong> – Make logging output more verbose</p></li>
-<li><p><strong>conf</strong> – user defined dictionary passed from CLI</p></li>
-<li><p><strong>rerun_failed_tasks</strong> – </p></li>
-<li><p><strong>run_backwards</strong> – </p></li>
-<li><p><strong>run_at_least_once</strong> – If true, always run the DAG at least once even
+<li><p><strong>verbose</strong> -- Make logging output more verbose</p></li>
+<li><p><strong>conf</strong> -- user defined dictionary passed from CLI</p></li>
+<li><p><strong>rerun_failed_tasks</strong> -- </p></li>
+<li><p><strong>run_backwards</strong> -- </p></li>
+<li><p><strong>run_at_least_once</strong> -- If true, always run the DAG at least once even
 if no logical run exists within the time range.</p></li>
 </ul>
 </dd>
@@ -2135,17 +2135,17 @@ Returns the dag run.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – defines the run id for this dag run</p></li>
-<li><p><strong>run_type</strong> (<em>Optional</em><em>[</em><em>airflow.utils.types.DagRunType</em><em>]</em>) – type of DagRun</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – the execution date of this dag run</p></li>
-<li><p><strong>state</strong> (<em>airflow.utils.state.DagRunState</em>) – the state of the dag run</p></li>
-<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – the date this dag run should be evaluated</p></li>
-<li><p><strong>external_trigger</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) – whether this dag run is externally triggered</p></li>
-<li><p><strong>conf</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#dict" title="(in Python v3.10)"><em>dict</em></a><em>]</em>) – Dict containing configuration/parameters to pass to the DAG</p></li>
-<li><p><strong>creating_job_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – id of the job creating this DagRun</p></li>
-<li><p><strong>session</strong> – database session</p></li>
-<li><p><strong>dag_hash</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Hash of Serialized DAG</p></li>
-<li><p><strong>data_interval</strong> (<em>Optional</em><em>[</em><em>Tuple</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em>) – Data interval of the DagRun</p></li>
+<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- defines the run id for this dag run</p></li>
+<li><p><strong>run_type</strong> (<em>Optional</em><em>[</em><em>airflow.utils.types.DagRunType</em><em>]</em>) -- type of DagRun</p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- the execution date of this dag run</p></li>
+<li><p><strong>state</strong> (<em>airflow.utils.state.DagRunState</em>) -- the state of the dag run</p></li>
+<li><p><strong>start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- the date this dag run should be evaluated</p></li>
+<li><p><strong>external_trigger</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) -- whether this dag run is externally triggered</p></li>
+<li><p><strong>conf</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#dict" title="(in Python v3.10)"><em>dict</em></a><em>]</em>) -- Dict containing configuration/parameters to pass to the DAG</p></li>
+<li><p><strong>creating_job_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- id of the job creating this DagRun</p></li>
+<li><p><strong>session</strong> -- database session</p></li>
+<li><p><strong>dag_hash</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Hash of Serialized DAG</p></li>
+<li><p><strong>data_interval</strong> (<em>Optional</em><em>[</em><em>Tuple</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em>) -- Data interval of the DagRun</p></li>
 </ul>
 </dd>
 </dl>
@@ -2167,7 +2167,7 @@ calculated fields.</p>
 <p>Note that this method can be called for both DAGs and SubDAGs. A SubDag is actually a SubDagOperator.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>dags</strong> (<em>Collection</em><em>[</em><a class="reference internal" href="#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>DAG</em></a><em>]</em>) – the DAG objects to save to the DB</p>
+<dd class="field-odd"><p><strong>dags</strong> (<em>Collection</em><em>[</em><a class="reference internal" href="#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>DAG</em></a><em>]</em>) -- the DAG objects to save to the DB</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>None</p>
@@ -2201,7 +2201,7 @@ SubDagOperator.</p>
 marked as active in the ORM</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>active_dag_ids</strong> – list of DAG IDs that are active</p>
+<dd class="field-odd"><p><strong>active_dag_ids</strong> -- list of DAG IDs that are active</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>None</p>
@@ -2216,7 +2216,7 @@ marked as active in the ORM</p>
 the expiration date. These DAGs were likely deleted.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>expiration_date</strong> – set inactive DAGs that were touched before this
+<dd class="field-odd"><p><strong>expiration_date</strong> -- set inactive DAGs that were touched before this
 time</p>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -2232,10 +2232,10 @@ time</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>session</strong> – ORM session</p></li>
-<li><p><strong>dag_id</strong> – ID of the DAG to get the task concurrency of</p></li>
-<li><p><strong>task_ids</strong> – A list of valid task IDs for the given DAG</p></li>
-<li><p><strong>states</strong> – A list of states to filter by if supplied</p></li>
+<li><p><strong>session</strong> -- ORM session</p></li>
+<li><p><strong>dag_id</strong> -- ID of the DAG to get the task concurrency of</p></li>
+<li><p><strong>task_ids</strong> -- A list of valid task IDs for the given DAG</p></li>
+<li><p><strong>states</strong> -- A list of states to filter by if supplied</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -2275,7 +2275,7 @@ rather than merge with, existing info.</p>
 <dt class="sig sig-object py" id="airflow.models.dag.DAG.validate_schedule_and_params">
 <span class="sig-name descname"><span class="pre">validate_schedule_and_params</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dag.html#DAG.validate_schedule_and_params"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.dag.DAG.validate_schedule_ [...]
 <dd><p>Validates &amp; raise exception if there are any Params in the DAG which neither have a default value nor
-have the null in schema[‘type’] list, but the DAG have a schedule_interval which is not None.</p>
+have the null in schema['type'] list, but the DAG have a schedule_interval which is not None.</p>
 </dd></dl>
 
 </dd></dl>
@@ -2498,7 +2498,7 @@ have the null in schema[‘type’] list, but the DAG have a schedule_interval w
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.dag.DagModel.get_is_paused">
 <span class="sig-name descname"><span class="pre">get_is_paused</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em><span class="sig-paren">)</sp [...]
-<dd><p>Provide interface compatibility to ‘DAG’.</p>
+<dd><p>Provide interface compatibility to 'DAG'.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -2510,8 +2510,8 @@ have the null in schema[‘type’] list, but the DAG have a schedule_interval w
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_ids</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – List of Dag ids</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dag_ids</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- List of Dag ids</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -2540,7 +2540,7 @@ have a value</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.dag.DagModel.relative_fileloc">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">relative_fileloc</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dag.html#DagModel.relative_fileloc"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a cla [...]
-<dd><p>File location of the importable dag ‘file’ relative to the configured DAGs folder.</p>
+<dd><p>File location of the importable dag 'file' relative to the configured DAGs folder.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -2552,9 +2552,9 @@ have a value</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>is_paused</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Is the DAG paused</p></li>
-<li><p><strong>including_subdags</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – whether to include the DAG’s subdags</p></li>
-<li><p><strong>session</strong> – session</p></li>
+<li><p><strong>is_paused</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Is the DAG paused</p></li>
+<li><p><strong>including_subdags</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- whether to include the DAG's subdags</p></li>
+<li><p><strong>session</strong> -- session</p></li>
 </ul>
 </dd>
 </dl>
@@ -2567,8 +2567,8 @@ have a value</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>alive_dag_filelocs</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – file paths of alive DAGs</p></li>
-<li><p><strong>session</strong> – ORM Session</p></li>
+<li><p><strong>alive_dag_filelocs</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- file paths of alive DAGs</p></li>
+<li><p><strong>session</strong> -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -2578,8 +2578,8 @@ have a value</p>
 <dt class="sig sig-object py" id="airflow.models.dag.DagModel.dags_needing_dagruns">
 <em class="property"><span class="pre">classmethod</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">dags_needing_dagruns</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">cls</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dag.html#DagModel.dags_n [...]
 <dd><p>Return (and lock) a list of Dag objects that are due to create a new DagRun.</p>
-<p>This will return a resultset of rows  that is row-level-locked with a “SELECT … FOR UPDATE” query,
-you should ensure that any scheduling decisions are made in a single transaction – as soon as the
+<p>This will return a resultset of rows  that is row-level-locked with a &quot;SELECT ... FOR UPDATE&quot; query,
+you should ensure that any scheduling decisions are made in a single transaction -- as soon as the
 transaction is committed it will be unlocked.</p>
 <dl class="field-list simple">
 </dl>
@@ -2592,8 +2592,8 @@ transaction is committed it will be unlocked.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag</strong> (<a class="reference internal" href="#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>DAG</em></a>) – The DAG object</p></li>
-<li><p><strong>most_recent_dag_run</strong> (<em>Union</em><em>[</em><em>None</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference internal" href="../../timetables/base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) – DataInterval ( [...]
+<li><p><strong>dag</strong> (<a class="reference internal" href="#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>DAG</em></a>) -- The DAG object</p></li>
+<li><p><strong>most_recent_dag_run</strong> (<em>Union</em><em>[</em><em>None</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference internal" href="../../timetables/base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) -- DataInterval  [...]
 if not yet scheduled.</p></li>
 </ul>
 </dd>
@@ -2610,8 +2610,8 @@ Accepts kwargs for operator kwarg. Can be used to parameterize DAGs.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_args</strong> – Arguments for DAG object</p></li>
-<li><p><strong>dag_kwargs</strong> – Kwargs for DAG object.</p></li>
+<li><p><strong>dag_args</strong> -- Arguments for DAG object</p></li>
+<li><p><strong>dag_kwargs</strong> -- Kwargs for DAG object.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagbag/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagbag/index.html
index e37246dc0..de19b090e 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagbag/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagbag/index.html
@@ -870,14 +870,14 @@ independent settings sets.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_folder</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/pathlib.html#pathlib.Path" title="(in Python v3.10)"><em>pathlib.Path</em></a><em>, </em><em>None</em><em>]</em>) – the folder to scan to find DAGs</p></li>
-<li><p><strong>include_examples</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – whether to include the examples that ship
+<li><p><strong>dag_folder</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/pathlib.html#pathlib.Path" title="(in Python v3.10)"><em>pathlib.Path</em></a><em>, </em><em>None</em><em>]</em>) -- the folder to scan to find DAGs</p></li>
+<li><p><strong>include_examples</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- whether to include the examples that ship
 with airflow or not</p></li>
-<li><p><strong>include_smart_sensor</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – whether to include the smart sensor native
+<li><p><strong>include_smart_sensor</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- whether to include the smart sensor native
 DAGs that create the smart sensor operators for whole cluster</p></li>
-<li><p><strong>read_dags_from_db</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Read DAGs from DB if <code class="docutils literal notranslate"><span class="pre">True</span></code> is passed.
+<li><p><strong>read_dags_from_db</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Read DAGs from DB if <code class="docutils literal notranslate"><span class="pre">True</span></code> is passed.
 If <code class="docutils literal notranslate"><span class="pre">False</span></code> DAGs are read from python files.</p></li>
-<li><p><strong>load_op_links</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Should the extra operator link be loaded via plugins when
+<li><p><strong>load_op_links</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Should the extra operator link be loaded via plugins when
 de-serializing the DAG? This flag is set to False in Scheduler so that Extra Operator links
 are not loaded to not run User code in Scheduler.</p></li>
 </ul>
@@ -923,7 +923,7 @@ are not loaded to not run User code in Scheduler.</p></li>
 <dd><p>Gets the DAG out of the dictionary, and refreshes it if expired</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>dag_id</strong> – DAG Id</p>
+<dd class="field-odd"><p><strong>dag_id</strong> -- DAG Id</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagcode/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagcode/index.html
index 08fd445be..f2ce8cd72 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagcode/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagcode/index.html
@@ -872,7 +872,7 @@
 <dd><p>Writes code into database.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> – ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> -- ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -884,8 +884,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>filelocs</strong> (<em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – file paths of DAGs to sync</p></li>
-<li><p><strong>session</strong> – ORM Session</p></li>
+<li><p><strong>filelocs</strong> (<em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- file paths of DAGs to sync</p></li>
+<li><p><strong>session</strong> -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -898,8 +898,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>alive_dag_filelocs</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – file paths of alive DAGs</p></li>
-<li><p><strong>session</strong> – ORM Session</p></li>
+<li><p><strong>alive_dag_filelocs</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- file paths of alive DAGs</p></li>
+<li><p><strong>session</strong> -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -912,8 +912,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>fileloc</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the file to check</p></li>
-<li><p><strong>session</strong> – ORM Session</p></li>
+<li><p><strong>fileloc</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the file to check</p></li>
+<li><p><strong>session</strong> -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -925,7 +925,7 @@
 <dd><p>Returns source code for a given fileloc.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>fileloc</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – file path of a DAG</p>
+<dd class="field-odd"><p><strong>fileloc</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- file path of a DAG</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>source code as string</p>
@@ -956,7 +956,7 @@
 <dd><p>Hashing file location for indexing.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>full_filepath</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – full filepath of DAG file</p>
+<dd class="field-odd"><p><strong>full_filepath</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- full filepath of DAG file</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>hashed full_filepath</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagpickle/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagpickle/index.html
index a452eebbd..12cc48f4c 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagpickle/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagpickle/index.html
@@ -799,7 +799,7 @@
 <dt class="sig sig-object py" id="airflow.models.dagpickle.DagPickle">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.models.dagpickle.</span></span><span class="sig-name descname"><span class="pre">DagPickle</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">dag</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/dagpickle.html#DagPickle"><s [...]
 <dd><p>Bases: <a class="reference internal" href="../base/index.html#airflow.models.base.Base" title="airflow.models.base.Base"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.base.Base</span></code></a></p>
-<p>Dags can originate from different places (user repos, main repo, …)
+<p>Dags can originate from different places (user repos, main repo, ...)
 and also get executed in different places (different executors). This
 object represents a version of a DAG and becomes a source of truth for
 a BackfillJob execution. A pickle is a native python serialized object,
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagrun/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagrun/index.html
index e7be06234..ca7dea285 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagrun/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/dagrun/index.html
@@ -1068,7 +1068,7 @@ by the scheduler (for regular runs) or by an external trigger</p>
 <dd><p>Reloads the current dagrun from the database</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – database session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- database session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1085,8 +1085,8 @@ by the scheduler (for regular runs) or by an external trigger</p>
 <dt class="sig sig-object py" id="airflow.models.dagrun.DagRun.next_dagruns_to_examine">
 <em class="property"><span class="pre">classmethod</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">next_dagruns_to_examine</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">cls</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">state</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span></em>, <em class="sig-param"><span class="n"><sp [...]
 <dd><p>Return the next DagRuns that the scheduler should attempt to schedule.</p>
-<p>This will return zero or more DagRun rows that are row-level-locked with a “SELECT … FOR UPDATE”
-query, you should ensure that any scheduling decisions are made in a single transaction – as soon as
+<p>This will return zero or more DagRun rows that are row-level-locked with a &quot;SELECT ... FOR UPDATE&quot;
+query, you should ensure that any scheduling decisions are made in a single transaction -- as soon as
 the transaction is committed it will be unlocked.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Return type</dt>
@@ -1102,17 +1102,17 @@ the transaction is committed it will be unlocked.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) – the dag_id or list of dag_id to find dag runs for</p></li>
-<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – defines the run id for this dag run</p></li>
-<li><p><strong>run_type</strong> (<em>Optional</em><em>[</em><em>airflow.utils.types.DagRunType</em><em>]</em>) – type of DagRun</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em><em>]</em>) – the executi [...]
-<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) – the state of the dag run</p></li>
-<li><p><strong>external_trigger</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) – whether this dag run is externally triggered</p></li>
-<li><p><strong>no_backfills</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – return no backfills (True), return all (False).
+<li><p><strong>dag_id</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) -- the dag_id or list of dag_id to find dag runs for</p></li>
+<li><p><strong>run_id</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- defines the run id for this dag run</p></li>
+<li><p><strong>run_type</strong> (<em>Optional</em><em>[</em><em>airflow.utils.types.DagRunType</em><em>]</em>) -- type of DagRun</p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em><em>]</em>) -- the execut [...]
+<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) -- the state of the dag run</p></li>
+<li><p><strong>external_trigger</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) -- whether this dag run is externally triggered</p></li>
+<li><p><strong>no_backfills</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- return no backfills (True), return all (False).
 Defaults to False</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – database session</p></li>
-<li><p><strong>execution_start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – dag run that was executed from this date</p></li>
-<li><p><strong>execution_end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – dag run that was executed until this date</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- database session</p></li>
+<li><p><strong>execution_start_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- dag run that was executed from this date</p></li>
+<li><p><strong>execution_end_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- dag run that was executed until this date</p></li>
 </ul>
 </dd>
 </dl>
@@ -1126,10 +1126,10 @@ Defaults to False</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the dag_id to find duplicates for</p></li>
-<li><p><strong>run_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – defines the run id for this dag run</p></li>
-<li><p><strong>execution_date</strong> (<a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a>) – the execution date</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – database session</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the dag_id to find duplicates for</p></li>
+<li><p><strong>run_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- defines the run id for this dag run</p></li>
+<li><p><strong>execution_date</strong> (<a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a>) -- the execution date</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- database session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1158,8 +1158,8 @@ Defaults to False</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the task id</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – Sqlalchemy ORM Session</p></li>
+<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the task id</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- Sqlalchemy ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1203,8 +1203,8 @@ of its TaskInstances.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – Sqlalchemy ORM Session</p></li>
-<li><p><strong>execute_callbacks</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Should dag callbacks (success/failure, SLA etc) be invoked
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- Sqlalchemy ORM Session</p></li>
+<li><p><strong>execute_callbacks</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Should dag callbacks (success/failure, SLA etc) be invoked
 directly (default: true) or recorded as a pending request in the <code class="docutils literal notranslate"><span class="pre">callback</span></code> property</p></li>
 </ul>
 </dd>
@@ -1232,7 +1232,7 @@ needs to be executed</p>
 database yet. It will set state to removed or add the task if required.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – Sqlalchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- Sqlalchemy ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1244,9 +1244,9 @@ database yet. It will set state to removed or add the task if required.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – Sqlalchemy ORM Session</p></li>
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – DAG ID</p></li>
-<li><p><strong>execution_date</strong> (<a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a>) – execution date</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- Sqlalchemy ORM Session</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- DAG ID</p></li>
+<li><p><strong>execution_date</strong> (<a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a>) -- execution date</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1278,10 +1278,10 @@ if one exists. None otherwise.</p>
 <dt class="sig sig-object py" id="airflow.models.dagrun.DagRun.schedule_tis">
 <span class="sig-name descname"><span class="pre">schedule_tis</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">schedulable_tis</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">NEW_SESSION</span></span></em><span cla [...]
 <dd><p>Set the given task instances in to the scheduled state.</p>
-<p>Each element of <code class="docutils literal notranslate"><span class="pre">schedulable_tis</span></code> should have it’s <code class="docutils literal notranslate"><span class="pre">task</span></code> attribute already set.</p>
+<p>Each element of <code class="docutils literal notranslate"><span class="pre">schedulable_tis</span></code> should have it's <code class="docutils literal notranslate"><span class="pre">task</span></code> attribute already set.</p>
 <p>Any EmptyOperator without callbacks is instead set straight to the success state.</p>
-<p>All the TIs should belong to this DagRun, but this code is in the hot-path, this is not checked – it
-is the caller’s responsibility to call this function only with TIs from a single dag run.</p>
+<p>All the TIs should belong to this DagRun, but this code is in the hot-path, this is not checked -- it
+is the caller's responsibility to call this function only with TIs from a single dag run.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/mappedoperator/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/mappedoperator/index.html
index 1749243fe..6d6da4235 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/mappedoperator/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/mappedoperator/index.html
@@ -1041,7 +1041,7 @@
 <dl class="py class">
 <dt class="sig sig-object py" id="airflow.models.mappedoperator.OperatorPartial">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.models.mappedoperator.</span></span><span class="sig-name descname"><span class="pre">OperatorPartial</span></span><a class="reference internal" href="../../../../_modules/airflow/models/mappedoperator.html#OperatorPartial"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.mapped [...]
-<dd><p>An “intermediate state” returned by <code class="docutils literal notranslate"><span class="pre">BaseOperator.partial()</span></code>.</p>
+<dd><p>An &quot;intermediate state&quot; returned by <code class="docutils literal notranslate"><span class="pre">BaseOperator.partial()</span></code>.</p>
 <p>This only exists at DAG-parsing time; the only intended usage is for the
 user to call <code class="docutils literal notranslate"><span class="pre">.expand()</span></code> on it at some point (usually in a method chain) to
 create a <code class="docutils literal notranslate"><span class="pre">MappedOperator</span></code> to add into the DAG.</p>
@@ -1447,12 +1447,12 @@ create a <code class="docutils literal notranslate"><span class="pre">MappedOper
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.mappedoperator.MappedOperator.unmap">
 <span class="sig-name descname"><span class="pre">unmap</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">unmap_kwargs</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/mapped [...]
-<dd><p>Get the “normal” Operator after applying the current mapping.</p>
+<dd><p>Get the &quot;normal&quot; Operator after applying the current mapping.</p>
 <p>If <code class="docutils literal notranslate"><span class="pre">operator_class</span></code> is not a class (i.e. this DAG has been deserialized) then this will return a
-SerializedBaseOperator that aims to “look like” the real operator.</p>
+SerializedBaseOperator that aims to &quot;look like&quot; the real operator.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>unmap_kwargs</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – Override the args to pass to the Operator constructor. Only used when
+<dd class="field-odd"><p><strong>unmap_kwargs</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- Override the args to pass to the Operator constructor. Only used when
 <code class="docutils literal notranslate"><span class="pre">operator_class</span></code> is still an actual class.</p>
 </dd>
 </dl>
@@ -1489,8 +1489,8 @@ template fields on the <em>unmapped</em> BaseOperator.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Dict with values to apply on content</p></li>
-<li><p><strong>jinja_env</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment" title="(in Jinja v2.11.x)"><em>jinja2.Environment</em></a><em>]</em>) – Jinja environment</p></li>
+<li><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Dict with values to apply on content</p></li>
+<li><p><strong>jinja_env</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/api/#jinja2.Environment" title="(in Jinja v2.11.x)"><em>jinja2.Environment</em></a><em>]</em>) -- Jinja environment</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/param/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/param/index.html
index bf58cfb5a..eb5072aca 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/param/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/param/index.html
@@ -853,9 +853,9 @@ it always validates and returns the default value.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>default</strong> (<em>Any</em>) – The value this Param object holds</p></li>
-<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Optional help text for the Param</p></li>
-<li><p><strong>schema</strong> – The validation schema of the Param, if not given then all kwargs except
+<li><p><strong>default</strong> (<em>Any</em>) -- The value this Param object holds</p></li>
+<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Optional help text for the Param</p></li>
+<li><p><strong>schema</strong> -- The validation schema of the Param, if not given then all kwargs except
 default &amp; description will form the schema</p></li>
 </ul>
 </dd>
@@ -875,7 +875,7 @@ default &amp; description will form the schema</p></li>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.param.Param.resolve">
 <span class="sig-name descname"><span class="pre">resolve</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">value</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">NOTSET</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">suppress_exception</span></span><span class="o"><span c [...]
-<dd><p>Runs the validations and returns the Param’s final value.
+<dd><p>Runs the validations and returns the Param's final value.
 May raise ValueError on failed validations, or TypeError
 if no value is passed and no value already exists.
 We first check that value is json-serializable; if not, warn.
@@ -883,8 +883,8 @@ In future release we will require the value to be json-serializable.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>value</strong> (<em>Any</em>) – The value to be updated for the Param</p></li>
-<li><p><strong>suppress_exception</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – To raise an exception or not when the validations fails.
+<li><p><strong>value</strong> (<em>Any</em>) -- The value to be updated for the Param</p></li>
+<li><p><strong>suppress_exception</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- To raise an exception or not when the validations fails.
 If true and validations fails, the return value would be None.</p></li>
 </ul>
 </dd>
@@ -913,7 +913,7 @@ If true and validations fails, the return value would be None.</p></li>
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.models.param.</span></span><span class="sig-name descname"><span class="pre">ParamsDict</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">dict_obj</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em>, <em class="sig- [...]
 <dd><p>Bases: <code class="xref py py-obj docutils literal notranslate"><span class="pre">MutableMapping</span></code>[<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><code class="xref py py-obj docutils literal notranslate"><span class="pre">str</span></code></a>, <code class="xref py py-obj docutils literal notranslate"><span class="pre">Any</span></code>]</p>
 <p>Class to hold all params for dags or tasks. All the keys are strictly string and values
-are converted into Param’s object if they are not already. This class is to replace param’s
+are converted into Param's object if they are not already. This class is to replace param's
 dictionary implicitly and ideally not needed to be used directly.</p>
 <dl class="field-list simple">
 </dl>
@@ -965,13 +965,13 @@ dictionary implicitly and ideally not needed to be used directly.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.param.ParamsDict.__setitem__">
 <span class="sig-name descname"><span class="pre">__setitem__</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">key</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">value</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/param.html#ParamsDict.__setitem__"><span [...]
-<dd><p>Override for dictionary’s <code class="docutils literal notranslate"><span class="pre">setitem</span></code> method. This method make sure that all values are of
-Param’s type only.</p>
+<dd><p>Override for dictionary's <code class="docutils literal notranslate"><span class="pre">setitem</span></code> method. This method make sure that all values are of
+Param's type only.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – A key which needs to be inserted or updated in the dict</p></li>
-<li><p><strong>value</strong> (<em>Any</em>) – A value which needs to be set against the key. It could be of any
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- A key which needs to be inserted or updated in the dict</p></li>
+<li><p><strong>value</strong> (<em>Any</em>) -- A value which needs to be set against the key. It could be of any
 type but will be converted and stored as a Param object eventually.</p></li>
 </ul>
 </dd>
@@ -981,11 +981,11 @@ type but will be converted and stored as a Param object eventually.</p></li>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.param.ParamsDict.__getitem__">
 <span class="sig-name descname"><span class="pre">__getitem__</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">key</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/param.html#ParamsDict.__getitem__"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="heade [...]
-<dd><p>Override for dictionary’s <code class="docutils literal notranslate"><span class="pre">getitem</span></code> method. After fetching the key, it would call the
+<dd><p>Override for dictionary's <code class="docutils literal notranslate"><span class="pre">getitem</span></code> method. After fetching the key, it would call the
 resolve method as well on the Param object.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The key to fetch</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The key to fetch</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1001,13 +1001,13 @@ resolve method as well on the Param object.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.param.ParamsDict.items">
 <span class="sig-name descname"><span class="pre">items</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/param.html#ParamsDict.items"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.param.ParamsDict.items" title="Permalink to this definition">¶< [...]
-<dd><p>D.items() -&gt; a set-like object providing a view on D’s items</p>
+<dd><p>D.items() -&gt; a set-like object providing a view on D's items</p>
 </dd></dl>
 
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.param.ParamsDict.values">
 <span class="sig-name descname"><span class="pre">values</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/param.html#ParamsDict.values"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.param.ParamsDict.values" title="Permalink to this definition" [...]
-<dd><p>D.values() -&gt; an object providing a view on D’s values</p>
+<dd><p>D.values() -&gt; an object providing a view on D's values</p>
 </dd></dl>
 
 <dl class="py method">
@@ -1051,16 +1051,16 @@ when you trigger your DagRun.</p>
 <p><strong>Example</strong>:</p>
 <blockquote>
 <div><dl class="simple">
-<dt>with DAG(…) as dag:</dt><dd><p>EmailOperator(subject=dag.param(‘subject’, ‘Hi from Airflow!’))</p>
+<dt>with DAG(...) as dag:</dt><dd><p>EmailOperator(subject=dag.param('subject', 'Hi from Airflow!'))</p>
 </dd>
 </dl>
 </div></blockquote>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>current_dag</strong> (<a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a>) – Dag being used for parameter.</p></li>
-<li><p><strong>name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – key value which is used to set the parameter</p></li>
-<li><p><strong>default</strong> (<em>Any</em>) – Default value used if no parameter was set.</p></li>
+<li><p><strong>current_dag</strong> (<a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a>) -- Dag being used for parameter.</p></li>
+<li><p><strong>name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- key value which is used to set the parameter</p></li>
+<li><p><strong>default</strong> (<em>Any</em>) -- Default value used if no parameter was set.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/pool/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/pool/index.html
index 0a4f20cc0..ecca48c80 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/pool/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/pool/index.html
@@ -922,8 +922,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>pool_name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The pool name of the Pool to get.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p></li>
+<li><p><strong>pool_name</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The pool name of the Pool to get.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -938,7 +938,7 @@
 <dd><p>Get the Pool of the default_pool from the Pools.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>the pool object</p>
@@ -953,8 +953,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>id</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – pool id</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p></li>
+<li><p><strong>id</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- pool id</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -987,13 +987,13 @@
 <em class="property"><span class="pre">static</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">slots_stats</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">lock_rows</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">False</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span><span class="o"><span class [...]
 <dd><p>Get Pool stats (Number of Running, Queued, Open &amp; Total tasks)</p>
 <p>If <code class="docutils literal notranslate"><span class="pre">lock_rows</span></code> is True, and the database engine in use supports the <code class="docutils literal notranslate"><span class="pre">NOWAIT</span></code> syntax, then a
-non-blocking lock will be attempted – if the lock is not available then SQLAlchemy will throw an
+non-blocking lock will be attempted -- if the lock is not available then SQLAlchemy will throw an
 OperationalError.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>lock_rows</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Should we attempt to obtain a row-level lock on all the Pool rows returns</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p></li>
+<li><p><strong>lock_rows</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Should we attempt to obtain a row-level lock on all the Pool rows returns</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1016,7 +1016,7 @@ OperationalError.</p>
 <dd><p>Get the number of slots used by running/queued tasks at the moment.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>the used number of slots</p>
@@ -1030,7 +1030,7 @@ OperationalError.</p>
 <dd><p>Get the number of slots used by running tasks at the moment.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>the used number of slots</p>
@@ -1044,7 +1044,7 @@ OperationalError.</p>
 <dd><p>Get the number of slots used by queued tasks at the moment.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>the used number of slots</p>
@@ -1058,7 +1058,7 @@ OperationalError.</p>
 <dd><p>Get the number of slots open at the moment.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>the number of slots</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/renderedtifields/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/renderedtifields/index.html
index 70b58c54d..3c6df74e7 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/renderedtifields/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/renderedtifields/index.html
@@ -893,8 +893,8 @@ table.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>ti</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) – Task Instance</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SqlAlchemy Session</p></li>
+<li><p><strong>ti</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) -- Task Instance</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SqlAlchemy Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -914,8 +914,8 @@ table.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>ti</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) – Task Instance</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SqlAlchemy Session</p></li>
+<li><p><strong>ti</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><em>airflow.models.taskinstance.TaskInstance</em></a>) -- Task Instance</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SqlAlchemy Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -933,7 +933,7 @@ table.</p>
 <dd><p>Write instance to database</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SqlAlchemy Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SqlAlchemy Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -943,14 +943,14 @@ table.</p>
 <em class="property"><span class="pre">classmethod</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">delete_old_records</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">cls</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">task_id</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">dag_id</span></span></em>, <em class="sig-param"><span class="n"><span c [...]
 <dd><p>Keep only Last X (num_to_keep) number of records for a task by deleting others.</p>
 <p>In the case of data for a mapped task either all of the rows or none of the rows will be deleted, so
-we don’t end up with partial data for a set of mapped Task Instances left in the database.</p>
+we don't end up with partial data for a set of mapped Task Instances left in the database.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Task ID</p></li>
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Dag ID</p></li>
-<li><p><strong>num_to_keep</strong> – Number of Records to keep</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SqlAlchemy Session</p></li>
+<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Task ID</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Dag ID</p></li>
+<li><p><strong>num_to_keep</strong> -- Number of Records to keep</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SqlAlchemy Session</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/sensorinstance/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/sensorinstance/index.html
index fab2bdb05..4421be236 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/sensorinstance/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/sensorinstance/index.html
@@ -933,7 +933,7 @@ Every smart sensor process takes care of tasks whose <cite>shardcode</cite> are
 <dd><p>Get the object dotted class path. Used for getting operator classpath.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>obj</strong> – </p>
+<dd class="field-odd"><p><strong>obj</strong> -- </p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>The class path of input object</p>
@@ -952,11 +952,11 @@ context used for a sensor and set the sensor_instance table state to sensing.</p
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>ti</strong> – The task instance for the sensor to be registered.</p></li>
-<li><p><strong>poke_context</strong> – Context used for sensor poke function.</p></li>
-<li><p><strong>execution_context</strong> – Context used for execute sensor such as timeout
+<li><p><strong>ti</strong> -- The task instance for the sensor to be registered.</p></li>
+<li><p><strong>poke_context</strong> -- Context used for sensor poke function.</p></li>
+<li><p><strong>execution_context</strong> -- Context used for execute sensor such as timeout
 setting and email configuration.</p></li>
-<li><p><strong>session</strong> – SQLAlchemy ORM Session</p></li>
+<li><p><strong>session</strong> -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -988,7 +988,7 @@ database, in all other cases this will be incremented.</p>
 <dd><p>Returns the DagRun for this SensorInstance</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>DagRun</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/serialized_dag/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/serialized_dag/index.html
index e82c2393d..f27b12872 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/serialized_dag/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/serialized_dag/index.html
@@ -943,9 +943,9 @@ changed, it updates the record, ignores otherwise.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag</strong> (<a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a>) – a DAG to be written into database</p></li>
-<li><p><strong>min_update_interval</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – minimal interval in seconds to update serialized DAG</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dag</strong> (<a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a>) -- a DAG to be written into database</p></li>
+<li><p><strong>min_update_interval</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- minimal interval in seconds to update serialized DAG</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -963,7 +963,7 @@ changed, it updates the record, ignores otherwise.</p>
 <dd><p>Reads all DAGs in serialized_dag table.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>a dict of DAGs read from database</p>
@@ -1002,8 +1002,8 @@ changed, it updates the record, ignores otherwise.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>alive_dag_filelocs</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – file paths of alive DAGs</p></li>
-<li><p><strong>session</strong> – ORM Session</p></li>
+<li><p><strong>alive_dag_filelocs</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- file paths of alive DAGs</p></li>
+<li><p><strong>session</strong> -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1016,8 +1016,8 @@ changed, it updates the record, ignores otherwise.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the DAG to check</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the DAG to check</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1032,8 +1032,8 @@ root dag_id from the DAG table.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the DAG to fetch</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the DAG to fetch</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1047,8 +1047,8 @@ DAG is saved in a separate database query.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dags</strong> (<em>List</em><em>[</em><a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a><em>]</em>) – the DAG objects to save to the DB</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dags</strong> (<em>List</em><em>[</em><a class="reference internal" href="../dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a><em>]</em>) -- the DAG objects to save to the DB</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1065,8 +1065,8 @@ in serialized_dag table</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – DAG ID</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- DAG ID</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1078,7 +1078,7 @@ in serialized_dag table</p>
 <dd><p>Get the maximum date when any DAG was last updated in serialized_dag table</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1090,8 +1090,8 @@ in serialized_dag table</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – DAG ID</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p></li>
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- DAG ID</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1109,7 +1109,7 @@ in serialized_dag table</p>
 <dd><p>Get the dependencies between DAGs</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/skipmixin/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/skipmixin/index.html
index 65ec7111c..713178dec 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/skipmixin/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/skipmixin/index.html
@@ -847,10 +847,10 @@ are cleared.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_run</strong> (<a class="reference internal" href="../dagrun/index.html#airflow.models.dagrun.DagRun" title="airflow.models.dagrun.DagRun"><em>airflow.models.dagrun.DagRun</em></a>) – the DagRun for which to set the tasks to skipped</p></li>
-<li><p><strong>execution_date</strong> (<em>pendulum.DateTime</em>) – execution_date</p></li>
-<li><p><strong>tasks</strong> (<em>Sequence</em><em>[</em><a class="reference internal" href="../baseoperator/index.html#airflow.models.baseoperator.BaseOperator" title="airflow.models.baseoperator.BaseOperator"><em>airflow.models.baseoperator.BaseOperator</em></a><em>]</em>) – tasks to skip (not task_ids)</p></li>
-<li><p><strong>session</strong> (<em>sqlalchemy.Session</em>) – db session to use</p></li>
+<li><p><strong>dag_run</strong> (<a class="reference internal" href="../dagrun/index.html#airflow.models.dagrun.DagRun" title="airflow.models.dagrun.DagRun"><em>airflow.models.dagrun.DagRun</em></a>) -- the DagRun for which to set the tasks to skipped</p></li>
+<li><p><strong>execution_date</strong> (<em>pendulum.DateTime</em>) -- execution_date</p></li>
+<li><p><strong>tasks</strong> (<em>Sequence</em><em>[</em><a class="reference internal" href="../baseoperator/index.html#airflow.models.baseoperator.BaseOperator" title="airflow.models.baseoperator.BaseOperator"><em>airflow.models.baseoperator.BaseOperator</em></a><em>]</em>) -- tasks to skip (not task_ids)</p></li>
+<li><p><strong>session</strong> (<em>sqlalchemy.Session</em>) -- db session to use</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskinstance/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskinstance/index.html
index e8410d5f0..e8de533e7 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskinstance/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskinstance/index.html
@@ -1112,12 +1112,12 @@ get killed.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>tis</strong> – a list of task instances</p></li>
-<li><p><strong>session</strong> – current session</p></li>
-<li><p><strong>dag_run_state</strong> (<em>Union</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>, </em><em>airflow.typing_compat.Literal</em><em>[</em><em>False</em><em>]</em><em>]</em>) – state to set DagRun to. If set to False, dagrun state will not
+<li><p><strong>tis</strong> -- a list of task instances</p></li>
+<li><p><strong>session</strong> -- current session</p></li>
+<li><p><strong>dag_run_state</strong> (<em>Union</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>, </em><em>airflow.typing_compat.Literal</em><em>[</em><em>False</em><em>]</em><em>]</em>) -- state to set DagRun to. If set to False, dagrun state will not
 be changed.</p></li>
-<li><p><strong>dag</strong> – DAG object</p></li>
-<li><p><strong>activate_dag_runs</strong> – Deprecated parameter, do not pass</p></li>
+<li><p><strong>dag</strong> -- DAG object</p></li>
+<li><p><strong>activate_dag_runs</strong> -- Deprecated parameter, do not pass</p></li>
 </ul>
 </dd>
 </dl>
@@ -1195,10 +1195,10 @@ be changed.</p></li>
 <p>Task instances store the state of a task instance. This table is the
 authority and single source of truth around what tasks have run and the
 state they are in.</p>
-<p>The SqlAlchemy model doesn’t have a SqlAlchemy foreign key to the task or
+<p>The SqlAlchemy model doesn't have a SqlAlchemy foreign key to the task or
 dag model deliberately to have more control over transactions.</p>
 <p>Database transactions on this table should insure double triggers and
-any confusion around what task instances are or aren’t ready to run
+any confusion around what task instances are or aren't ready to run
 even while multiple schedulers may be firing task instances.</p>
 <p>A value of -1 in map_index represents any of: a TI without mapped tasks;
 a TI with mapped tasks that has yet to be expanded (state=pending);
@@ -1385,7 +1385,7 @@ a TI with mapped tasks that expanded to an empty list (state=skipped).</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskinstance.TaskInstance.init_on_load">
 <span class="sig-name descname"><span class="pre">init_on_load</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskinstance.html#TaskInstance.init_on_load"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.taskinstance.TaskInstance.init_on_load"  [...]
-<dd><p>Initialize the attributes that aren’t stored in the DB</p>
+<dd><p>Initialize the attributes that aren't stored in the DB</p>
 </dd></dl>
 
 <dl class="py method">
@@ -1400,7 +1400,7 @@ database, in all other cases this will be incremented.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskinstance.TaskInstance.prev_attempted_tries">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">prev_attempted_tries</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskinstance.html#TaskInstance.prev_attempted_tries"><span class="viewcode-link"><span class="pre">[source]</s [...]
-<dd><p>Based on this instance’s try_number, this will calculate
+<dd><p>Based on this instance's try_number, this will calculate
 the number of previously attempted tries, defaulting to 0.</p>
 </dd></dl>
 
@@ -1425,25 +1425,25 @@ the orchestrator.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – DAG ID</p></li>
-<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Task ID</p></li>
-<li><p><strong>run_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The run_id of this task’s DagRun</p></li>
-<li><p><strong>mark_success</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether to mark the task as successful</p></li>
-<li><p><strong>ignore_all_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ignore all ignorable dependencies.
+<li><p><strong>dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- DAG ID</p></li>
+<li><p><strong>task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Task ID</p></li>
+<li><p><strong>run_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The run_id of this task's DagRun</p></li>
+<li><p><strong>mark_success</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether to mark the task as successful</p></li>
+<li><p><strong>ignore_all_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ignore all ignorable dependencies.
 Overrides the other ignore_* parameters.</p></li>
-<li><p><strong>ignore_depends_on_past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ignore depends_on_past parameter of DAGs
+<li><p><strong>ignore_depends_on_past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ignore depends_on_past parameter of DAGs
 (e.g. for Backfills)</p></li>
-<li><p><strong>ignore_task_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ignore task-specific dependencies such as depends_on_past
+<li><p><strong>ignore_task_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ignore task-specific dependencies such as depends_on_past
 and trigger rule</p></li>
-<li><p><strong>ignore_ti_state</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ignore the task instance’s previous failure/success</p></li>
-<li><p><strong>local</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether to run the task locally</p></li>
-<li><p><strong>pickle_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – If the DAG was serialized to the DB, the ID
+<li><p><strong>ignore_ti_state</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ignore the task instance's previous failure/success</p></li>
+<li><p><strong>local</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether to run the task locally</p></li>
+<li><p><strong>pickle_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- If the DAG was serialized to the DB, the ID
 associated with the pickled DAG</p></li>
-<li><p><strong>file_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – path to the file containing the DAG definition</p></li>
-<li><p><strong>raw</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – raw mode (needs more details)</p></li>
-<li><p><strong>job_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – job ID (needs more details)</p></li>
-<li><p><strong>pool</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the Airflow pool that the task should run in</p></li>
-<li><p><strong>cfg_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the Path to the configuration file</p></li>
+<li><p><strong>file_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- path to the file containing the DAG definition</p></li>
+<li><p><strong>raw</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- raw mode (needs more details)</p></li>
+<li><p><strong>job_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- job ID (needs more details)</p></li>
+<li><p><strong>pool</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the Airflow pool that the task should run in</p></li>
+<li><p><strong>cfg_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the Path to the configuration file</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1475,7 +1475,7 @@ we use and looking up the state becomes part of the session, otherwise
 a new session is used.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> -- SQLAlchemy ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1483,10 +1483,10 @@ a new session is used.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskinstance.TaskInstance.error">
 <span class="sig-name descname"><span class="pre">error</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">NEW_SESSION</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/task [...]
-<dd><p>Forces the task instance’s state to FAILED in the database.</p>
+<dd><p>Forces the task instance's state to FAILED in the database.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> -- SQLAlchemy ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1498,8 +1498,8 @@ a new session is used.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>session</strong> – SQLAlchemy ORM Session</p></li>
-<li><p><strong>lock_for_update</strong> – if True, indicates that the database should
+<li><p><strong>session</strong> -- SQLAlchemy ORM Session</p></li>
+<li><p><strong>lock_for_update</strong> -- if True, indicates that the database should
 lock the TaskInstance (issuing a FOR UPDATE clause) until the
 session is committed.</p></li>
 </ul>
@@ -1514,8 +1514,8 @@ session is committed.</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>task</strong> (<em>airflow.models.operator.Operator</em>) – The task object to copy from</p></li>
-<li><p><strong>pool_override</strong> – Use the pool_override instead of task’s pool</p></li>
+<li><p><strong>task</strong> (<em>airflow.models.operator.Operator</em>) -- The task object to copy from</p></li>
+<li><p><strong>pool_override</strong> -- Use the pool_override instead of task's pool</p></li>
 </ul>
 </dd>
 </dl>
@@ -1530,7 +1530,7 @@ run are removed. If the task is mapped, only the one with matching map
 index is removed.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1550,8 +1550,8 @@ index is removed.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>state</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – State to set for the TI</p></li>
-<li><p><strong>session</strong> – SQLAlchemy ORM Session</p></li>
+<li><p><strong>state</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- State to set for the TI</p></li>
+<li><p><strong>session</strong> -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1574,7 +1574,7 @@ schedule of a task until the dependents are done. For instance,
 if the task DROPs and recreates a table.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> -- SQLAlchemy ORM Session</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1582,12 +1582,12 @@ if the task DROPs and recreates a table.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskinstance.TaskInstance.get_previous_dagrun">
 <span class="sig-name descname"><span class="pre">get_previous_dagrun</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">state</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">None</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">session</span></span><span class="o"><span cl [...]
-<dd><p>The DagRun that ran before this task instance’s DagRun.</p>
+<dd><p>The DagRun that ran before this task instance's DagRun.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) – If passed, it only take into account instances of a specific state.</p></li>
-<li><p><strong>session</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a><em>]</em>) – SQLAlchemy ORM Session.</p></li>
+<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) -- If passed, it only take into account instances of a specific state.</p></li>
+<li><p><strong>session</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a><em>]</em>) -- SQLAlchemy ORM Session.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1600,8 +1600,8 @@ if the task DROPs and recreates a table.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) – If passed, it only take into account instances of a specific state.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p></li>
+<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) -- If passed, it only take into account instances of a specific state.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1630,8 +1630,8 @@ Please use <cite>airflow.models.taskinstance.TaskInstance.get_previous_ti</cite>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) – If passed, it only take into account instances of a specific state.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p></li>
+<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) -- If passed, it only take into account instances of a specific state.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1644,8 +1644,8 @@ Please use <cite>airflow.models.taskinstance.TaskInstance.get_previous_ti</cite>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) – If passed, it only take into account instances of a specific state.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p></li>
+<li><p><strong>state</strong> (<em>Optional</em><em>[</em><em>airflow.utils.state.DagRunState</em><em>]</em>) -- If passed, it only take into account instances of a specific state.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -1669,10 +1669,10 @@ the UI will ignore some dependencies).</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dep_context</strong> – The execution context that determines the dependencies that
+<li><p><strong>dep_context</strong> -- The execution context that determines the dependencies that
 should be evaluated.</p></li>
-<li><p><strong>session</strong> – database session</p></li>
-<li><p><strong>verbose</strong> – whether log details on failed dependencies on
+<li><p><strong>session</strong> -- database session</p></li>
+<li><p><strong>verbose</strong> -- whether log details on failed dependencies on
 info or debug log level</p></li>
 </ul>
 </dd>
@@ -1711,7 +1711,7 @@ to be retried.</p>
 <dd><p>Returns the DagRun for this TaskInstance</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – SQLAlchemy ORM Session</p>
+<dd class="field-odd"><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- SQLAlchemy ORM Session</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>DagRun</p>
@@ -1731,17 +1731,17 @@ executed, in preparation for _run_raw_task</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>verbose</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – whether to turn on more verbose logging</p></li>
-<li><p><strong>ignore_all_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ignore all of the non-critical dependencies, just runs</p></li>
-<li><p><strong>ignore_depends_on_past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Ignore depends_on_past DAG attribute</p></li>
-<li><p><strong>ignore_task_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Don’t check the dependencies of this TaskInstance’s task</p></li>
-<li><p><strong>ignore_ti_state</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Disregards previous task instance state</p></li>
-<li><p><strong>mark_success</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Don’t run the task, mark its state as success</p></li>
-<li><p><strong>test_mode</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Doesn’t record success or failure in the DB</p></li>
-<li><p><strong>job_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Job (BackfillJob / LocalTaskJob / SchedulerJob) ID</p></li>
-<li><p><strong>pool</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – specifies the pool to use to run the task instance</p></li>
-<li><p><strong>external_executor_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The identifier of the celery executor</p></li>
-<li><p><strong>session</strong> – SQLAlchemy ORM Session</p></li>
+<li><p><strong>verbose</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- whether to turn on more verbose logging</p></li>
+<li><p><strong>ignore_all_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ignore all of the non-critical dependencies, just runs</p></li>
+<li><p><strong>ignore_depends_on_past</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Ignore depends_on_past DAG attribute</p></li>
+<li><p><strong>ignore_task_deps</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Don't check the dependencies of this TaskInstance's task</p></li>
+<li><p><strong>ignore_ti_state</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Disregards previous task instance state</p></li>
+<li><p><strong>mark_success</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Don't run the task, mark its state as success</p></li>
+<li><p><strong>test_mode</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Doesn't record success or failure in the DB</p></li>
+<li><p><strong>job_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Job (BackfillJob / LocalTaskJob / SchedulerJob) ID</p></li>
+<li><p><strong>pool</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- specifies the pool to use to run the task instance</p></li>
+<li><p><strong>external_executor_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The identifier of the celery executor</p></li>
+<li><p><strong>session</strong> -- SQLAlchemy ORM Session</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -1779,8 +1779,8 @@ executed, in preparation for _run_raw_task</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>error</strong> (<a class="reference external" href="https://docs.python.org/3/library/exceptions.html#BaseException" title="(in Python v3.10)"><em>BaseException</em></a>) – exception to get traceback from</p></li>
-<li><p><strong>truncate_to</strong> (<em>Callable</em>) – Function to truncate TB to. Must have a <code class="docutils literal notranslate"><span class="pre">__code__</span></code> attribute</p></li>
+<li><p><strong>error</strong> (<a class="reference external" href="https://docs.python.org/3/library/exceptions.html#BaseException" title="(in Python v3.10)"><em>BaseException</em></a>) -- exception to get traceback from</p></li>
+<li><p><strong>truncate_to</strong> (<em>Callable</em>) -- Function to truncate TB to. Must have a <code class="docutils literal notranslate"><span class="pre">__code__</span></code> attribute</p></li>
 </ul>
 </dd>
 </dl>
@@ -1885,11 +1885,11 @@ before replacement is returned.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Key to store the value under.</p></li>
-<li><p><strong>value</strong> (<em>Any</em>) – Value to store. What types are possible depends on whether
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Key to store the value under.</p></li>
+<li><p><strong>value</strong> (<em>Any</em>) -- Value to store. What types are possible depends on whether
 <code class="docutils literal notranslate"><span class="pre">enable_xcom_pickling</span></code> is true or not. If so, this can be any
 picklable object; only be JSON-serializable may be used otherwise.</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – Deprecated parameter that has no effect.</p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- Deprecated parameter that has no effect.</p></li>
 </ul>
 </dd>
 </dl>
@@ -1902,19 +1902,19 @@ picklable object; only be JSON-serializable may be used otherwise.</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – A key for the XCom. If provided, only XComs with matching
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- A key for the XCom. If provided, only XComs with matching
 keys will be returned. The default key is <code class="docutils literal notranslate"><span class="pre">'return_value'</span></code>, also
 available as constant <code class="docutils literal notranslate"><span class="pre">XCOM_RETURN_KEY</span></code>. This key is automatically
 given to XComs returned by tasks (as opposed to being pushed
 manually). To remove the filter, pass <em>None</em>.</p></li>
-<li><p><strong>task_ids</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) – Only XComs from tasks with matching ids will be
+<li><p><strong>task_ids</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) -- Only XComs from tasks with matching ids will be
 pulled. Pass <em>None</em> to remove the filter.</p></li>
-<li><p><strong>dag_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – If provided, only pulls XComs from this DAG. If <em>None</em>
+<li><p><strong>dag_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- If provided, only pulls XComs from this DAG. If <em>None</em>
 (default), the DAG of the calling task is used.</p></li>
-<li><p><strong>map_indexes</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em><em>]</em><em>]</em>) – If provided, only pull XComs with matching indexes.
+<li><p><strong>map_indexes</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em><em>]</em><em>]</em>) -- If provided, only pull XComs with matching indexes.
 If <em>None</em> (default), this is inferred from the task(s) being pulled
 (see below for details).</p></li>
-<li><p><strong>include_prior_dates</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If False, only XComs from the current
+<li><p><strong>include_prior_dates</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If False, only XComs from the current
 execution_date are returned. If <em>True</em>, XComs from previous dates
 are returned as well.</p></li>
 </ul>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/tasklog/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/tasklog/index.html
index 0be6e466f..48b843787 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/tasklog/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/tasklog/index.html
@@ -803,7 +803,7 @@
 <dd><p>Bases: <a class="reference internal" href="../base/index.html#airflow.models.base.Base" title="airflow.models.base.Base"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.base.Base</span></code></a></p>
 <p>Changes to <code class="docutils literal notranslate"><span class="pre">log_filename_template</span></code> and <code class="docutils literal notranslate"><span class="pre">elasticsearch_id</span></code>.</p>
 <p>This table is automatically populated when Airflow starts up, to store the
-config’s value if it does not match the last row in the table.</p>
+config's value if it does not match the last row in the table.</p>
 <dl class="py attribute">
 <dt class="sig sig-object py" id="airflow.models.tasklog.LogTemplate.__tablename__">
 <span class="sig-name descname"><span class="pre">__tablename__</span></span><em class="property"><span class="w"> </span><span class="pre">=</span> <span class="pre">log_template</span></em><a class="reference internal" href="../../../../_modules/airflow/models/tasklog.html#LogTemplate.__tablename__"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.tasklog.LogTemplate.__tablename__" title="Permalink to this definition">¶ [...]
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmap/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmap/index.html
index c84aa380b..874449f4d 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmap/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmap/index.html
@@ -844,7 +844,7 @@ ordered value sequence).</p>
 <dd><p>Bases: <a class="reference internal" href="../base/index.html#airflow.models.base.Base" title="airflow.models.base.Base"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.base.Base</span></code></a></p>
 <p>Model to track dynamic task-mapping information.</p>
 <p>This is currently only populated by an upstream TaskInstance pushing an
-XCom that’s pulled by a downstream for mapping purposes.</p>
+XCom that's pulled by a downstream for mapping purposes.</p>
 <dl class="field-list simple">
 </dl>
 <dl class="py attribute">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmixin/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmixin/index.html
index 50fac6a1c..b42a7b9f9 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmixin/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskmixin/index.html
@@ -876,8 +876,8 @@
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DependencyMixin.roots">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">roots</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DependencyMixin.roots"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="heade [...]
-<dd><p>List of root nodes – ones with no upstream dependencies.</p>
-<p>a.k.a. the “start” of this sub-graph</p>
+<dd><p>List of root nodes -- ones with no upstream dependencies.</p>
+<p>a.k.a. the &quot;start&quot; of this sub-graph</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -885,8 +885,8 @@
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DependencyMixin.leaves">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">leaves</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DependencyMixin.leaves"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="hea [...]
-<dd><p>List of leaf nodes – ones with only upstream dependencies.</p>
-<p>a.k.a. the “end” of this sub-graph</p>
+<dd><p>List of leaf nodes -- ones with only upstream dependencies.</p>
+<p>a.k.a. the &quot;end&quot; of this sub-graph</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -935,7 +935,7 @@ Override if necessary.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DependencyMixin.__rrshift__">
 <span class="sig-name descname"><span class="pre">__rrshift__</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">other</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DependencyMixin.__rrshift__"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a c [...]
-<dd><p>Called for Task &gt;&gt; [Task] because list don’t have __rshift__ operators.</p>
+<dd><p>Called for Task &gt;&gt; [Task] because list don't have __rshift__ operators.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -943,7 +943,7 @@ Override if necessary.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DependencyMixin.__rlshift__">
 <span class="sig-name descname"><span class="pre">__rlshift__</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">other</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DependencyMixin.__rlshift__"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a c [...]
-<dd><p>Called for Task &lt;&lt; [Task] because list don’t have __lshift__ operators.</p>
+<dd><p>Called for Task &lt;&lt; [Task] because list don't have __lshift__ operators.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -969,7 +969,7 @@ Override if necessary.</p>
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DAGNode">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.models.taskmixin.</span></span><span class="sig-name descname"><span class="pre">DAGNode</span></span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DAGNode"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.models.taskmixin.DAGNode" title="Permal [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><code class="xref py py-obj docutils literal notranslate"><span class="pre">DependencyMixin</span></code></a></p>
-<p>A base class for a node in the graph of a workflow – an Operator or a Task Group, either mapped or
+<p>A base class for a node in the graph of a workflow -- an Operator or a Task Group, either mapped or
 unmapped.</p>
 <dl class="py attribute">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DAGNode.dag">
@@ -1041,8 +1041,8 @@ unmapped.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DAGNode.roots">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">roots</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DAGNode.roots"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" h [...]
-<dd><p>List of root nodes – ones with no upstream dependencies.</p>
-<p>a.k.a. the “start” of this sub-graph</p>
+<dd><p>List of root nodes -- ones with no upstream dependencies.</p>
+<p>a.k.a. the &quot;start&quot; of this sub-graph</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -1050,8 +1050,8 @@ unmapped.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DAGNode.leaves">
 <em class="property"><span class="pre">property</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">leaves</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DAGNode.leaves"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" [...]
-<dd><p>List of leaf nodes – ones with only upstream dependencies.</p>
-<p>a.k.a. the “end” of this sub-graph</p>
+<dd><p>List of leaf nodes -- ones with only upstream dependencies.</p>
+<p>a.k.a. the &quot;end&quot; of this sub-graph</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -1109,7 +1109,7 @@ downstream.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.taskmixin.DAGNode.serialize_for_task_group">
 <em class="property"><span class="pre">abstract</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">serialize_for_task_group</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/taskmixin.html#DAGNode.serialize_for_task_group"><span class="viewcode-link"><span class="pre">[source]</s [...]
-<dd><p>This is used by SerializedTaskGroup to serialize a task group’s content.</p>
+<dd><p>This is used by SerializedTaskGroup to serialize a task group's content.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -1121,7 +1121,7 @@ downstream.</p>
 <p>For now, this walks the entire DAG to find mapped nodes that has this
 current task as an upstream. We cannot use <code class="docutils literal notranslate"><span class="pre">downstream_list</span></code> since it
 only contains operators, not task groups. In the future, we should
-provide a way to record an DAG node’s all downstream nodes instead.</p>
+provide a way to record an DAG node's all downstream nodes instead.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskreschedule/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskreschedule/index.html
index 1754110a6..fb601553f 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskreschedule/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/taskreschedule/index.html
@@ -902,10 +902,10 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>session</strong> – the database session object</p></li>
-<li><p><strong>task_instance</strong> – the task instance to find task reschedules for</p></li>
-<li><p><strong>descending</strong> – If True then records are returned in descending order</p></li>
-<li><p><strong>try_number</strong> – Look for TaskReschedule of the given try_number. Default is None which
+<li><p><strong>session</strong> -- the database session object</p></li>
+<li><p><strong>task_instance</strong> -- the task instance to find task reschedules for</p></li>
+<li><p><strong>descending</strong> -- If True then records are returned in descending order</p></li>
+<li><p><strong>try_number</strong> -- Look for TaskReschedule of the given try_number. Default is None which
 looks for the same try_number of the given task_instance.</p></li>
 </ul>
 </dd>
@@ -920,9 +920,9 @@ in ascending order.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>session</strong> – the database session object</p></li>
-<li><p><strong>task_instance</strong> – the task instance to find task reschedules for</p></li>
-<li><p><strong>try_number</strong> – Look for TaskReschedule of the given try_number. Default is None which
+<li><p><strong>session</strong> -- the database session object</p></li>
+<li><p><strong>task_instance</strong> -- the task instance to find task reschedules for</p></li>
+<li><p><strong>try_number</strong> -- Look for TaskReschedule of the given try_number. Default is None which
 looks for the same try_number of the given task_instance.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/trigger/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/trigger/index.html
index af6285518..7384e3bd1 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/trigger/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/trigger/index.html
@@ -819,7 +819,7 @@
 other Triggers, and fire off events that will unpause deferred Tasks,
 start linked DAGs, etc.</p>
 <p>They are persisted into the database and then re-hydrated into a
-“triggerer” process, where many are run at once. We model it so that
+&quot;triggerer&quot; process, where many are run at once. We model it so that
 there is a many-to-one relationship between Task and Trigger, for future
 deduplication logic to use.</p>
 <p>Rows will be evicted from the database when the triggerer detects no
@@ -903,7 +903,7 @@ the runtime code understands as immediate-fail, and pack the error into
 next_kwargs.</p>
 <p>TODO: Once we have shifted callback (and email) handling to run on
 workers as first-class concepts, we can run the failure code here
-in-process, but we can’t do that right now.</p>
+in-process, but we can't do that right now.</p>
 </dd></dl>
 
 <dl class="py method">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/variable/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/variable/index.html
index 2b74b3fab..572ca5dae 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/variable/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/variable/index.html
@@ -908,14 +908,14 @@ as a simple key value store within Airflow.</p>
 <dt class="sig sig-object py" id="airflow.models.variable.Variable.setdefault">
 <em class="property"><span class="pre">classmethod</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">setdefault</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">cls</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">key</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">default</span></span></em>, <em class="sig-param"><span class="n"><span class="pre"> [...]
 <dd><p>Like a Python builtin dict object, setdefault returns the current value
-for a key, and if it isn’t there, stores the default value and returns it.</p>
+for a key, and if it isn't there, stores the default value and returns it.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> – Dict key for this Variable</p></li>
-<li><p><strong>default</strong> – Default value to set and return if the variable
-isn’t already in the DB</p></li>
-<li><p><strong>deserialize_json</strong> – Store this as a JSON encoded value in the DB
+<li><p><strong>key</strong> -- Dict key for this Variable</p></li>
+<li><p><strong>default</strong> -- Default value to set and return if the variable
+isn't already in the DB</p></li>
+<li><p><strong>deserialize_json</strong> -- Store this as a JSON encoded value in the DB
 and un-encode it when retrieving a value</p></li>
 </ul>
 </dd>
@@ -932,9 +932,9 @@ and un-encode it when retrieving a value</p></li>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p></li>
-<li><p><strong>default_var</strong> (<em>Any</em>) – Default value of the Variable if the Variable doesn’t exist</p></li>
-<li><p><strong>deserialize_json</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Deserialize the value to a Python dict</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p></li>
+<li><p><strong>default_var</strong> (<em>Any</em>) -- Default value of the Variable if the Variable doesn't exist</p></li>
+<li><p><strong>deserialize_json</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Deserialize the value to a Python dict</p></li>
 </ul>
 </dd>
 </dl>
@@ -948,11 +948,11 @@ This operation will overwrite an existing variable.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p></li>
-<li><p><strong>value</strong> (<em>Any</em>) – Value to set for the Variable</p></li>
-<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Description of the Variable</p></li>
-<li><p><strong>serialize_json</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Serialize the value to a JSON string</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SQL Alchemy Sessions</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p></li>
+<li><p><strong>value</strong> (<em>Any</em>) -- Value to set for the Variable</p></li>
+<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Description of the Variable</p></li>
+<li><p><strong>serialize_json</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Serialize the value to a JSON string</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SQL Alchemy Sessions</p></li>
 </ul>
 </dd>
 </dl>
@@ -965,10 +965,10 @@ This operation will overwrite an existing variable.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p></li>
-<li><p><strong>value</strong> (<em>Any</em>) – Value to set for the Variable</p></li>
-<li><p><strong>serialize_json</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Serialize the value to a JSON string</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SQL Alchemy Session</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p></li>
+<li><p><strong>value</strong> (<em>Any</em>) -- Value to set for the Variable</p></li>
+<li><p><strong>serialize_json</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Serialize the value to a JSON string</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SQL Alchemy Session</p></li>
 </ul>
 </dd>
 </dl>
@@ -981,8 +981,8 @@ This operation will overwrite an existing variable.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – SQL Alchemy Sessions</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- SQL Alchemy Sessions</p></li>
 </ul>
 </dd>
 </dl>
@@ -1003,7 +1003,7 @@ exists in an environment variable or custom secrets backend, then
 subsequent reads will not read the set value.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p>
 </dd>
 </dl>
 </dd></dl>
@@ -1014,7 +1014,7 @@ subsequent reads will not read the set value.</p>
 <dd><p>Get Airflow Variable by iterating over all Secret Backends.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>Variable Value</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom/index.html
index f0abcc01b..13f82f756 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom/index.html
@@ -971,18 +971,18 @@ i.e automatically deserialize Xcom value when loading from DB.</p>
 <dt class="sig sig-object py" id="airflow.models.xcom.BaseXCom.get_value">
 <em class="property"><span class="pre">classmethod</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">get_value</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">cls</span></span></em>, <em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">ti_key</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">key< [...]
 <dd><p>Retrieve an XCom value for a task instance.</p>
-<p>This method returns “full” XCom values (i.e. uses <code class="docutils literal notranslate"><span class="pre">deserialize_value</span></code>
-from the XCom backend). Use <code class="xref py py-meth docutils literal notranslate"><span class="pre">get_many()</span></code> if you want the “shortened”
+<p>This method returns &quot;full&quot; XCom values (i.e. uses <code class="docutils literal notranslate"><span class="pre">deserialize_value</span></code>
+from the XCom backend). Use <code class="xref py py-meth docutils literal notranslate"><span class="pre">get_many()</span></code> if you want the &quot;shortened&quot;
 value via <code class="docutils literal notranslate"><span class="pre">orm_deserialize_value</span></code>.</p>
 <p>If there are no results, <em>None</em> is returned. If multiple XCom entries
 match the criteria, an arbitrary one is returned.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>ti_key</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – The TaskInstanceKey to look up the XCom for.</p></li>
-<li><p><strong>key</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – A key for the XCom. If provided, only XCom with matching
+<li><p><strong>ti_key</strong> (<a class="reference internal" href="../taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- The TaskInstanceKey to look up the XCom for.</p></li>
+<li><p><strong>key</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- A key for the XCom. If provided, only XCom with matching
 keys will be returned. Pass <em>None</em> (default) to remove the filter.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) – Database session. If not given, a new session will be
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.Session</em></a>) -- Database session. If not given, a new session will be
 created for this function.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom_arg/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom_arg/index.html
index 95b4000af..f4823fc8e 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom_arg/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/models/xcom_arg/index.html
@@ -812,7 +812,7 @@
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.models.xcom_arg.</span></span><span class="sig-name descname"><span class="pre">XComArg</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">operator</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">key</span></span><span class="o"><span class="pre">=</span></span><span  [...]
 <dd><p>Bases: <a class="reference internal" href="../taskmixin/index.html#airflow.models.taskmixin.DependencyMixin" title="airflow.models.taskmixin.DependencyMixin"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.taskmixin.DependencyMixin</span></code></a></p>
 <p>Class that represents a XCom push from a previous operator.
-Defaults to “return_value” as only key.</p>
+Defaults to &quot;return_value&quot; as only key.</p>
 <dl class="simple">
 <dt>Current implementation supports</dt><dd><p>xcomarg &gt;&gt; op
 xcomarg &lt;&lt; op
@@ -840,8 +840,8 @@ op &lt;&lt; xcomarg   (by BaseOperator code)</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>operator</strong> (<em>airflow.models.operator.Operator</em>) – operator to which the XComArg belongs to</p></li>
-<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – key value which is used for xcom_pull (key in the XCom table)</p></li>
+<li><p><strong>operator</strong> (<em>airflow.models.operator.Operator</em>) -- operator to which the XComArg belongs to</p></li>
+<li><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- key value which is used for xcom_pull (key in the XCom table)</p></li>
 </ul>
 </dd>
 </dl>
@@ -854,7 +854,7 @@ op &lt;&lt; xcomarg   (by BaseOperator code)</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.models.xcom_arg.XComArg.__getitem__">
 <span class="sig-name descname"><span class="pre">__getitem__</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">self</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">item</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/xcom_arg.html#XComArg.__getitem__"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="head [...]
-<dd><p>Implements xcomresult[‘some_result_key’]</p>
+<dd><p>Implements xcomresult['some_result_key']</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -942,7 +942,7 @@ collection objects, and instances with <code class="docutils literal notranslate
 <dt class="sig sig-object py" id="airflow.models.xcom_arg.XComArg.apply_upstream_relationship">
 <em class="property"><span class="pre">static</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">apply_upstream_relationship</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">op</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">arg</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/models/xcom_arg.html#XComArg.apply [...]
 <dd><p>Set dependency for XComArgs.</p>
-<p>This looks for XComArg objects in <code class="docutils literal notranslate"><span class="pre">arg</span></code> “deeply” (looking inside
+<p>This looks for XComArg objects in <code class="docutils literal notranslate"><span class="pre">arg</span></code> &quot;deeply&quot; (looking inside
 collections objects and classes decorated with <code class="docutils literal notranslate"><span class="pre">template_fields</span></code>), and
 sets the relationship to <code class="docutils literal notranslate"><span class="pre">op</span></code> on any found.</p>
 <dl class="field-list simple">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/bash/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/bash/index.html
index 54ab9d3cb..c89c24851 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/bash/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/bash/index.html
@@ -862,21 +862,21 @@ will also be pushed to an XCom when the bash command completes</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>bash_command</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The command, set of commands or reference to a
-bash script (must be ‘.sh’) to be executed. (templated)</p></li>
-<li><p><strong>env</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – If env is not None, it must be a dict that defines the
+<li><p><strong>bash_command</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The command, set of commands or reference to a
+bash script (must be '.sh') to be executed. (templated)</p></li>
+<li><p><strong>env</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- If env is not None, it must be a dict that defines the
 environment variables for the new process; these are used instead
 of inheriting the current process environment, which is the default
 behavior. (templated)</p></li>
-<li><p><strong>append_env</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If False(default) uses the environment variables passed in env params
+<li><p><strong>append_env</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If False(default) uses the environment variables passed in env params
 and does not inherit the current process environment. If True, inherits the environment variables
 from current passes and then environment variable passed by the user will either update the existing
 inherited environment variables or the new variables gets appended to it</p></li>
-<li><p><strong>output_encoding</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Output encoding of bash command</p></li>
-<li><p><strong>skip_exit_code</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – If task exits with this exit code, leave the task
+<li><p><strong>output_encoding</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Output encoding of bash command</p></li>
+<li><p><strong>skip_exit_code</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- If task exits with this exit code, leave the task
 in <code class="docutils literal notranslate"><span class="pre">skipped</span></code> state (default: 99). If set to <code class="docutils literal notranslate"><span class="pre">None</span></code>, any non-zero
 exit code will be treated as a failure.</p></li>
-<li><p><strong>cwd</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Working directory to execute the command in.
+<li><p><strong>cwd</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Working directory to execute the command in.
 If None (default), the command is run in a temporary directory.</p></li>
 </ul>
 </dd>
@@ -915,22 +915,22 @@ addressing this is to prefix the command with <code class="docutils literal notr
 <p>Example:
 .. code-block:: python</p>
 <blockquote>
-<div><p>bash_command = “set -e; python3 script.py ‘{{ next_execution_date }}’”</p>
+<div><p>bash_command = &quot;set -e; python3 script.py '{{ next_execution_date }}'&quot;</p>
 </div></blockquote>
 </div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Add a space after the script name when directly calling a <code class="docutils literal notranslate"><span class="pre">.sh</span></code> script with the
-<code class="docutils literal notranslate"><span class="pre">bash_command</span></code> argument – for example <code class="docutils literal notranslate"><span class="pre">bash_command=&quot;my_script.sh</span> <span class="pre">&quot;</span></code>.  This
+<code class="docutils literal notranslate"><span class="pre">bash_command</span></code> argument -- for example <code class="docutils literal notranslate"><span class="pre">bash_command=&quot;my_script.sh</span> <span class="pre">&quot;</span></code>.  This
 is because Airflow tries to apply load this file and process it as a Jinja template to
 it ends with <code class="docutils literal notranslate"><span class="pre">.sh</span></code>, which will likely not be what most users want.</p>
 </div>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
-<p>Care should be taken with “user” input or when using Jinja templates in the
+<p>Care should be taken with &quot;user&quot; input or when using Jinja templates in the
 <code class="docutils literal notranslate"><span class="pre">bash_command</span></code>, as this bash operator does not perform any escaping or
 sanitization of the command.</p>
-<p>This applies mostly to using “dag_run” conf, as that can be submitted via
+<p>This applies mostly to using &quot;dag_run&quot; conf, as that can be submitted via
 users in the Web UI. Most of the default template variables are not at
 risk.</p>
 </div>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/branch/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/branch/index.html
index 0cda923f7..b2ba6a6df 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/branch/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/branch/index.html
@@ -858,7 +858,7 @@ necessary to choose a branch and returning a task_id or list of
 task_ids.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Context dictionary as passed to execute()</p>
+<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Context dictionary as passed to execute()</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/datetime/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/datetime/index.html
index b64f4ec7d..7d9479ac2 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/datetime/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/datetime/index.html
@@ -863,14 +863,14 @@ For more information on how to use this operator, take a look at the guide:
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>follow_task_ids_if_true</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – task id or task ids to follow if
+<li><p><strong>follow_task_ids_if_true</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- task id or task ids to follow if
 <code class="docutils literal notranslate"><span class="pre">datetime.datetime.now()</span></code> falls above target_lower and below <code class="docutils literal notranslate"><span class="pre">target_upper</span></code>.</p></li>
-<li><p><strong>follow_task_ids_if_false</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – task id or task ids to follow if
+<li><p><strong>follow_task_ids_if_false</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- task id or task ids to follow if
 <code class="docutils literal notranslate"><span class="pre">datetime.datetime.now()</span></code> falls below target_lower or above <code class="docutils literal notranslate"><span class="pre">target_upper</span></code>.</p></li>
-<li><p><strong>target_lower</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.time" title="(in Python v3.10)"><em>datetime.time</em></a><em>, </em><em>None</em><em>]</em>) – target lower bound.</p></li>
-<li><p><strong>target_upper</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.time" title="(in Python v3.10)"><em>datetime.time</em></a><em>, </em><em>None</em><em>]</em>) – target upper bound.</p></li>
-<li><p><strong>use_task_execution_date</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If <code class="docutils literal notranslate"><span class="pre">True</span></code>, uses task’s execution day to compare with targets.
-Execution date is useful for backfilling. If <code class="docutils literal notranslate"><span class="pre">False</span></code>, uses system’s date.</p></li>
+<li><p><strong>target_lower</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.time" title="(in Python v3.10)"><em>datetime.time</em></a><em>, </em><em>None</em><em>]</em>) -- target lower bound.</p></li>
+<li><p><strong>target_upper</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.time" title="(in Python v3.10)"><em>datetime.time</em></a><em>, </em><em>None</em><em>]</em>) -- target upper bound.</p></li>
+<li><p><strong>use_task_execution_date</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If <code class="docutils literal notranslate"><span class="pre">True</span></code>, uses task's execution day to compare with targets.
+Execution date is useful for backfilling. If <code class="docutils literal notranslate"><span class="pre">False</span></code>, uses system's date.</p></li>
 </ul>
 </dd>
 </dl>
@@ -882,7 +882,7 @@ necessary to choose a branch and returning a task_id or list of
 task_ids.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Context dictionary as passed to execute()</p>
+<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Context dictionary as passed to execute()</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/email/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/email/index.html
index 0a0f42e2c..bf4731838 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/email/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/email/index.html
@@ -849,17 +849,17 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>to</strong> (<em>Union</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – list of emails to send the email to. (templated)</p></li>
-<li><p><strong>subject</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – subject line for the email. (templated)</p></li>
-<li><p><strong>html_content</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – content of the email, html markup
+<li><p><strong>to</strong> (<em>Union</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- list of emails to send the email to. (templated)</p></li>
+<li><p><strong>subject</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- subject line for the email. (templated)</p></li>
+<li><p><strong>html_content</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- content of the email, html markup
 is allowed. (templated)</p></li>
-<li><p><strong>files</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) – file names to attach in email (templated)</p></li>
-<li><p><strong>cc</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – list of recipients to be added in CC field</p></li>
-<li><p><strong>bcc</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – list of recipients to be added in BCC field</p></li>
-<li><p><strong>mime_subtype</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – MIME sub content type</p></li>
-<li><p><strong>mime_charset</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – character set parameter added to the Content-Type
+<li><p><strong>files</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) -- file names to attach in email (templated)</p></li>
+<li><p><strong>cc</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- list of recipients to be added in CC field</p></li>
+<li><p><strong>bcc</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- list of recipients to be added in BCC field</p></li>
+<li><p><strong>mime_subtype</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- MIME sub content type</p></li>
+<li><p><strong>mime_charset</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- character set parameter added to the Content-Type
 header.</p></li>
-<li><p><strong>custom_headers</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – additional headers to add to the MIME message.</p></li>
+<li><p><strong>custom_headers</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- additional headers to add to the MIME message.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/generic_transfer/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/generic_transfer/index.html
index d4dad47ba..27cee0e81 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/generic_transfer/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/generic_transfer/index.html
@@ -853,13 +853,13 @@ needs to expose a <cite>get_records</cite> method, and the destination a
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – SQL query to execute against the source database. (templated)</p></li>
-<li><p><strong>destination_table</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – target table. (templated)</p></li>
-<li><p><strong>source_conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – source connection</p></li>
-<li><p><strong>destination_conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – destination connection</p></li>
-<li><p><strong>preoperator</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) – sql statement or list of statements to be
+<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- SQL query to execute against the source database. (templated)</p></li>
+<li><p><strong>destination_table</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- target table. (templated)</p></li>
+<li><p><strong>source_conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- source connection</p></li>
+<li><p><strong>destination_conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- destination connection</p></li>
+<li><p><strong>preoperator</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em><em>]</em>) -- sql statement or list of statements to be
 executed prior to loading the data. (templated)</p></li>
-<li><p><strong>insert_args</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#dict" title="(in Python v3.10)"><em>dict</em></a><em>]</em>) – extra params for <cite>insert_rows</cite> method.</p></li>
+<li><p><strong>insert_args</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#dict" title="(in Python v3.10)"><em>dict</em></a><em>]</em>) -- extra params for <cite>insert_rows</cite> method.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/latest_only/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/latest_only/index.html
index 571f282f1..4120a69b6 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/latest_only/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/latest_only/index.html
@@ -862,7 +862,7 @@ necessary to choose a branch and returning a task_id or list of
 task_ids.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Context dictionary as passed to execute()</p>
+<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Context dictionary as passed to execute()</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/python/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/python/index.html
index 8a61d10f3..900ef8c27 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/python/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/python/index.html
@@ -934,12 +934,12 @@ def my_task()</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>python_callable</strong> (<em>Optional</em><em>[</em><em>Callable</em><em>]</em>) – A reference to an object that is callable</p></li>
-<li><p><strong>op_kwargs</strong> – a dictionary of keyword arguments that will get unpacked
+<li><p><strong>python_callable</strong> (<em>Optional</em><em>[</em><em>Callable</em><em>]</em>) -- A reference to an object that is callable</p></li>
+<li><p><strong>op_kwargs</strong> -- a dictionary of keyword arguments that will get unpacked
 in your function (templated)</p></li>
-<li><p><strong>op_args</strong> – a list of positional arguments that will get unpacked when
+<li><p><strong>op_args</strong> -- a list of positional arguments that will get unpacked when
 calling your callable (templated)</p></li>
-<li><p><strong>multiple_outputs</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) – if set, function return value will be
+<li><p><strong>multiple_outputs</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a><em>]</em>) -- if set, function return value will be
 unrolled to multiple XCom values. Dict will unroll to xcom values with keys as keys.
 Defaults to False.</p></li>
 </ul>
@@ -979,18 +979,18 @@ the values of <code class="docutils literal notranslate"><span class="pre">ti</s
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>python_callable</strong> (<em>Callable</em>) – A reference to an object that is callable</p></li>
-<li><p><strong>op_kwargs</strong> (<em>Optional</em><em>[</em><em>Mapping</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – a dictionary of keyword arguments that will get unpacked
+<li><p><strong>python_callable</strong> (<em>Callable</em>) -- A reference to an object that is callable</p></li>
+<li><p><strong>op_kwargs</strong> (<em>Optional</em><em>[</em><em>Mapping</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- a dictionary of keyword arguments that will get unpacked
 in your function</p></li>
-<li><p><strong>op_args</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><em>Any</em><em>]</em><em>]</em>) – a list of positional arguments that will get unpacked when
+<li><p><strong>op_args</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><em>Any</em><em>]</em><em>]</em>) -- a list of positional arguments that will get unpacked when
 calling your callable</p></li>
-<li><p><strong>templates_dict</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – a dictionary where the values are templates that
+<li><p><strong>templates_dict</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- a dictionary where the values are templates that
 will get templated by the Airflow engine sometime between
 <code class="docutils literal notranslate"><span class="pre">__init__</span></code> and <code class="docutils literal notranslate"><span class="pre">execute</span></code> takes place and are made available
-in your callable’s context after the template has been applied. (templated)</p></li>
-<li><p><strong>templates_exts</strong> (<em>Optional</em><em>[</em><em>Sequence</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – a list of file extensions to resolve while
+in your callable's context after the template has been applied. (templated)</p></li>
+<li><p><strong>templates_exts</strong> (<em>Optional</em><em>[</em><em>Sequence</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- a list of file extensions to resolve while
 processing templated fields, for examples <code class="docutils literal notranslate"><span class="pre">['.sql',</span> <span class="pre">'.hql']</span></code></p></li>
-<li><p><strong>show_return_value_in_logs</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – a bool value whether to show return_value
+<li><p><strong>show_return_value_in_logs</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- a bool value whether to show return_value
 logs. Defaults to True, which allows return value log output.
 It can be set to False to prevent log output of return value when you return huge data
 such as transmission a large amount of XCom to TaskAPI.</p></li>
@@ -1064,14 +1064,14 @@ Context is the same dictionary used as when rendering jinja templates.</p>
 <dt class="sig sig-object py" id="airflow.operators.python.BranchPythonOperator">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.operators.python.</span></span><span class="sig-name descname"><span class="pre">BranchPythonOperator</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">python_callable</span></span></em>, <em class="sig-param"><span c [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.operators.python.PythonOperator" title="airflow.operators.python.PythonOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">PythonOperator</span></code></a>, <a class="reference internal" href="../../models/skipmixin/index.html#airflow.models.skipmixin.SkipMixin" title="airflow.models.skipmixin.SkipMixin"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.sk [...]
-<p>Allows a workflow to “branch” or follow a path following the execution
+<p>Allows a workflow to &quot;branch&quot; or follow a path following the execution
 of this task.</p>
 <p>It derives the PythonOperator and expects a Python function that returns
 a single task_id or list of task_ids to follow. The task_id(s) returned
-should point to a task directly downstream from {self}. All other “branches”
+should point to a task directly downstream from {self}. All other &quot;branches&quot;
 or directly downstream tasks are marked with a state of <code class="docutils literal notranslate"><span class="pre">skipped</span></code> so that
-these paths can’t move forward. The <code class="docutils literal notranslate"><span class="pre">skipped</span></code> states are propagated
-downstream to allow for the DAG state to fill up and the DAG run’s state
+these paths can't move forward. The <code class="docutils literal notranslate"><span class="pre">skipped</span></code> states are propagated
+downstream to allow for the DAG state to fill up and the DAG run's state
 to be inferred.</p>
 <dl class="field-list simple">
 </dl>
@@ -1094,7 +1094,7 @@ Context is the same dictionary used as when rendering jinja templates.</p>
 <p>Allows a pipeline to continue based on the result of a <code class="docutils literal notranslate"><span class="pre">python_callable</span></code>.</p>
 <p>The ShortCircuitOperator is derived from the PythonOperator and evaluates the result of a
 <code class="docutils literal notranslate"><span class="pre">python_callable</span></code>. If the returned result is False or a falsy value, the pipeline will be
-short-circuited. Downstream tasks will be marked with a state of “skipped” based on the short-circuiting
+short-circuited. Downstream tasks will be marked with a state of &quot;skipped&quot; based on the short-circuiting
 mode configured. If the returned result is True or a truthy value, downstream tasks proceed as normal and
 an <code class="docutils literal notranslate"><span class="pre">XCom</span></code> of the returned result is pushed.</p>
 <p>The short-circuiting can be configured to either respect or ignore the <code class="docutils literal notranslate"><span class="pre">trigger_rule</span></code> set for
@@ -1110,7 +1110,7 @@ tasks were purposely meant to be skipped but perhaps not other subsequent tasks.
 </div>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>ignore_downstream_trigger_rules</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If set to True, all downstream tasks from this operator task will
+<dd class="field-odd"><p><strong>ignore_downstream_trigger_rules</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If set to True, all downstream tasks from this operator task will
 be skipped. This is the default behavior. If set to False, the direct, downstream task(s) will be
 skipped but the <code class="docutils literal notranslate"><span class="pre">trigger_rule</span></code> defined for a other downstream tasks will be respected.</p>
 </dd>
@@ -1150,30 +1150,30 @@ Airflow through plugins. You can use string_args though.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>python_callable</strong> (<em>Callable</em>) – A python function with no references to outside variables,
+<li><p><strong>python_callable</strong> (<em>Callable</em>) -- A python function with no references to outside variables,
 defined with def, which will be run in a virtualenv</p></li>
-<li><p><strong>requirements</strong> (<em>Union</em><em>[</em><em>None</em><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – Either a list of requirement strings, or a (templated)
-“requirements file” as specified by pip.</p></li>
-<li><p><strong>python_version</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10) [...]
+<li><p><strong>requirements</strong> (<em>Union</em><em>[</em><em>None</em><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>, </em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- Either a list of requirement strings, or a (templated)
+&quot;requirements file&quot; as specified by pip.</p></li>
+<li><p><strong>python_version</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10) [...]
 both 2 and 2.7 are acceptable forms.</p></li>
-<li><p><strong>use_dill</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether to use dill to serialize
+<li><p><strong>use_dill</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether to use dill to serialize
 the args and result (pickle is default). This allow more complex types
 but requires you to include dill in your requirements.</p></li>
-<li><p><strong>system_site_packages</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether to include
+<li><p><strong>system_site_packages</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether to include
 system_site_packages in your virtualenv.
 See virtualenv documentation for more information.</p></li>
-<li><p><strong>pip_install_options</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – a list of pip install options when installing requirements
-See ‘pip install -h’ for available options</p></li>
-<li><p><strong>op_args</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><em>Any</em><em>]</em><em>]</em>) – A list of positional arguments to pass to python_callable.</p></li>
-<li><p><strong>op_kwargs</strong> (<em>Optional</em><em>[</em><em>Mapping</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – A dict of keyword arguments to pass to python_callable.</p></li>
-<li><p><strong>string_args</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – Strings that are present in the global var virtualenv_string_args,
+<li><p><strong>pip_install_options</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- a list of pip install options when installing requirements
+See 'pip install -h' for available options</p></li>
+<li><p><strong>op_args</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><em>Any</em><em>]</em><em>]</em>) -- A list of positional arguments to pass to python_callable.</p></li>
+<li><p><strong>op_kwargs</strong> (<em>Optional</em><em>[</em><em>Mapping</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- A dict of keyword arguments to pass to python_callable.</p></li>
+<li><p><strong>string_args</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- Strings that are present in the global var virtualenv_string_args,
 available to python_callable at runtime as a list[str]. Note that args are split
 by newline.</p></li>
-<li><p><strong>templates_dict</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – a dictionary where the values are templates that
+<li><p><strong>templates_dict</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- a dictionary where the values are templates that
 will get templated by the Airflow engine sometime between
 <code class="docutils literal notranslate"><span class="pre">__init__</span></code> and <code class="docutils literal notranslate"><span class="pre">execute</span></code> takes place and are made available
-in your callable’s context after the template has been applied</p></li>
-<li><p><strong>templates_exts</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – a list of file extensions to resolve while
+in your callable's context after the template has been applied</p></li>
+<li><p><strong>templates_exts</strong> (<em>Optional</em><em>[</em><em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- a list of file extensions to resolve while
 processing templated fields, for examples <code class="docutils literal notranslate"><span class="pre">['.sql',</span> <span class="pre">'.hql']</span></code></p></li>
 </ul>
 </dd>
@@ -1254,7 +1254,7 @@ max_depth on deepcopy operations.</p>
 <dt class="sig sig-object py" id="airflow.operators.python.get_current_context">
 <span class="sig-prename descclassname"><span class="pre">airflow.operators.python.</span></span><span class="sig-name descname"><span class="pre">get_current_context</span></span><span class="sig-paren">(</span><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/operators/python.html#get_current_context"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.operators.python.get_current_co [...]
 <dd><p>Obtain the execution context for the currently executing operator without
-altering user method’s signature.
+altering user method's signature.
 This is the simplest method of retrieving the execution context dictionary.</p>
 <p><strong>Old style:</strong></p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">my_task</span><span class="p">(</span><span class="o">**</span><span class="n">context</span><span class="p">):</span>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/smooth/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/smooth/index.html
index 565cd233a..c833a2efd 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/smooth/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/smooth/index.html
@@ -842,7 +842,7 @@
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.operators.smooth.</span></span><span class="sig-name descname"><span class="pre">SmoothOperator</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">**</span></span><span class="n"><span class="pre">kwargs</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../ [...]
 <dd><p>Bases: <a class="reference internal" href="../../models/baseoperator/index.html#airflow.models.baseoperator.BaseOperator" title="airflow.models.baseoperator.BaseOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.baseoperator.BaseOperator</span></code></a></p>
 <p>Operator that does literally nothing but it logs YouTube link to
-Sade song “Smooth Operator”.</p>
+Sade song &quot;Smooth Operator&quot;.</p>
 <dl class="py attribute">
 <dt class="sig sig-object py" id="airflow.operators.smooth.SmoothOperator.ui_color">
 <span class="sig-name descname"><span class="pre">ui_color</span></span><em class="property"><span class="w"> </span><span class="pre">=</span> <span class="pre">#e8f7e4</span></em><a class="reference internal" href="../../../../_modules/airflow/operators/smooth.html#SmoothOperator.ui_color"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.operators.smooth.SmoothOperator.ui_color" title="Permalink to this definition">¶</a></dt>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/sql/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/sql/index.html
index b44254cfb..b7d6f91ac 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/sql/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/sql/index.html
@@ -1008,8 +1008,8 @@ values return <code class="docutils literal notranslate"><span class="pre">False
 <p>Given a query like <code class="docutils literal notranslate"><span class="pre">SELECT</span> <span class="pre">COUNT(*)</span> <span class="pre">FROM</span> <span class="pre">foo</span></code>, it will fail only if
 the count <code class="docutils literal notranslate"><span class="pre">==</span> <span class="pre">0</span></code>. You can craft much more complex query that could,
 for instance, check that the table has the same number of rows as
-the source table upstream, or that the count of today’s partition is
-greater than yesterday’s partition, or that a set of metrics are less
+the source table upstream, or that the count of today's partition is
+greater than yesterday's partition, or that a set of metrics are less
 than 3 standard deviation for the 7 day average.</p>
 <p>This operator can be used as a data quality check in your pipeline, and
 depending on where you put it in your DAG, you have the choice to
@@ -1019,9 +1019,9 @@ without stopping the progress of the DAG.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the sql to be executed. (templated)</p></li>
-<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the connection ID used to connect to the database.</p></li>
-<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of database which overwrite the defined one in connection</p></li>
+<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the sql to be executed. (templated)</p></li>
+<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the connection ID used to connect to the database.</p></li>
+<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of database which overwrite the defined one in connection</p></li>
 </ul>
 </dd>
 </dl>
@@ -1065,9 +1065,9 @@ Context is the same dictionary used as when rendering jinja templates.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the sql to be executed. (templated)</p></li>
-<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the connection ID used to connect to the database.</p></li>
-<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of database which overwrite the defined one in connection</p></li>
+<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the sql to be executed. (templated)</p></li>
+<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the connection ID used to connect to the database.</p></li>
+<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of database which overwrite the defined one in connection</p></li>
 </ul>
 </dd>
 </dl>
@@ -1115,21 +1115,21 @@ a certain tolerance of the ones from days_back before.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>table</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the table name</p></li>
-<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the connection ID used to connect to the database.</p></li>
-<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of database which will overwrite the defined one in connection</p></li>
-<li><p><strong>days_back</strong> (<em>SupportsAbs</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – number of days between ds and the ds we want to check
+<li><p><strong>table</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the table name</p></li>
+<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the connection ID used to connect to the database.</p></li>
+<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of database which will overwrite the defined one in connection</p></li>
+<li><p><strong>days_back</strong> (<em>SupportsAbs</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- number of days between ds and the ds we want to check
 against. Defaults to 7 days</p></li>
-<li><p><strong>date_filter_column</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The column name for the dates to filter on. Defaults to ‘ds’</p></li>
-<li><p><strong>ratio_formula</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – <p>which formula to use to compute the ratio between
+<li><p><strong>date_filter_column</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The column name for the dates to filter on. Defaults to 'ds'</p></li>
+<li><p><strong>ratio_formula</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- <p>which formula to use to compute the ratio between
 the two metrics. Assuming cur is the metric of today and ref is
 the metric to today - days_back.</p>
 <p>max_over_min: computes max(cur, ref) / min(cur, ref)
 relative_diff: computes abs(cur-ref) / ref</p>
-<p>Default: ‘max_over_min’</p>
+<p>Default: 'max_over_min'</p>
 </p></li>
-<li><p><strong>ignore_zero</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – whether we should ignore zero metrics</p></li>
-<li><p><strong>metrics_thresholds</strong> (<em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) – a dictionary of ratios indexed by metrics</p></li>
+<li><p><strong>ignore_zero</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- whether we should ignore zero metrics</p></li>
+<li><p><strong>metrics_thresholds</strong> (<em>Dict</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a><em>]</em>) -- a dictionary of ratios indexed by metrics</p></li>
 </ul>
 </dd>
 </dl>
@@ -1183,11 +1183,11 @@ value OR a sql statement that results a numeric.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the sql to be executed. (templated)</p></li>
-<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – the connection ID used to connect to the database.</p></li>
-<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of database which overwrite the defined one in connection</p></li>
-<li><p><strong>min_threshold</strong> (<em>Any</em>) – numerical value or min threshold sql to be executed (templated)</p></li>
-<li><p><strong>max_threshold</strong> (<em>Any</em>) – numerical value or max threshold sql to be executed (templated)</p></li>
+<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the sql to be executed. (templated)</p></li>
+<li><p><strong>conn_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- the connection ID used to connect to the database.</p></li>
+<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of database which overwrite the defined one in connection</p></li>
+<li><p><strong>min_threshold</strong> (<em>Any</em>) -- numerical value or min threshold sql to be executed (templated)</p></li>
+<li><p><strong>max_threshold</strong> (<em>Any</em>) -- numerical value or max threshold sql to be executed (templated)</p></li>
 </ul>
 </dd>
 </dl>
@@ -1227,19 +1227,19 @@ Default functionality will log metadata.</p>
 <dt class="sig sig-object py" id="airflow.operators.sql.BranchSQLOperator">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.operators.sql.</span></span><span class="sig-name descname"><span class="pre">BranchSQLOperator</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">sql</span></span></em>, <em class="sig-param"><span class="n"><span cla [...]
 <dd><p>Bases: <a class="reference internal" href="#airflow.operators.sql.BaseSQLOperator" title="airflow.operators.sql.BaseSQLOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">BaseSQLOperator</span></code></a>, <code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.models.SkipMixin</span></code></p>
-<p>Allows a DAG to “branch” or follow a specified path based on the results of a SQL query.</p>
+<p>Allows a DAG to &quot;branch&quot; or follow a specified path based on the results of a SQL query.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The SQL code to be executed, should return true or false (templated)
-Template reference are recognized by str ending in ‘.sql’.
+<li><p><strong>sql</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The SQL code to be executed, should return true or false (templated)
+Template reference are recognized by str ending in '.sql'.
 Expected SQL query to return Boolean (True/False), integer (0 = False, Otherwise = 1)
 or string (true/y/yes/1/on/false/n/no/0/off).</p></li>
-<li><p><strong>follow_task_ids_if_true</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – task id or task ids to follow if query returns true</p></li>
-<li><p><strong>follow_task_ids_if_false</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – task id or task ids to follow if query returns false</p></li>
-<li><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the connection ID used to connect to the database.</p></li>
-<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – name of database which overwrite the defined one in connection</p></li>
-<li><p><strong>parameters</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><em>Mapping</em><em>, </em><em>Iterable</em><em>]</em><em>]</em>) – (optional) the parameters to render the SQL query with.</p></li>
+<li><p><strong>follow_task_ids_if_true</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- task id or task ids to follow if query returns true</p></li>
+<li><p><strong>follow_task_ids_if_false</strong> (<em>List</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- task id or task ids to follow if query returns false</p></li>
+<li><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the connection ID used to connect to the database.</p></li>
+<li><p><strong>database</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- name of database which overwrite the defined one in connection</p></li>
+<li><p><strong>parameters</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><em>Mapping</em><em>, </em><em>Iterable</em><em>]</em><em>]</em>) -- (optional) the parameters to render the SQL query with.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/subdag/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/subdag/index.html
index 40d6ce1db..22b0bc380 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/subdag/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/subdag/index.html
@@ -862,7 +862,7 @@ The module which provides a way to nest your DAGs and so your levels of complexi
 <dt class="sig sig-object py" id="airflow.operators.subdag.SkippedStatePropagationOptions">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.operators.subdag.</span></span><span class="sig-name descname"><span class="pre">SkippedStatePropagationOptions</span></span><a class="reference internal" href="../../../../_modules/airflow/operators/subdag.html#SkippedStatePropagationOptions"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#a [...]
 <dd><p>Bases: <a class="reference external" href="https://docs.python.org/3/library/enum.html#enum.Enum" title="(in Python v3.10)"><code class="xref py py-obj docutils literal notranslate"><span class="pre">enum.Enum</span></code></a></p>
-<p>Available options for skipped state propagation of subdag’s tasks to parent dag tasks.</p>
+<p>Available options for skipped state propagation of subdag's tasks to parent dag tasks.</p>
 <dl class="py attribute">
 <dt class="sig sig-object py" id="airflow.operators.subdag.SkippedStatePropagationOptions.ALL_LEAVES">
 <span class="sig-name descname"><span class="pre">ALL_LEAVES</span></span><em class="property"><span class="w"> </span><span class="pre">=</span> <span class="pre">all_leaves</span></em><a class="reference internal" href="../../../../_modules/airflow/operators/subdag.html#SkippedStatePropagationOptions.ALL_LEAVES"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.operators.subdag.SkippedStatePropagationOptions.ALL_LEAVES" title=" [...]
@@ -881,7 +881,7 @@ The module which provides a way to nest your DAGs and so your levels of complexi
 <dd><p>Bases: <a class="reference internal" href="../../sensors/base/index.html#airflow.sensors.base.BaseSensorOperator" title="airflow.sensors.base.BaseSensorOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.sensors.base.BaseSensorOperator</span></code></a></p>
 <p>This class is deprecated.
 Please use <cite>airflow.utils.task_group.TaskGroup</cite>.</p>
-<p>This runs a sub dag. By convention, a sub dag’s dag_id
+<p>This runs a sub dag. By convention, a sub dag's dag_id
 should be prefixed by its parent and a dot. As in <cite>parent.child</cite>.
 Although SubDagOperator can occupy a pool/concurrency slot,
 user can specify the mode=reschedule so that the slot will be
@@ -889,12 +889,12 @@ released periodically to avoid potential deadlock.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>subdag</strong> (<a class="reference internal" href="../../models/dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a>) – the DAG object to run as a subdag of the current DAG.</p></li>
-<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) – sqlalchemy session</p></li>
-<li><p><strong>conf</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – Configuration for the subdag</p></li>
-<li><p><strong>propagate_skipped_state</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="#airflow.operators.subdag.SkippedStatePropagationOptions" title="airflow.operators.subdag.SkippedStatePropagationOptions"><em>SkippedStatePropagationOptions</em></a><em>]</em>) – by setting this argument you can define
+<li><p><strong>subdag</strong> (<a class="reference internal" href="../../models/dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><em>airflow.models.dag.DAG</em></a>) -- the DAG object to run as a subdag of the current DAG.</p></li>
+<li><p><strong>session</strong> (<a class="reference external" href="https://docs.sqlalchemy.org/en/latest/orm/session_api.html#sqlalchemy.orm.Session" title="(in SQLAlchemy v1.4)"><em>sqlalchemy.orm.session.Session</em></a>) -- sqlalchemy session</p></li>
+<li><p><strong>conf</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- Configuration for the subdag</p></li>
+<li><p><strong>propagate_skipped_state</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="#airflow.operators.subdag.SkippedStatePropagationOptions" title="airflow.operators.subdag.SkippedStatePropagationOptions"><em>SkippedStatePropagationOptions</em></a><em>]</em>) -- by setting this argument you can define
 whether the skipped state of leaf task(s) should be propagated to the
-parent dag’s downstream task.</p></li>
+parent dag's downstream task.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/trigger_dagrun/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/trigger_dagrun/index.html
index ff5bca313..77f32603b 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/trigger_dagrun/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/trigger_dagrun/index.html
@@ -907,8 +907,8 @@ supported at runtime but is deprecated.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>operator</strong> (<a class="reference internal" href="../../models/abstractoperator/index.html#airflow.models.abstractoperator.AbstractOperator" title="airflow.models.abstractoperator.AbstractOperator"><em>airflow.models.abstractoperator.AbstractOperator</em></a>) – airflow operator</p></li>
-<li><p><strong>ti_key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) – TaskInstance ID to return link for</p></li>
+<li><p><strong>operator</strong> (<a class="reference internal" href="../../models/abstractoperator/index.html#airflow.models.abstractoperator.AbstractOperator" title="airflow.models.abstractoperator.AbstractOperator"><em>airflow.models.abstractoperator.AbstractOperator</em></a>) -- airflow operator</p></li>
+<li><p><strong>ti_key</strong> (<a class="reference internal" href="../../models/taskinstance/index.html#airflow.models.taskinstance.TaskInstanceKey" title="airflow.models.taskinstance.TaskInstanceKey"><em>airflow.models.taskinstance.TaskInstanceKey</em></a>) -- TaskInstance ID to return link for</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -930,20 +930,20 @@ supported at runtime but is deprecated.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>trigger_dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The dag_id to trigger (templated).</p></li>
-<li><p><strong>trigger_run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The run ID to use for the triggered DAG run (templated).
+<li><p><strong>trigger_dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The dag_id to trigger (templated).</p></li>
+<li><p><strong>trigger_run_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The run ID to use for the triggered DAG run (templated).
 If not provided, a run ID will be automatically generated.</p></li>
-<li><p><strong>conf</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – Configuration for the DAG run (templated).</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em>) – Execution date for the dag (templated).</p></li>
-<li><p><strong>reset_dag_run</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether or not clear existing dag run if already exists.
+<li><p><strong>conf</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- Configuration for the DAG run (templated).</p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em>) -- Execution date for the dag (templated).</p></li>
+<li><p><strong>reset_dag_run</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether or not clear existing dag run if already exists.
 This is useful when backfill or rerun an existing dag run.
 When reset_dag_run=False and dag run exists, DagRunAlreadyExists will be raised.
 When reset_dag_run=True and dag run exists, existing dag run will be cleared to rerun.</p></li>
-<li><p><strong>wait_for_completion</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether or not wait for dag run completion. (default: False)</p></li>
-<li><p><strong>poke_interval</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – Poke interval to check dag run status when wait_for_completion=True.
+<li><p><strong>wait_for_completion</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether or not wait for dag run completion. (default: False)</p></li>
+<li><p><strong>poke_interval</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- Poke interval to check dag run status when wait_for_completion=True.
 (default: 60)</p></li>
-<li><p><strong>allowed_states</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) – List of allowed states, default is <code class="docutils literal notranslate"><span class="pre">['success']</span></code>.</p></li>
-<li><p><strong>failed_states</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) – List of failed or dis-allowed states, default is <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p></li>
+<li><p><strong>allowed_states</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) -- List of allowed states, default is <code class="docutils literal notranslate"><span class="pre">['success']</span></code>.</p></li>
+<li><p><strong>failed_states</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) -- List of failed or dis-allowed states, default is <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/weekday/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/weekday/index.html
index cdfe84a04..5469b3b3a 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/weekday/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/operators/weekday/index.html
@@ -843,9 +843,9 @@ For more information on how to use this operator, take a look at the guide:
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>follow_task_ids_if_true</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – task id or task ids to follow if criteria met</p></li>
-<li><p><strong>follow_task_ids_if_false</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – task id or task ids to follow if criteria does not met</p></li>
-<li><p><strong>week_day</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – <p>Day of the week to check (full name). Optionally, a set
+<li><p><strong>follow_task_ids_if_true</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- task id or task ids to follow if criteria met</p></li>
+<li><p><strong>follow_task_ids_if_false</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- task id or task ids to follow if criteria does not met</p></li>
+<li><p><strong>week_day</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- <p>Day of the week to check (full name). Optionally, a set
 of days can also be provided using a set.
 Example values:</p>
 <blockquote>
@@ -857,9 +857,9 @@ Example values:</p>
 </ul>
 </div></blockquote>
 </p></li>
-<li><p><strong>use_task_execution_day</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – If <code class="docutils literal notranslate"><span class="pre">True</span></code>, uses task’s execution day to compare
+<li><p><strong>use_task_execution_day</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- If <code class="docutils literal notranslate"><span class="pre">True</span></code>, uses task's execution day to compare
 with is_today. Execution Date is Useful for backfilling.
-If <code class="docutils literal notranslate"><span class="pre">False</span></code>, uses system’s day of the week.</p></li>
+If <code class="docutils literal notranslate"><span class="pre">False</span></code>, uses system's day of the week.</p></li>
 </ul>
 </dd>
 </dl>
@@ -871,7 +871,7 @@ necessary to choose a branch and returning a task_id or list of
 task_ids.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) – Context dictionary as passed to execute()</p>
+<dd class="field-odd"><p><strong>context</strong> (<em>airflow.utils.context.Context</em>) -- Context dictionary as passed to execute()</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/base_secrets/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/base_secrets/index.html
index a6ab24ad3..fafda0bfd 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/base_secrets/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/base_secrets/index.html
@@ -755,9 +755,9 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>path_prefix</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Prefix of the path to get secret</p></li>
-<li><p><strong>secret_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Secret id</p></li>
-<li><p><strong>sep</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – separator used to concatenate connections_prefix and conn_id. Default: “/”</p></li>
+<li><p><strong>path_prefix</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Prefix of the path to get secret</p></li>
+<li><p><strong>secret_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Secret id</p></li>
+<li><p><strong>sep</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- separator used to concatenate connections_prefix and conn_id. Default: &quot;/&quot;</p></li>
 </ul>
 </dd>
 </dl>
@@ -771,7 +771,7 @@
 <code class="docutils literal notranslate"><span class="pre">get_connection</span></code> instead.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -784,8 +784,8 @@ Looks at first character to determine how to deserialize.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p></li>
-<li><p><strong>value</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – the serialized representation of the Connection object</p></li>
+<li><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p></li>
+<li><p><strong>value</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- the serialized representation of the Connection object</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -805,7 +805,7 @@ Looks at first character to determine how to deserialize.</p>
 instead.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -817,7 +817,7 @@ instead.</p>
 <p>Tries <code class="docutils literal notranslate"><span class="pre">get_conn_value</span></code> first and if not implemented, tries <code class="docutils literal notranslate"><span class="pre">get_conn_uri</span></code></p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -828,7 +828,7 @@ instead.</p>
 <dd><p>Return connection object with a given <code class="docutils literal notranslate"><span class="pre">conn_id</span></code>.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -839,7 +839,7 @@ instead.</p>
 <dd><p>Return value for Airflow Variable</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>Variable Value</p>
@@ -856,7 +856,7 @@ instead.</p>
 <dd><p>Return value for Airflow Config Key</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Config Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Config Key</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>Config Value</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/environment_variables/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/environment_variables/index.html
index ef934426d..4fc9689ef 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/environment_variables/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/environment_variables/index.html
@@ -790,7 +790,7 @@
 <code class="docutils literal notranslate"><span class="pre">get_connection</span></code> instead.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -801,7 +801,7 @@
 <dd><p>Get Airflow Variable from Environment Variable</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>Variable Value</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/local_filesystem/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/local_filesystem/index.html
index f01adfe18..462abcc40 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/local_filesystem/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/local_filesystem/index.html
@@ -815,7 +815,7 @@
 <p><code class="docutils literal notranslate"><span class="pre">JSON</span></code>, <cite>YAML</cite> and <code class="docutils literal notranslate"><span class="pre">.env</span></code> files are supported.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>file_path</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The location of the file that will be processed.</p>
+<dd class="field-odd"><p><strong>file_path</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The location of the file that will be processed.</p>
 </dd>
 <dt class="field-even">Return type</dt>
 <dd class="field-even"><p>Dict[<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)">str</a>, List[<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)">str</a>]]</p>
@@ -826,7 +826,7 @@
 <dl class="py function">
 <dt class="sig sig-object py" id="airflow.secrets.local_filesystem.load_connections">
 <span class="sig-prename descclassname"><span class="pre">airflow.secrets.local_filesystem.</span></span><span class="sig-name descname"><span class="pre">load_connections</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">file_path</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/secrets/local_filesystem.html#load_connections"><span class="viewcode-link"><span class="pre"> [...]
-<dd><p>This function is deprecated. Please use <cite>airflow.secrets.local_filesystem.load_connections_dict</cite>.”,</p>
+<dd><p>This function is deprecated. Please use <cite>airflow.secrets.local_filesystem.load_connections_dict</cite>.&quot;,</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -855,8 +855,8 @@
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>variables_file_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – File location with variables data.</p></li>
-<li><p><strong>connections_file_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – File location with connection data.</p></li>
+<li><p><strong>variables_file_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- File location with variables data.</p></li>
+<li><p><strong>connections_file_path</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- File location with connection data.</p></li>
 </ul>
 </dd>
 </dl>
@@ -867,7 +867,7 @@
 <p>Tries <code class="docutils literal notranslate"><span class="pre">get_conn_value</span></code> first and if not implemented, tries <code class="docutils literal notranslate"><span class="pre">get_conn_uri</span></code></p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -878,7 +878,7 @@
 <dd><p>Return connection object with a given <code class="docutils literal notranslate"><span class="pre">conn_id</span></code>.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -889,7 +889,7 @@
 <dd><p>Return value for Airflow Variable</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>Variable Value</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/metastore/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/metastore/index.html
index 876d5d50c..7856fc9b0 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/metastore/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/secrets/metastore/index.html
@@ -746,7 +746,7 @@
 <p>Tries <code class="docutils literal notranslate"><span class="pre">get_conn_value</span></code> first and if not implemented, tries <code class="docutils literal notranslate"><span class="pre">get_conn_uri</span></code></p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -757,7 +757,7 @@
 <dd><p>Return connection object with a given <code class="docutils literal notranslate"><span class="pre">conn_id</span></code>.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>conn_id</strong> – connection id</p>
+<dd class="field-odd"><p><strong>conn_id</strong> -- connection id</p>
 </dd>
 </dl>
 </dd></dl>
@@ -768,7 +768,7 @@
 <dd><p>Get Airflow Variable from Metadata DB</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – Variable Key</p>
+<dd class="field-odd"><p><strong>key</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- Variable Key</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>Variable Value</p>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/base/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/base/index.html
index 4030a8f95..e8ba08387 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/base/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/base/index.html
@@ -859,23 +859,23 @@ a criteria is met and fail if and when they time out.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>soft_fail</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Set to true to mark the task as SKIPPED on failure</p></li>
-<li><p><strong>poke_interval</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a>) – Time in seconds that the job should wait in
+<li><p><strong>soft_fail</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Set to true to mark the task as SKIPPED on failure</p></li>
+<li><p><strong>poke_interval</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a>) -- Time in seconds that the job should wait in
 between each tries</p></li>
-<li><p><strong>timeout</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a>) – Time, in seconds before the task times out and fails.</p></li>
-<li><p><strong>mode</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – How the sensor operates.
+<li><p><strong>timeout</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#float" title="(in Python v3.10)"><em>float</em></a>) -- Time, in seconds before the task times out and fails.</p></li>
+<li><p><strong>mode</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- How the sensor operates.
 Options are: <code class="docutils literal notranslate"><span class="pre">{</span> <span class="pre">poke</span> <span class="pre">|</span> <span class="pre">reschedule</span> <span class="pre">}</span></code>, default is <code class="docutils literal notranslate"><span class="pre">poke</span></code>.
 When set to <code class="docutils literal notranslate"><span class="pre">poke</span></code> the sensor is taking up a worker slot for its
 whole execution time and sleeps between pokes. Use this mode if the
 expected runtime of the sensor is short or if a short poke interval
 is required. Note that the sensor will hold onto a worker slot and
-a pool slot for the duration of the sensor’s runtime in this mode.
+a pool slot for the duration of the sensor's runtime in this mode.
 When set to <code class="docutils literal notranslate"><span class="pre">reschedule</span></code> the sensor task frees the worker slot when
-the criteria is not yet met and it’s rescheduled at a later time. Use
+the criteria is not yet met and it's rescheduled at a later time. Use
 this mode if the time before the criteria is met is expected to be
 quite long. The poke interval should be more than one minute to
 prevent too much load on the scheduler.</p></li>
-<li><p><strong>exponential_backoff</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – allow progressive longer waits between
+<li><p><strong>exponential_backoff</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- allow progressive longer waits between
 pokes by using exponential backoff algorithm</p></li>
 </ul>
 </dd>
@@ -922,8 +922,8 @@ override.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>ti</strong> – Task instance object.</p></li>
-<li><p><strong>context</strong> – TaskInstance template context from the ti.</p></li>
+<li><p><strong>ti</strong> -- Task instance object.</p></li>
+<li><p><strong>context</strong> -- TaskInstance template context from the ti.</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -940,7 +940,7 @@ poke_context with operator class can be used to identify a unique
 sensor job.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>context</strong> – TaskInstance template context.</p>
+<dd class="field-odd"><p><strong>context</strong> -- TaskInstance template context.</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>A dictionary with key in poke_context_fields.</p>
@@ -956,7 +956,7 @@ execution_context include execution requirement for each sensor task
 such as timeout setup, email_alert setup.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>context</strong> – TaskInstance template context.</p>
+<dd class="field-odd"><p><strong>context</strong> -- TaskInstance template context.</p>
 </dd>
 <dt class="field-even">Returns</dt>
 <dd class="field-even"><p>A dictionary with key in execution_fields.</p>
@@ -997,10 +997,10 @@ returns a copy of the task</p>
 <dd><p>Class Decorator for child classes of BaseSensorOperator to indicate
 that instances of this class are only safe to use poke mode.</p>
 <p>Will decorate all methods in the class to assert they did not change
-the mode from ‘poke’.</p>
+the mode from 'poke'.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>cls</strong> – BaseSensor class to enforce methods only use ‘poke’ mode.</p>
+<dd class="field-odd"><p><strong>cls</strong> -- BaseSensor class to enforce methods only use 'poke' mode.</p>
 </dd>
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/bash/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/bash/index.html
index b98dc2122..f5c6af669 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/bash/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/bash/index.html
@@ -790,13 +790,13 @@ return code is 0.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>bash_command</strong> – The command, set of commands or reference to a
-bash script (must be ‘.sh’) to be executed.</p></li>
-<li><p><strong>env</strong> – If env is not None, it must be a mapping that defines the
+<li><p><strong>bash_command</strong> -- The command, set of commands or reference to a
+bash script (must be '.sh') to be executed.</p></li>
+<li><p><strong>env</strong> -- If env is not None, it must be a mapping that defines the
 environment variables for the new process; these are used instead
 of inheriting the current process environment, which is the default
 behavior. (templated)</p></li>
-<li><p><strong>output_encoding</strong> – output encoding of bash command.</p></li>
+<li><p><strong>output_encoding</strong> -- output encoding of bash command.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/date_time/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/date_time/index.html
index 4db8e2d3b..457b86749 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/date_time/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/date_time/index.html
@@ -821,7 +821,7 @@ required to run at 01:00 next day, using <code class="docutils literal notransla
 </dl>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>target_time</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – datetime after which the job succeeds. (templated)</p>
+<dd class="field-odd"><p><strong>target_time</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- datetime after which the job succeeds. (templated)</p>
 </dd>
 </dl>
 <dl class="py attribute">
@@ -849,7 +849,7 @@ a worker slot while it is waiting.</p>
 <p>It is a drop-in replacement for DateTimeSensor.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>target_time</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) – datetime after which the job succeeds. (templated)</p>
+<dd class="field-odd"><p><strong>target_time</strong> (<em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em>) -- datetime after which the job succeeds. (templated)</p>
 </dd>
 </dl>
 <dl class="py method">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/external_task/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/external_task/index.html
index 505a2fa4b..293e826da 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/external_task/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/external_task/index.html
@@ -835,8 +835,8 @@ supported at runtime but is deprecated.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>operator</strong> – airflow operator</p></li>
-<li><p><strong>ti_key</strong> – TaskInstance ID to return link for</p></li>
+<li><p><strong>operator</strong> -- airflow operator</p></li>
+<li><p><strong>ti_key</strong> -- TaskInstance ID to return link for</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -856,27 +856,27 @@ specific logical date.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>external_dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The dag_id that contains the task you want to
+<li><p><strong>external_dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The dag_id that contains the task you want to
 wait for</p></li>
-<li><p><strong>external_task_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – The task_id that contains the task you want to
+<li><p><strong>external_task_id</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- The task_id that contains the task you want to
 wait for. If <code class="docutils literal notranslate"><span class="pre">None</span></code> (default value) the sensor waits for the DAG</p></li>
-<li><p><strong>external_task_ids</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – The list of task_ids that you want to wait for.
+<li><p><strong>external_task_ids</strong> (<em>Optional</em><em>[</em><em>Collection</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- The list of task_ids that you want to wait for.
 If <code class="docutils literal notranslate"><span class="pre">None</span></code> (default value) the sensor waits for the DAG. Either
 external_task_id or external_task_ids can be passed to
 ExternalTaskSensor, but not both.</p></li>
-<li><p><strong>allowed_states</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – Iterable of allowed states, default is <code class="docutils literal notranslate"><span class="pre">['success']</span></code></p></li>
-<li><p><strong>failed_states</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) – Iterable of failed or dis-allowed states, default is <code class="docutils literal notranslate"><span class="pre">None</span></code></p></li>
-<li><p><strong>execution_delta</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) – time difference with the previous execution to
+<li><p><strong>allowed_states</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- Iterable of allowed states, default is <code class="docutils literal notranslate"><span class="pre">['success']</span></code></p></li>
+<li><p><strong>failed_states</strong> (<em>Optional</em><em>[</em><em>Iterable</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em><em>]</em>) -- Iterable of failed or dis-allowed states, default is <code class="docutils literal notranslate"><span class="pre">None</span></code></p></li>
+<li><p><strong>execution_delta</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.timedelta" title="(in Python v3.10)"><em>datetime.timedelta</em></a><em>]</em>) -- time difference with the previous execution to
 look at, the default is the same logical date as the current task or DAG.
 For yesterday, use [positive!] datetime.timedelta(days=1). Either
 execution_delta or execution_date_fn can be passed to
 ExternalTaskSensor, but not both.</p></li>
-<li><p><strong>execution_date_fn</strong> (<em>Optional</em><em>[</em><em>Callable</em><em>]</em>) – function that receives the current execution’s logical date as the first
+<li><p><strong>execution_date_fn</strong> (<em>Optional</em><em>[</em><em>Callable</em><em>]</em>) -- function that receives the current execution's logical date as the first
 positional argument and optionally any number of keyword arguments available in the
 context dictionary, and returns the desired logical dates to query.
 Either execution_delta or execution_date_fn can be passed to ExternalTaskSensor,
 but not both.</p></li>
-<li><p><strong>check_existence</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Set to <cite>True</cite> to check if the external task exists (when
+<li><p><strong>check_existence</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Set to <cite>True</cite> to check if the external task exists (when
 external_task_id is not None) or check if the DAG to wait for exists (when
 external_task_id is None), and immediately cease waiting if the external task
 or DAG does not exist (default value: False).</p></li>
@@ -913,9 +913,9 @@ override.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>dttm_filter</strong> – date time filter for execution date</p></li>
-<li><p><strong>session</strong> – airflow session object</p></li>
-<li><p><strong>states</strong> – task or dag states</p></li>
+<li><p><strong>dttm_filter</strong> -- date time filter for execution date</p></li>
+<li><p><strong>session</strong> -- airflow session object</p></li>
+<li><p><strong>states</strong> -- task or dag states</p></li>
 </ul>
 </dd>
 <dt class="field-even">Returns</dt>
@@ -934,16 +934,16 @@ override.</p>
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.sensors.external_task.</span></span><span class="sig-name descname"><span class="pre">ExternalTaskMarker</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">external_dag_id</span></span></em>, <em class="sig-param"><spa [...]
 <dd><p>Bases: <a class="reference internal" href="../../operators/empty/index.html#airflow.operators.empty.EmptyOperator" title="airflow.operators.empty.EmptyOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.operators.empty.EmptyOperator</span></code></a></p>
 <p>Use this operator to indicate that a task on a different DAG depends on this task.
-When this task is cleared with “Recursive” selected, Airflow will clear the task on
+When this task is cleared with &quot;Recursive&quot; selected, Airflow will clear the task on
 the other DAG and its downstream tasks recursively. Transitive dependencies are followed
 until the recursion_depth is reached.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>external_dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The dag_id that contains the dependent task that needs to be cleared.</p></li>
-<li><p><strong>external_task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) – The task_id of the dependent task that needs to be cleared.</p></li>
-<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em>) – The logical date of the dependent task execution that needs to be cleared.</p></li>
-<li><p><strong>recursion_depth</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) – The maximum level of transitive dependencies allowed. Default is 10.
+<li><p><strong>external_dag_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The dag_id that contains the dependent task that needs to be cleared.</p></li>
+<li><p><strong>external_task_id</strong> (<a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a>) -- The task_id of the dependent task that needs to be cleared.</p></li>
+<li><p><strong>execution_date</strong> (<em>Optional</em><em>[</em><em>Union</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><a class="reference external" href="https://docs.python.org/3/library/datetime.html#datetime.datetime" title="(in Python v3.10)"><em>datetime.datetime</em></a><em>]</em><em>]</em>) -- The logical date of the dependent task execution that needs to be cleared.< [...]
+<li><p><strong>recursion_depth</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#int" title="(in Python v3.10)"><em>int</em></a>) -- The maximum level of transitive dependencies allowed. Default is 10.
 This is mostly used for preventing cyclic dependencies. It is fine to increase
 this number if necessary. However, too many levels of transitive dependencies will make
 it slower to clear tasks in the web UI.</p></li>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/filesystem/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/filesystem/index.html
index 33461d720..7e1bcfd5d 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/filesystem/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/filesystem/index.html
@@ -793,11 +793,11 @@ any files exist inside it (either directly, or within a subdirectory)</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>fs_conn_id</strong> – reference to the File (path)
+<li><p><strong>fs_conn_id</strong> -- reference to the File (path)
 connection id</p></li>
-<li><p><strong>filepath</strong> – File or folder name (relative to
+<li><p><strong>filepath</strong> -- File or folder name (relative to
 the base path set within the connection), can be a glob.</p></li>
-<li><p><strong>recursive</strong> – when set to <code class="docutils literal notranslate"><span class="pre">True</span></code>, enables recursive directory matching behavior of
+<li><p><strong>recursive</strong> -- when set to <code class="docutils literal notranslate"><span class="pre">True</span></code>, enables recursive directory matching behavior of
 <code class="docutils literal notranslate"><span class="pre">**</span></code> in glob filepath parameter. Defaults to <code class="docutils literal notranslate"><span class="pre">False</span></code>.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/python/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/python/index.html
index b92c26507..ec9489a21 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/python/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/python/index.html
@@ -793,15 +793,15 @@ in the callable</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>python_callable</strong> (<em>Callable</em>) – A reference to an object that is callable</p></li>
-<li><p><strong>op_kwargs</strong> (<em>Optional</em><em>[</em><em>Mapping</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) – a dictionary of keyword arguments that will get unpacked
+<li><p><strong>python_callable</strong> (<em>Callable</em>) -- A reference to an object that is callable</p></li>
+<li><p><strong>op_kwargs</strong> (<em>Optional</em><em>[</em><em>Mapping</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>, </em><em>Any</em><em>]</em><em>]</em>) -- a dictionary of keyword arguments that will get unpacked
 in your function</p></li>
-<li><p><strong>op_args</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) – a list of positional arguments that will get unpacked when
+<li><p><strong>op_args</strong> (<em>Optional</em><em>[</em><em>List</em><em>]</em>) -- a list of positional arguments that will get unpacked when
 calling your callable</p></li>
-<li><p><strong>templates_dict</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) – a dictionary where the values are templates that
+<li><p><strong>templates_dict</strong> (<em>Optional</em><em>[</em><em>Dict</em><em>]</em>) -- a dictionary where the values are templates that
 will get templated by the Airflow engine sometime between
 <code class="docutils literal notranslate"><span class="pre">__init__</span></code> and <code class="docutils literal notranslate"><span class="pre">execute</span></code> takes place and are made available
-in your callable’s context after the template has been applied.</p></li>
+in your callable's context after the template has been applied.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/smart_sensor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/smart_sensor/index.html
index 96f68fa9c..14993b1a7 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/smart_sensor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/smart_sensor/index.html
@@ -918,7 +918,7 @@ A sensor work object has the following attributes:
 <cite>log</cite>: The sensor work logger which will mock the corresponding task instance log.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>si</strong> – The sensor_instance ORM object.</p>
+<dd class="field-odd"><p><strong>si</strong> -- The sensor_instance ORM object.</p>
 </dd>
 </dl>
 <dl class="py method">
@@ -1012,8 +1012,8 @@ for retry without failing current run.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>exception_info</strong> – Details of the exception information.</p></li>
-<li><p><strong>is_infra_failure</strong> – If current exception was caused by transient infra failure.
+<li><p><strong>exception_info</strong> -- Details of the exception information.</p></li>
+<li><p><strong>is_infra_failure</strong> -- If current exception was caused by transient infra failure.
 There is a retry window _infra_failure_retry_window that the smart sensor will
 retry poke function without failing current task run.</p></li>
 </ul>
@@ -1084,14 +1084,14 @@ all sensor task state in task_instance table</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>soft_fail</strong> – Set to true to mark the task as SKIPPED on failure</p></li>
-<li><p><strong>poke_interval</strong> – Time in seconds that the job should wait in
+<li><p><strong>soft_fail</strong> -- Set to true to mark the task as SKIPPED on failure</p></li>
+<li><p><strong>poke_interval</strong> -- Time in seconds that the job should wait in
 between each tries.</p></li>
-<li><p><strong>smart_sensor_timeout</strong> – Time, in seconds before the internal sensor
+<li><p><strong>smart_sensor_timeout</strong> -- Time, in seconds before the internal sensor
 job times out if poke_timeout is not defined.</p></li>
-<li><p><strong>shard_min</strong> – shard code lower bound (inclusive)</p></li>
-<li><p><strong>shard_max</strong> – shard code upper bound (exclusive)</p></li>
-<li><p><strong>poke_timeout</strong> – Time, in seconds before the task times out and fails.</p></li>
+<li><p><strong>shard_min</strong> -- shard code lower bound (inclusive)</p></li>
+<li><p><strong>shard_max</strong> -- shard code upper bound (exclusive)</p></li>
+<li><p><strong>poke_timeout</strong> -- Time, in seconds before the task times out and fails.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/sql/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/sql/index.html
index cd2950b1f..8486e7f97 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/sql/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/sql/index.html
@@ -790,7 +790,7 @@
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.sensors.sql.</span></span><span class="sig-name descname"><span class="pre">SqlSensor</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">conn_id</span></span></em>, <em class="sig-param"><span class="n"><span class="pr [...]
 <dd><p>Bases: <a class="reference internal" href="../base/index.html#airflow.sensors.base.BaseSensorOperator" title="airflow.sensors.base.BaseSensorOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.sensors.base.BaseSensorOperator</span></code></a></p>
 <p>Runs a sql statement repeatedly until a criteria is met. It will keep trying until
-success or failure criteria are met, or if the first cell is not in (0, ‘0’, ‘’, None).
+success or failure criteria are met, or if the first cell is not in (0, '0', '', None).
 Optional success and failure callables are called with the first cell returned as the argument.
 If success callable is defined the sensor will keep retrying until the criteria is met.
 If failure callable is defined and the criteria is met the sensor will raise AirflowException.
@@ -799,16 +799,16 @@ be passed to the sensor in which case it will fail if no rows have been returned
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>conn_id</strong> – The connection to run the sensor against</p></li>
-<li><p><strong>sql</strong> – The sql to run. To pass, it needs to return at least one cell
+<li><p><strong>conn_id</strong> -- The connection to run the sensor against</p></li>
+<li><p><strong>sql</strong> -- The sql to run. To pass, it needs to return at least one cell
 that contains a non-zero / empty string value.</p></li>
-<li><p><strong>parameters</strong> – The parameters to render the SQL query with (optional).</p></li>
-<li><p><strong>success</strong> – Success criteria for the sensor is a Callable that takes first_cell
+<li><p><strong>parameters</strong> -- The parameters to render the SQL query with (optional).</p></li>
+<li><p><strong>success</strong> -- Success criteria for the sensor is a Callable that takes first_cell
 as the only argument, and returns a boolean (optional).</p></li>
-<li><p><strong>failure</strong> – Failure criteria for the sensor is a Callable that takes first_cell
+<li><p><strong>failure</strong> -- Failure criteria for the sensor is a Callable that takes first_cell
 as the only argument and return a boolean (optional).</p></li>
-<li><p><strong>fail_on_empty</strong> – Explicitly fail on no rows returned.</p></li>
-<li><p><strong>hook_params</strong> – Extra config params to be passed to the underlying hook.
+<li><p><strong>fail_on_empty</strong> -- Explicitly fail on no rows returned.</p></li>
+<li><p><strong>hook_params</strong> -- Extra config params to be passed to the underlying hook.
 Should match the desired hook constructor params.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_delta/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_delta/index.html
index 4aa62ee6d..296fc7484 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_delta/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_delta/index.html
@@ -796,10 +796,10 @@
 <dt class="sig sig-object py" id="airflow.sensors.time_delta.TimeDeltaSensor">
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.sensors.time_delta.</span></span><span class="sig-name descname"><span class="pre">TimeDeltaSensor</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">delta</span></span></em>, <em class="sig-param"><span class="o"><spa [...]
 <dd><p>Bases: <a class="reference internal" href="../base/index.html#airflow.sensors.base.BaseSensorOperator" title="airflow.sensors.base.BaseSensorOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.sensors.base.BaseSensorOperator</span></code></a></p>
-<p>Waits for a timedelta after the run’s data interval.</p>
+<p>Waits for a timedelta after the run's data interval.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>delta</strong> – time length to wait after the data interval before succeeding.</p>
+<dd class="field-odd"><p><strong>delta</strong> -- time length to wait after the data interval before succeeding.</p>
 </dd>
 </dl>
 <dl class="py method">
@@ -821,7 +821,7 @@ override.</p>
 taking up a worker slot while it is waiting.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>delta</strong> – time length to wait after the data interval before succeeding.</p>
+<dd class="field-odd"><p><strong>delta</strong> -- time length to wait after the data interval before succeeding.</p>
 </dd>
 </dl>
 <dl class="py method">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_sensor/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_sensor/index.html
index 74622e14e..7bef6c986 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_sensor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/time_sensor/index.html
@@ -799,7 +799,7 @@
 <p>Waits until the specified time of the day.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>target_time</strong> – time after which the job succeeds</p>
+<dd class="field-odd"><p><strong>target_time</strong> -- time after which the job succeeds</p>
 </dd>
 </dl>
 <dl class="py method">
@@ -821,7 +821,7 @@ override.</p>
 it is waiting.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
-<dd class="field-odd"><p><strong>target_time</strong> – time after which the job succeeds</p>
+<dd class="field-odd"><p><strong>target_time</strong> -- time after which the job succeeds</p>
 </dd>
 </dl>
 <dl class="py method">
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/weekday/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/weekday/index.html
index e231659cd..ab800b19e 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/weekday/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/sensors/weekday/index.html
@@ -784,7 +784,7 @@
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.sensors.weekday.</span></span><span class="sig-name descname"><span class="pre">DayOfWeekSensor</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="o"><span class="pre">*</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">week_day</span></span></em>, <em class="sig-param"><span class="n"><spa [...]
 <dd><p>Bases: <a class="reference internal" href="../base/index.html#airflow.sensors.base.BaseSensorOperator" title="airflow.sensors.base.BaseSensorOperator"><code class="xref py py-obj docutils literal notranslate"><span class="pre">airflow.sensors.base.BaseSensorOperator</span></code></a></p>
 <p>Waits until the first specified day of the week. For example, if the execution
-day of the task is ‘2018-12-22’ (Saturday) and you pass ‘FRIDAY’, the task will wait
+day of the task is '2018-12-22' (Saturday) and you pass 'FRIDAY', the task will wait
 until next Friday.</p>
 <p><strong>Example</strong> (with single day):</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">weekend_check</span> <span class="o">=</span> <span class="n">DayOfWeekSensor</span><span class="p">(</span>
@@ -816,7 +816,7 @@ until next Friday.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>week_day</strong> – <p>Day of the week to check (full name). Optionally, a set
+<li><p><strong>week_day</strong> -- <p>Day of the week to check (full name). Optionally, a set
 of days can also be provided using a set.
 Example values:</p>
 <blockquote>
@@ -828,10 +828,10 @@ Example values:</p>
 </ul>
 </div></blockquote>
 </p></li>
-<li><p><strong>use_task_execution_day</strong> – If <code class="docutils literal notranslate"><span class="pre">True</span></code>, uses task’s execution day to compare
+<li><p><strong>use_task_execution_day</strong> -- If <code class="docutils literal notranslate"><span class="pre">True</span></code>, uses task's execution day to compare
 with week_day. Execution Date is Useful for backfilling.
-If <code class="docutils literal notranslate"><span class="pre">False</span></code>, uses system’s day of the week. Useful when you
-don’t want to run anything on weekdays on the system.</p></li>
+If <code class="docutils literal notranslate"><span class="pre">False</span></code>, uses system's day of the week. Useful when you
+don't want to run anything on weekdays on the system.</p></li>
 </ul>
 </dd>
 </dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/base/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/base/index.html
index 4cf80b02c..39da57d04 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/base/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/base/index.html
@@ -797,7 +797,7 @@
 <em class="property"><span class="pre">class</span><span class="w"> </span></em><span class="sig-prename descclassname"><span class="pre">airflow.timetables.base.</span></span><span class="sig-name descname"><span class="pre">DataInterval</span></span><a class="reference internal" href="../../../../_modules/airflow/timetables/base.html#DataInterval"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.timetables.base.DataInterval" t [...]
 <dd><p>Bases: <code class="xref py py-obj docutils literal notranslate"><span class="pre">NamedTuple</span></code></p>
 <p>A data interval for a DagRun to operate over.</p>
-<p>Both <code class="docutils literal notranslate"><span class="pre">start</span></code> and <code class="docutils literal notranslate"><span class="pre">end</span></code> <strong>MUST</strong> be “aware”, i.e. contain timezone
+<p>Both <code class="docutils literal notranslate"><span class="pre">start</span></code> and <code class="docutils literal notranslate"><span class="pre">end</span></code> <strong>MUST</strong> be &quot;aware&quot;, i.e. contain timezone
 information.</p>
 <dl class="py attribute">
 <dt class="sig sig-object py" id="airflow.timetables.base.DataInterval.start">
@@ -812,7 +812,7 @@ information.</p>
 <dl class="py method">
 <dt class="sig sig-object py" id="airflow.timetables.base.DataInterval.exact">
 <em class="property"><span class="pre">classmethod</span><span class="w"> </span></em><span class="sig-name descname"><span class="pre">exact</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">cls</span></span></em>, <em class="sig-param"><span class="n"><span class="pre">at</span></span></em><span class="sig-paren">)</span><a class="reference internal" href="../../../../_modules/airflow/timetables/base.html#DataInterval.exact"><span clas [...]
-<dd><p>Represent an “interval” containing only an exact time.</p>
+<dd><p>Represent an &quot;interval&quot; containing only an exact time.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -826,8 +826,8 @@ information.</p>
 <p>Restriction on when a DAG can be scheduled for a run.</p>
 <p>Specifically, the run must not be earlier than <code class="docutils literal notranslate"><span class="pre">earliest</span></code>, nor later than
 <code class="docutils literal notranslate"><span class="pre">latest</span></code>. If <code class="docutils literal notranslate"><span class="pre">catchup</span></code> is <em>False</em>, the run must also not be earlier than
-the current time, i.e. “missed” schedules are not backfilled.</p>
-<p>These values are generally set on the DAG or task’s <code class="docutils literal notranslate"><span class="pre">start_date</span></code>,
+the current time, i.e. &quot;missed&quot; schedules are not backfilled.</p>
+<p>These values are generally set on the DAG or task's <code class="docutils literal notranslate"><span class="pre">start_date</span></code>,
 <code class="docutils literal notranslate"><span class="pre">end_date</span></code>, and <code class="docutils literal notranslate"><span class="pre">catchup</span></code> arguments.</p>
 <p>Both <code class="docutils literal notranslate"><span class="pre">earliest</span></code> and <code class="docutils literal notranslate"><span class="pre">latest</span></code>, if not <em>None</em>, are inclusive; a DAG run
 can happen exactly at either point of time. They are guaranteed to be aware
@@ -861,7 +861,7 @@ schedule a DagRun creation.</p>
 <dt class="sig sig-object py" id="airflow.timetables.base.DagRunInfo.run_after">
 <span class="sig-name descname"><span class="pre">run_after</span></span><em class="property"><span class="w"> </span><span class="pre">:pendulum.DateTime</span></em><a class="reference internal" href="../../../../_modules/airflow/timetables/base.html#DagRunInfo.run_after"><span class="viewcode-link"><span class="pre">[source]</span></span></a><a class="headerlink" href="#airflow.timetables.base.DagRunInfo.run_after" title="Permalink to this definition">¶</a></dt>
 <dd><p>The earliest time this DagRun is created and its tasks scheduled.</p>
-<p>This <strong>MUST</strong> be “aware”, i.e. contain timezone information.</p>
+<p>This <strong>MUST</strong> be &quot;aware&quot;, i.e. contain timezone information.</p>
 </dd></dl>
 
 <dl class="py attribute">
@@ -972,7 +972,7 @@ is put into a dagbag. The default implementation does nothing.</p>
 <dd><p>A short summary for the timetable.</p>
 <p>This is used to display the timetable in the web UI. A cron expression
 timetable, for example, can use this to display the expression. The
-default implementation returns the timetable’s type name.</p>
+default implementation returns the timetable's type name.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -996,9 +996,9 @@ be when the user triggers the run. The default implementation raises
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>DataInterval</em></a><em>]</em>) – The data interval of the associated
-DAG’s last scheduled or backfilled run (manual runs not considered).</p></li>
-<li><p><strong>restriction</strong> (<a class="reference internal" href="#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>TimeRestriction</em></a>) – Restriction to apply when scheduling the DAG run.
+<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>DataInterval</em></a><em>]</em>) -- The data interval of the associated
+DAG's last scheduled or backfilled run (manual runs not considered).</p></li>
+<li><p><strong>restriction</strong> (<a class="reference internal" href="#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>TimeRestriction</em></a>) -- Restriction to apply when scheduling the DAG run.
 See documentation of <a class="reference internal" href="#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><code class="xref py py-class docutils literal notranslate"><span class="pre">TimeRestriction</span></code></a> for details.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/events/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/events/index.html
index d6f404898..de91dc816 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/events/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/events/index.html
@@ -746,14 +746,14 @@ predictable but truly irregular scheduling such as sporting events.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>event_dates</strong> (<em>Iterable</em><em>[</em><em>pendulum.DateTime</em><em>]</em>) – List of datetimes for the DAG to run at. Duplicates will be ignored. Must be finite
+<li><p><strong>event_dates</strong> (<em>Iterable</em><em>[</em><em>pendulum.DateTime</em><em>]</em>) -- List of datetimes for the DAG to run at. Duplicates will be ignored. Must be finite
 and of reasonable size as it will be loaded in its entirety.</p></li>
-<li><p><strong>restrict_to_events</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – Whether manual runs should use the most recent event or
+<li><p><strong>restrict_to_events</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- Whether manual runs should use the most recent event or
 the current time</p></li>
-<li><p><strong>presorted</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) – if True, event_dates will be assumed to be in ascending order. Provides modest
+<li><p><strong>presorted</strong> (<a class="reference external" href="https://docs.python.org/3/library/functions.html#bool" title="(in Python v3.10)"><em>bool</em></a>) -- if True, event_dates will be assumed to be in ascending order. Provides modest
 performance improvement for larger lists of event_dates.</p></li>
-<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) – A name for the timetable to display in the UI. Default None will be shown as
-“X Events” where X is the len of event_dates</p></li>
+<li><p><strong>description</strong> (<em>Optional</em><em>[</em><a class="reference external" href="https://docs.python.org/3/library/stdtypes.html#str" title="(in Python v3.10)"><em>str</em></a><em>]</em>) -- A name for the timetable to display in the UI. Default None will be shown as
+&quot;X Events&quot; where X is the len of event_dates</p></li>
 </ul>
 </dd>
 </dl>
@@ -763,7 +763,7 @@ performance improvement for larger lists of event_dates.</p></li>
 <dd><p>A short summary for the timetable.</p>
 <p>This is used to display the timetable in the web UI. A cron expression
 timetable, for example, can use this to display the expression. The
-default implementation returns the timetable’s type name.</p>
+default implementation returns the timetable's type name.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -782,9 +782,9 @@ default implementation returns the timetable’s type name.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) – The data interval of the associated
-DAG’s last scheduled or backfilled run (manual runs not considered).</p></li>
-<li><p><strong>restriction</strong> (<a class="reference internal" href="../base/index.html#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>airflow.timetables.base.TimeRestriction</em></a>) – Restriction to apply when scheduling the DAG run.
+<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) -- The data interval of the associated
+DAG's last scheduled or backfilled run (manual runs not considered).</p></li>
+<li><p><strong>restriction</strong> (<a class="reference internal" href="../base/index.html#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>airflow.timetables.base.TimeRestriction</em></a>) -- Restriction to apply when scheduling the DAG run.
 See documentation of <code class="xref py py-class docutils literal notranslate"><span class="pre">TimeRestriction</span></code> for details.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/interval/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/interval/index.html
index b6e84231c..1ea7f73b4 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/interval/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/interval/index.html
@@ -791,7 +791,7 @@ a five/six-segment representation, or one of <code class="docutils literal notra
 <p>The implementation extends on croniter to add timezone awareness. This is
 because croniter works only with naive timestamps, and cannot consider DST
 when determining the next/previous time.</p>
-<p>Don’t pass <code class="docutils literal notranslate"><span class="pre">&#64;once</span></code> in here; use <code class="docutils literal notranslate"><span class="pre">OnceTimetable</span></code> instead.</p>
+<p>Don't pass <code class="docutils literal notranslate"><span class="pre">&#64;once</span></code> in here; use <code class="docutils literal notranslate"><span class="pre">OnceTimetable</span></code> instead.</p>
 <dl class="field-list simple">
 </dl>
 <dl class="py method">
@@ -820,7 +820,7 @@ default implementation constructs the timetable without any arguments.</p>
 <dd><p>A short summary for the timetable.</p>
 <p>This is used to display the timetable in the web UI. A cron expression
 timetable, for example, can use this to display the expression. The
-default implementation returns the timetable’s type name.</p>
+default implementation returns the timetable's type name.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -899,7 +899,7 @@ default implementation constructs the timetable without any arguments.</p>
 <dd><p>A short summary for the timetable.</p>
 <p>This is used to display the timetable in the web UI. A cron expression
 timetable, for example, can use this to display the expression. The
-default implementation returns the timetable’s type name.</p>
+default implementation returns the timetable's type name.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
diff --git a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/simple/index.html b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/simple/index.html
index 8b87ce33c..249220779 100644
--- a/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/simple/index.html
+++ b/docs-archive/apache-airflow/2.3.0/_api/airflow/timetables/simple/index.html
@@ -763,7 +763,7 @@
 <dd><p>A short summary for the timetable.</p>
 <p>This is used to display the timetable in the web UI. A cron expression
 timetable, for example, can use this to display the expression. The
-default implementation returns the timetable’s type name.</p>
+default implementation returns the timetable's type name.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -776,9 +776,9 @@ default implementation returns the timetable’s type name.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) – The data interval of the associated
-DAG’s last scheduled or backfilled run (manual runs not considered).</p></li>
-<li><p><strong>restriction</strong> (<a class="reference internal" href="../base/index.html#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>airflow.timetables.base.TimeRestriction</em></a>) – Restriction to apply when scheduling the DAG run.
+<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) -- The data interval of the associated
+DAG's last scheduled or backfilled run (manual runs not considered).</p></li>
+<li><p><strong>restriction</strong> (<a class="reference internal" href="../base/index.html#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>airflow.timetables.base.TimeRestriction</em></a>) -- Restriction to apply when scheduling the DAG run.
 See documentation of <code class="xref py py-class docutils literal notranslate"><span class="pre">TimeRestriction</span></code> for details.</p></li>
 </ul>
 </dd>
@@ -813,7 +813,7 @@ a DagRunInfo object when asked at another time.</p>
 <dd><p>A short summary for the timetable.</p>
 <p>This is used to display the timetable in the web UI. A cron expression
 timetable, for example, can use this to display the expression. The
-default implementation returns the timetable’s type name.</p>
+default implementation returns the timetable's type name.</p>
 <dl class="field-list simple">
 </dl>
 </dd></dl>
@@ -826,9 +826,9 @@ default implementation returns the timetable’s type name.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Parameters</dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) – The data interval of the associated
-DAG’s last scheduled or backfilled run (manual runs not considered).</p></li>
-<li><p><strong>restriction</strong> (<a class="reference internal" href="../base/index.html#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>airflow.timetables.base.TimeRestriction</em></a>) – Restriction to apply when scheduling the DAG run.
+<li><p><strong>last_automated_data_interval</strong> (<em>Optional</em><em>[</em><a class="reference internal" href="../base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><em>airflow.timetables.base.DataInterval</em></a><em>]</em>) -- The data interval of the associated
+DAG's last scheduled or backfilled run (manual runs not considered).</p></li>
+<li><p><strong>restriction</strong> (<a class="reference internal" href="../base/index.html#airflow.timetables.base.TimeRestriction" title="airflow.timetables.base.TimeRestriction"><em>airflow.timetables.base.TimeRestriction</em></a>) -- Restriction to apply when scheduling the DAG run.
 See documentation of <code class="xref py py-class docutils literal notranslate"><span class="pre">TimeRestriction</span></code> for details.</p></li>
 </ul>
 </dd>
diff --git a/docs-archive/apache-airflow/2.3.0/_static/_gen/js/docs.js b/docs-archive/apache-airflow/2.3.0/_static/_gen/js/docs.js
index 57efdbeca..90898d86d 100644
--- a/docs-archive/apache-airflow/2.3.0/_static/_gen/js/docs.js
+++ b/docs-archive/apache-airflow/2.3.0/_static/_gen/js/docs.js
@@ -1 +1 @@
-!function(r){var n={};function o(t){if(n[t])return n[t].exports;var e=n[t]={i:t,l:!1,exports:{}};return r[t].call(e.exports,e,e.exports,o),e.l=!0,e.exports}o.m=r,o.c=n,o.d=function(t,e,r){o.o(t,e)||Object.defineProperty(t,e,{enumerable:!0,get:r})},o.r=function(t){"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(t,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(t,"__esModule",{value:!0})},o.t=function(e,t){if(1&t&&(e=o(e)),8&t)return e;if(4&t&&"object"==typ [...]
\ No newline at end of file
+!function(r){var n={};function o(t){if(n[t])return n[t].exports;var e=n[t]={i:t,l:!1,exports:{}};return r[t].call(e.exports,e,e.exports,o),e.l=!0,e.exports}o.m=r,o.c=n,o.d=function(t,e,r){o.o(t,e)||Object.defineProperty(t,e,{enumerable:!0,get:r})},o.r=function(t){"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(t,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(t,"__esModule",{value:!0})},o.t=function(e,t){if(1&t&&(e=o(e)),8&t)return e;if(4&t&&"object"==typ [...]
\ No newline at end of file
diff --git a/docs-archive/apache-airflow/2.3.0/best-practices.html b/docs-archive/apache-airflow/2.3.0/best-practices.html
index c5576fd46..baa023357 100644
--- a/docs-archive/apache-airflow/2.3.0/best-practices.html
+++ b/docs-archive/apache-airflow/2.3.0/best-practices.html
@@ -381,7 +381,7 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#backup-your-database">Backup your database</a></li>
 <li class="toctree-l2"><a class="reference internal" href="#disable-the-scheduler">Disable the scheduler</a></li>
-<li class="toctree-l2"><a class="reference internal" href="#add-integration-test-dags">Add “integration test” DAGs</a></li>
+<li class="toctree-l2"><a class="reference internal" href="#add-integration-test-dags">Add &quot;integration test&quot; DAGs</a></li>
 <li class="toctree-l2"><a class="reference internal" href="#prune-data-before-upgrading">Prune data before upgrading</a></li>
 </ul>
 </li>
@@ -580,7 +580,7 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#backup-your-database">Backup your database</a></li>
 <li class="toctree-l2"><a class="reference internal" href="#disable-the-scheduler">Disable the scheduler</a></li>
-<li class="toctree-l2"><a class="reference internal" href="#add-integration-test-dags">Add “integration test” DAGs</a></li>
+<li class="toctree-l2"><a class="reference internal" href="#add-integration-test-dags">Add &quot;integration test&quot; DAGs</a></li>
 <li class="toctree-l2"><a class="reference internal" href="#prune-data-before-upgrading">Prune data before upgrading</a></li>
 </ul>
 </li>
@@ -737,7 +737,7 @@ partition. You can use <code class="docutils literal notranslate"><span class="p
 follow this partitioning method while writing data in S3/HDFS as well.</p></li>
 <li><p>The Python datetime <code class="docutils literal notranslate"><span class="pre">now()</span></code> function gives the current datetime object. This
 function should never be used inside a task, especially to do the critical
-computation, as it leads to different outcomes on each run. It’s fine to use
+computation, as it leads to different outcomes on each run. It's fine to use
 it, for example, to generate a temporary log.</p></li>
 </ul>
 <div class="admonition tip">
@@ -770,7 +770,7 @@ Where at all possible, use <a class="reference internal" href="concepts/connecti
 <p>You should avoid writing the top level code which is not necessary to create Operators
 and build DAG relations between them. This is because of the design decision for the scheduler of Airflow
 and the impact the top-level code parsing speed on both performance and scalability of Airflow.</p>
-<p>Airflow scheduler executes the code outside the Operator’s <code class="docutils literal notranslate"><span class="pre">execute</span></code> methods with the minimum interval of
+<p>Airflow scheduler executes the code outside the Operator's <code class="docutils literal notranslate"><span class="pre">execute</span></code> methods with the minimum interval of
 <a class="reference internal" href="configurations-ref.html#config-scheduler-min-file-process-interval"><span class="std std-ref">min_file_process_interval</span></a> seconds. This is done in order
 to allow dynamic scheduling of the DAGs - where scheduling and dependencies might change over time and
 impact the next schedule of the DAG. Airflow scheduler tries to continuously make sure that what you have
@@ -840,9 +840,9 @@ than equivalent DAG where the <code class="docutils literal notranslate"><span c
 </div>
 <div class="section" id="dynamic-dag-generation">
 <h3>Dynamic DAG Generation<a class="headerlink" href="#dynamic-dag-generation" title="Permalink to this headline">¶</a></h3>
-<p>Sometimes writing DAGs manually isn’t practical.
+<p>Sometimes writing DAGs manually isn't practical.
 Maybe you have a lot of DAGs that do similar things with just a parameter changing between them.
-Or maybe you need a set of DAGs to load tables, but don’t want to manually update DAGs every time those tables change.
+Or maybe you need a set of DAGs to load tables, but don't want to manually update DAGs every time those tables change.
 In these and other cases, it can be more useful to dynamically generate DAGs.</p>
 <p>Avoiding excessive processing at the top level code described in the previous chapter is especially important
 in case of dynamic DAG configuration, which can be configured essentially in one of those ways:</p>
@@ -868,7 +868,7 @@ via Jinja template, which will delay reading the value until the task execution.
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">{{</span> <span class="n">var</span><span class="o">.</span><span class="n">json</span><span class="o">.&lt;</span><span class="n">variable_name</span><span class="o">&gt;</span> <span class="p">}}</span>
 </pre></div>
 </div>
-<p>For security purpose, you’re recommended to use the <a class="reference internal" href="security/secrets/secrets-backend/index.html#secrets-backend-configuration"><span class="std std-ref">Secrets Backend</span></a>
+<p>For security purpose, you're recommended to use the <a class="reference internal" href="security/secrets/secrets-backend/index.html#secrets-backend-configuration"><span class="std std-ref">Secrets Backend</span></a>
 for any variable that contains sensitive data.</p>
 </div>
 <div class="section" id="triggering-dags-after-changes">
@@ -894,8 +894,8 @@ each parameter by following the links):</p>
 </div>
 <div class="section" id="example-of-watcher-pattern-with-trigger-rules">
 <h3>Example of watcher pattern with trigger rules<a class="headerlink" href="#example-of-watcher-pattern-with-trigger-rules" title="Permalink to this headline">¶</a></h3>
-<p>The watcher pattern is how we call a DAG with a task that is “watching” the states of the other tasks.
-It’s primary purpose is to fail a DAG Run when any other task fail.
+<p>The watcher pattern is how we call a DAG with a task that is &quot;watching&quot; the states of the other tasks.
+It's primary purpose is to fail a DAG Run when any other task fail.
 The need came from the Airflow system tests that are DAGs with different tasks (similarly like a test containing steps).</p>
 <p>Normally, when any task fails, all other tasks are not executed and the whole DAG Run gets failed status too. But
 when we use trigger rules, we can disrupt the normal flow of running tasks and the whole DAG may represent different
@@ -913,7 +913,7 @@ executed and fail making the DAG Run fail too.</p>
 <p>Be aware that trigger rules only rely on the direct upstream (parent) tasks, e.g. <code class="docutils literal notranslate"><span class="pre">TriggerRule.ONE_FAILED</span></code>
 will ignore any failed (or <code class="docutils literal notranslate"><span class="pre">upstream_failed</span></code>) tasks that are not a direct parent of the parameterized task.</p>
 </div>
-<p>It’s easier to grab the concept with an example. Let’s say that we have the following DAG:</p>
+<p>It's easier to grab the concept with an example. Let's say that we have the following DAG:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">datetime</span> <span class="kn">import</span> <span class="n">datetime</span>
 <span class="kn">from</span> <span class="nn">airflow</span> <span class="kn">import</span> <span class="n">DAG</span>
 <span class="kn">from</span> <span class="nn">airflow.decorators</span> <span class="kn">import</span> <span class="n">task</span>
@@ -957,9 +957,9 @@ will ignore any failed (or <code class="docutils literal notranslate"><span clas
 <li><p><code class="docutils literal notranslate"><span class="pre">failing_task</span></code> always fails,</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">passing_task</span></code> always succeeds (if executed),</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">teardown</span></code> is always triggered (regardless the states of the other tasks) and it should always succeed,</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">watcher</span></code> is a downstream task for each other task, i.e. it will be triggered when any task fails and thus fail the whole DAG Run, since it’s a leaf task.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">watcher</span></code> is a downstream task for each other task, i.e. it will be triggered when any task fails and thus fail the whole DAG Run, since it's a leaf task.</p></li>
 </ul>
-<p>It’s important to note, that without <code class="docutils literal notranslate"><span class="pre">watcher</span></code> task, the whole DAG Run will get the <code class="docutils literal notranslate"><span class="pre">success</span></code> state, since the only failing task is not the leaf task, and the <code class="docutils literal notranslate"><span class="pre">teardown</span></code> task will finish with <code class="docutils literal notranslate"><span class="pre">success</span></code>.
+<p>It's important to note, that without <code class="docutils literal notranslate"><span class="pre">watcher</span></code> task, the whole DAG Run will get the <code class="docutils literal notranslate"><span class="pre">success</span></code> state, since the only failing task is not the leaf task, and the <code class="docutils literal notranslate"><span class="pre">teardown</span></code> task will finish with <code class="docutils literal notranslate"><span class="pre">success</span></code>.
 If we want the <code class="docutils literal notranslate"><span class="pre">watcher</span></code> to monitor the state of all tasks, we need to make it dependent on all of them separately. Thanks to this, we can fail the DAG Run if any of the tasks fail. Note that the watcher task has a trigger rule set to <code class="docutils literal notranslate"><span class="pre">&quot;one_failed&quot;</span></code>.
 On the other hand, without the <code class="docutils literal notranslate"><span class="pre">teardown</span></code> task, the <code class="docutils literal notranslate"><span class="pre">watcher</span></code> task will not be needed, because <code class="docutils literal notranslate"><span class="pre">failing_task</span></code> will propagate its <code class="docutils literal notranslate"><span class="pre">failed</span></code> state to downstream task <code class="docutils literal notrans [...]
 </div>
@@ -970,16 +970,16 @@ On the other hand, without the <code class="docutils literal notranslate"><span
 have many complex DAGs, their complexity might impact performance of scheduling. One of the ways to keep
 your Airflow instance performant and well utilized, you should strive to simplify and optimize your DAGs
 whenever possible - you have to remember that DAG parsing process and creation is just executing
-Python code and it’s up to you to make it as performant as possible. There are no magic recipes for making
-your DAG “less complex” - since this is a Python code, it’s the DAG writer who controls the complexity of
+Python code and it's up to you to make it as performant as possible. There are no magic recipes for making
+your DAG &quot;less complex&quot; - since this is a Python code, it's the DAG writer who controls the complexity of
 their code.</p>
-<p>There are no “metrics” for DAG complexity, especially, there are no metrics that can tell you
-whether your DAG is “simple enough”. However - as with any Python code you can definitely tell that
-your code is “simpler” or “faster” when you optimize it, the same can be said about DAG code. If you
+<p>There are no &quot;metrics&quot; for DAG complexity, especially, there are no metrics that can tell you
+whether your DAG is &quot;simple enough&quot;. However - as with any Python code you can definitely tell that
+your code is &quot;simpler&quot; or &quot;faster&quot; when you optimize it, the same can be said about DAG code. If you
 want to optimize your DAGs there are the following actions you can take:</p>
 <ul class="simple">
 <li><p>Make your DAG load faster. This is a single improvement advice that might be implemented in various ways
-but this is the one that has biggest impact on scheduler’s performance. Whenever you have a chance to make
+but this is the one that has biggest impact on scheduler's performance. Whenever you have a chance to make
 your DAG load faster - go for it, if your goal is to improve performance. Look at the
 <a class="reference internal" href="#best-practices-top-level-code"><span class="std std-ref">Top level Python Code</span></a> to get some tips of how you can do it. Also see at
 <a class="reference internal" href="#best-practices-dag-loader-test"><span class="std std-ref">DAG Loader Test</span></a> on how to asses your DAG loading time.</p></li>
@@ -1001,7 +1001,7 @@ UI of Airflow.</p></li>
 <h2>Testing a DAG<a class="headerlink" href="#testing-a-dag" title="Permalink to this headline">¶</a></h2>
 <p>Airflow users should treat DAGs as production level code, and DAGs should have various associated tests to
 ensure that they produce expected results. You can write a wide variety of tests for a DAG.
-Let’s take a look at some of them.</p>
+Let's take a look at some of them.</p>
 <div class="section" id="dag-loader-test">
 <span id="best-practices-dag-loader-test"></span><h3>DAG Loader Test<a class="headerlink" href="#dag-loader-test" title="Permalink to this headline">¶</a></h3>
 <p>This test should ensure that your DAG does not contain a piece of code that raises error while loading.
@@ -1029,7 +1029,7 @@ user    0m0.590s
 sys     0m0.108s
 </pre></div>
 </div>
-<p>The important metrics is the “real time” - which tells you how long time it took
+<p>The important metrics is the &quot;real time&quot; - which tells you how long time it took
 to process the DAG. Note that when loading the file this way, you are starting a new interpreter so there is
 an initial loading time that is not present when Airflow parses the DAG. You can assess the
 time of initialization by running:</p>
@@ -1196,17 +1196,17 @@ Do not hard code values inside the DAG and then change them manually according t
 </div>
 <div class="section" id="backup-your-database">
 <h2>Backup your database<a class="headerlink" href="#backup-your-database" title="Permalink to this headline">¶</a></h2>
-<p>It’s always a wise idea to backup the metadata database before undertaking any operation modifying the database.</p>
+<p>It's always a wise idea to backup the metadata database before undertaking any operation modifying the database.</p>
 </div>
 <div class="section" id="disable-the-scheduler">
 <h2>Disable the scheduler<a class="headerlink" href="#disable-the-scheduler" title="Permalink to this headline">¶</a></h2>
 <p>You might consider disabling the Airflow cluster while you perform such maintenance.</p>
 <p>One way to do so would be to set the param <code class="docutils literal notranslate"><span class="pre">[scheduler]</span> <span class="pre">&gt;</span> <span class="pre">use_job_schedule</span></code> to <code class="docutils literal notranslate"><span class="pre">False</span></code> and wait for any running DAGs to complete; after this no new DAG runs will be created unless externally triggered.</p>
-<p>A <em>better</em> way (though it’s a bit more manual) is to use the <code class="docutils literal notranslate"><span class="pre">dags</span> <span class="pre">pause</span></code> command.  You’ll need to keep track of the DAGs that are paused before you begin this operation so that you know which ones to unpause after maintenance is complete.  First run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">list</spa [...]
+<p>A <em>better</em> way (though it's a bit more manual) is to use the <code class="docutils literal notranslate"><span class="pre">dags</span> <span class="pre">pause</span></code> command.  You'll need to keep track of the DAGs that are paused before you begin this operation so that you know which ones to unpause after maintenance is complete.  First run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">list</spa [...]
 </div>
 <div class="section" id="add-integration-test-dags">
-<span id="integration-test-dags"></span><h2>Add “integration test” DAGs<a class="headerlink" href="#add-integration-test-dags" title="Permalink to this headline">¶</a></h2>
-<p>It can be helpful to add a couple “integration test” DAGs that use all the common services in your ecosystem (e.g. S3, Snowflake, Vault) but with dummy resources or “dev” accounts.  These test DAGs can be the ones you turn on <em>first</em> after an upgrade, because if they fail, it doesn’t matter and you can revert to your backup without negative consequences.  However, if they succeed, they should prove that your cluster is able to run tasks with the libraries and services that you  [...]
+<span id="integration-test-dags"></span><h2>Add &quot;integration test&quot; DAGs<a class="headerlink" href="#add-integration-test-dags" title="Permalink to this headline">¶</a></h2>
+<p>It can be helpful to add a couple &quot;integration test&quot; DAGs that use all the common services in your ecosystem (e.g. S3, Snowflake, Vault) but with dummy resources or &quot;dev&quot; accounts.  These test DAGs can be the ones you turn on <em>first</em> after an upgrade, because if they fail, it doesn't matter and you can revert to your backup without negative consequences.  However, if they succeed, they should prove that your cluster is able to run tasks with the libraries an [...]
 <p>For example, if you use an external secrets backend, make sure you have a task that retrieves a connection.  If you use KubernetesPodOperator, add a task that runs <code class="docutils literal notranslate"><span class="pre">sleep</span> <span class="pre">30;</span> <span class="pre">echo</span> <span class="pre">&quot;hello&quot;</span></code>.  If you need to write to s3, do so in a test task.  And if you need to access a database, add a task that does <code class="docutils literal  [...]
 </div>
 <div class="section" id="prune-data-before-upgrading">
@@ -1318,7 +1318,7 @@ Do not hard code values inside the DAG and then change them manually according t
 </li>
 <li><a class="reference internal" href="#backup-your-database">Backup your database</a></li>
 <li><a class="reference internal" href="#disable-the-scheduler">Disable the scheduler</a></li>
-<li><a class="reference internal" href="#add-integration-test-dags">Add “integration test” DAGs</a></li>
+<li><a class="reference internal" href="#add-integration-test-dags">Add &quot;integration test&quot; DAGs</a></li>
 <li><a class="reference internal" href="#prune-data-before-upgrading">Prune data before upgrading</a></li>
 </ul>
 </li>
diff --git a/docs-archive/apache-airflow/2.3.0/cli-and-env-variables-ref.html b/docs-archive/apache-airflow/2.3.0/cli-and-env-variables-ref.html
index 20cfe7d10..f4ee33fce 100644
--- a/docs-archive/apache-airflow/2.3.0/cli-and-env-variables-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/cli-and-env-variables-ref.html
@@ -1699,7 +1699,7 @@ development and testing.</p>
 <dl class="option-list">
 <dt><kbd>-A, --basic-auth</kbd></dt>
 <dd><p>Securing Flower with Basic Authentication. Accepts user:password pairs separated by a comma. Example: flower_basic_auth = user1:password1,user2:password2</p>
-<p>Default: “”</p>
+<p>Default: &quot;&quot;</p>
 </dd>
 <dt><kbd>-a, --broker-api</kbd></dt>
 <dd><p>Broker API</p>
@@ -1713,7 +1713,7 @@ development and testing.</p>
 </dd>
 <dt><kbd>-H, --hostname</kbd></dt>
 <dd><p>Set the hostname on which to run the server</p>
-<p>Default: “0.0.0.0”</p>
+<p>Default: &quot;0.0.0.0&quot;</p>
 </dd>
 <dt><kbd>-l, --log-file</kbd></dt>
 <dd><p>Location of the log file</p>
@@ -1733,7 +1733,7 @@ development and testing.</p>
 </dd>
 <dt><kbd>-u, --url-prefix</kbd></dt>
 <dd><p>URL prefix for Flower</p>
-<p>Default: “”</p>
+<p>Default: &quot;&quot;</p>
 </dd>
 </dl>
 </div>
@@ -1787,10 +1787,10 @@ development and testing.</p>
 </dd>
 <dt><kbd>-q, --queues</kbd></dt>
 <dd><p>Comma delimited list of queues to serve</p>
-<p>Default: “default”</p>
+<p>Default: &quot;default&quot;</p>
 </dd>
 <dt><kbd>-s, --skip-serve-logs</kbd></dt>
-<dd><p>Don’t start the serve logs process along with the workers</p>
+<dd><p>Don't start the serve logs process along with the workers</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>--stderr</kbd></dt>
@@ -1801,7 +1801,7 @@ development and testing.</p>
 </dd>
 <dt><kbd>-u, --umask</kbd></dt>
 <dd><p>Set the umask of celery worker in daemon mode</p>
-<p>Default: “0o077”</p>
+<p>Default: &quot;0o077&quot;</p>
 </dd>
 <dt><kbd>--without-gossip</kbd></dt>
 <dd><p>Don’t subscribe to other workers events</p>
@@ -1869,16 +1869,16 @@ development and testing.</p>
 <div class="section" id="list">
 <h6>list<a class="headerlink" href="#list" title="Permalink to this headline">¶</a></h6>
 <p>List options for the configuration</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">config</span> <span class="nb">list</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">auto</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n">off [...]
+<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">config</span> <span class="nb">list</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">off</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n">auto [...]
 </pre></div>
 </div>
 <div class="section" id="Named Arguments_repeat4">
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat4" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>--color</kbd></dt>
-<dd><p>Possible choices: auto, on, off</p>
+<dd><p>Possible choices: off, on, auto</p>
 <p>Do emit colored output (default: auto)</p>
-<p>Default: “auto”</p>
+<p>Default: &quot;auto&quot;</p>
 </dd>
 </dl>
 </div>
@@ -1960,7 +1960,7 @@ development and testing.</p>
 <div class="section" id="delete">
 <h6>delete<a class="headerlink" href="#delete" title="Permalink to this headline">¶</a></h6>
 <p>Delete a connection</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">connections</span> <span class="n">delete</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">auto</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class=" [...]
+<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">connections</span> <span class="n">delete</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">off</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n [...]
 </pre></div>
 </div>
 <div class="section" id="Positional Arguments_repeat6">
@@ -1975,9 +1975,9 @@ development and testing.</p>
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat6" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>--color</kbd></dt>
-<dd><p>Possible choices: auto, on, off</p>
+<dd><p>Possible choices: off, on, auto</p>
 <p>Do emit colored output (default: auto)</p>
-<p>Default: “auto”</p>
+<p>Default: &quot;auto&quot;</p>
 </dd>
 </dl>
 </div>
@@ -1988,11 +1988,11 @@ development and testing.</p>
 airflow connections export -
 The file format can be determined by the provided file extension. E.g., The following command will export the connections in JSON format:
 airflow connections export /tmp/connections.json
-The –file-format parameter can be used to control the file format. E.g., the default format is JSON in STDOUT mode, which can be overridden using:
-airflow connections export - –file-format yaml
-The –file-format parameter can also be used for the files, for example:
-airflow connections export /tmp/connections –file-format json.
-When exporting in <cite>env</cite> file format, you control whether URI format or JSON format is used to serialize the connection by passing <cite>uri</cite> or <cite>json</cite> with option <cite>–serialization-format</cite>.</p>
+The --file-format parameter can be used to control the file format. E.g., the default format is JSON in STDOUT mode, which can be overridden using:
+airflow connections export - --file-format yaml
+The --file-format parameter can also be used for the files, for example:
+airflow connections export /tmp/connections --file-format json.
+When exporting in <cite>env</cite> file format, you control whether URI format or JSON format is used to serialize the connection by passing <cite>uri</cite> or <cite>json</cite> with option <cite>--serialization-format</cite>.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">connections</span> <span class="n">export</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">file</span><span class="o">-</span><span class="nb">format</span> <span class="p">{</span><span class="n">json</span><span class="p">,</span><span cla [...]
                            <span class="p">[</span><span class="o">--</span><span class="nb">format</span> <span class="p">{</span><span class="n">json</span><span class="p">,</span><span class="n">yaml</span><span class="p">,</span><span class="n">env</span><span class="p">}]</span>
                            <span class="p">[</span><span class="o">--</span><span class="n">serialization</span><span class="o">-</span><span class="nb">format</span> <span class="p">{</span><span class="n">json</span><span class="p">,</span><span class="n">uri</span><span class="p">}]</span>
@@ -2016,7 +2016,7 @@ When exporting in <cite>env</cite> file format, you control whether URI format o
 </dd>
 <dt><kbd>--format</kbd></dt>
 <dd><p>Possible choices: json, yaml, env</p>
-<p>Deprecated – use <cite>–file-format</cite> instead. File format to use for the export.</p>
+<p>Deprecated -- use <cite>--file-format</cite> instead. File format to use for the export.</p>
 </dd>
 <dt><kbd>--serialization-format</kbd></dt>
 <dd><p>Possible choices: json, uri</p>
@@ -2028,7 +2028,7 @@ When exporting in <cite>env</cite> file format, you control whether URI format o
 <div class="section" id="get">
 <h6>get<a class="headerlink" href="#get" title="Permalink to this headline">¶</a></h6>
 <p>Get a connection</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">connections</span> <span class="n">get</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">auto</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n"> [...]
+<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">connections</span> <span class="n">get</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">off</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n">a [...]
                         <span class="p">[</span><span class="o">-</span><span class="n">o</span> <span class="n">table</span><span class="p">,</span> <span class="n">json</span><span class="p">,</span> <span class="n">yaml</span><span class="p">,</span> <span class="n">plain</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">v</span><span class="p">]</span>
                         <span class="n">conn_id</span>
 </pre></div>
@@ -2045,14 +2045,14 @@ When exporting in <cite>env</cite> file format, you control whether URI format o
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat8" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>--color</kbd></dt>
-<dd><p>Possible choices: auto, on, off</p>
+<dd><p>Possible choices: off, on, auto</p>
 <p>Do emit colored output (default: auto)</p>
-<p>Default: “auto”</p>
+<p>Default: &quot;auto&quot;</p>
 </dd>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2093,7 +2093,7 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2139,8 +2139,8 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dd><p>Redirect stdout to this file</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2184,7 +2184,7 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat11" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>-c, --conf</kbd></dt>
-<dd><p>JSON string that gets pickled into the DagRun’s conf attribute</p>
+<dd><p>JSON string that gets pickled into the DagRun's conf attribute</p>
 </dd>
 <dt><kbd>--continue-on-failures</kbd></dt>
 <dd><p>if set, the backfill will keep going even if some of the tasks failed</p>
@@ -2240,8 +2240,8 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dd><p>Override start_date YYYY-MM-DD</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-t, --task-regex</kbd></dt>
 <dd><p>The regex to filter specific task_ids to backfill (optional)</p>
@@ -2293,11 +2293,11 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2319,11 +2319,11 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2351,7 +2351,7 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>--state</kbd></dt>
 <dd><p>Only list the dag runs corresponding to the state</p>
@@ -2387,7 +2387,7 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-s, --start-date</kbd></dt>
 <dd><p>Override start_date YYYY-MM-DD</p>
@@ -2424,8 +2424,8 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <p>Default: 1</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2448,8 +2448,8 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat18" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2466,11 +2466,11 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2497,14 +2497,14 @@ The filetype must by json, yaml or env and will be automatically inferred.</p>
 </div>
 <div class="section" id="show">
 <h6>show<a class="headerlink" href="#show" title="Permalink to this headline">¶</a></h6>
-<p>The –imgcat option only works in iTerm.</p>
+<p>The --imgcat option only works in iTerm.</p>
 <p>For more information, see: <a class="reference external" href="https://www.iterm2.com/documentation-images.html">https://www.iterm2.com/documentation-images.html</a></p>
-<p>The –save option saves the result to the indicated file.</p>
+<p>The --save option saves the result to the indicated file.</p>
 <p>The file format is determined by the file extension. For more information about supported format, see: <a class="reference external" href="https://www.graphviz.org/doc/info/output.html">https://www.graphviz.org/doc/info/output.html</a></p>
 <p>If you want to create a PNG file then you should execute the following command:
-airflow dags show &lt;DAG_ID&gt; –save output.png</p>
+airflow dags show &lt;DAG_ID&gt; --save output.png</p>
 <p>If you want to create a DOT file then you should execute the following command:
-airflow dags show &lt;DAG_ID&gt; –save output.dot</p>
+airflow dags show &lt;DAG_ID&gt; --save output.dot</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">dags</span> <span class="n">show</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">imgcat</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">s</span> <span class="n">SAVE</span><span class="p">]</sp [...]
 </pre></div>
 </div>
@@ -2527,22 +2527,22 @@ airflow dags show &lt;DAG_ID&gt; –save output.dot</p>
 <dd><p>Saves the result to the indicated file.</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
 </div>
 <div class="section" id="show-dependencies">
 <h6>show-dependencies<a class="headerlink" href="#show-dependencies" title="Permalink to this headline">¶</a></h6>
-<p>The –imgcat option only works in iTerm.</p>
+<p>The --imgcat option only works in iTerm.</p>
 <p>For more information, see: <a class="reference external" href="https://www.iterm2.com/documentation-images.html">https://www.iterm2.com/documentation-images.html</a></p>
-<p>The –save option saves the result to the indicated file.</p>
+<p>The --save option saves the result to the indicated file.</p>
 <p>The file format is determined by the file extension. For more information about supported format, see: <a class="reference external" href="https://www.graphviz.org/doc/info/output.html">https://www.graphviz.org/doc/info/output.html</a></p>
 <p>If you want to create a PNG file then you should execute the following command:
-airflow dags show-dependencies –save output.png</p>
+airflow dags show-dependencies --save output.png</p>
 <p>If you want to create a DOT file then you should execute the following command:
-airflow dags show-dependencies –save output.dot</p>
+airflow dags show-dependencies --save output.dot</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">dags</span> <span class="n">show</span><span class="o">-</span><span class="n">dependencies</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">imgcat</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n [...]
 </pre></div>
 </div>
@@ -2557,8 +2557,8 @@ airflow dags show-dependencies –save output.dot</p>
 <dd><p>Saves the result to the indicated file.</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2584,8 +2584,8 @@ airflow dags show-dependencies –save output.dot</p>
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat23" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2593,14 +2593,14 @@ airflow dags show-dependencies –save output.dot</p>
 <div class="section" id="test">
 <h6>test<a class="headerlink" href="#test" title="Permalink to this headline">¶</a></h6>
 <p>Execute one single DagRun for a given DAG and execution date, using the DebugExecutor.</p>
-<p>The –imgcat-dagrun option only works in iTerm.</p>
+<p>The --imgcat-dagrun option only works in iTerm.</p>
 <p>For more information, see: <a class="reference external" href="https://www.iterm2.com/documentation-images.html">https://www.iterm2.com/documentation-images.html</a></p>
-<p>If –save-dagrun is used, then, after completing the backfill, saves the diagram for current DAG Run to the indicated file.
+<p>If --save-dagrun is used, then, after completing the backfill, saves the diagram for current DAG Run to the indicated file.
 The file format is determined by the file extension. For more information about supported format, see: <a class="reference external" href="https://www.graphviz.org/doc/info/output.html">https://www.graphviz.org/doc/info/output.html</a></p>
 <p>If you want to create a PNG file then you should execute the following command:
-airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.png</p>
+airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; --save-dagrun output.png</p>
 <p>If you want to create a DOT file then you should execute the following command:
-airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.dot</p>
+airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; --save-dagrun output.dot</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">dags</span> <span class="n">test</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">imgcat</span><span class="o">-</span><span class="n">dagrun</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">sav [...]
                   <span class="p">[</span><span class="o">--</span><span class="n">show</span><span class="o">-</span><span class="n">dagrun</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">S</span> <span class="n">SUBDIR</span><span class="p">]</span>
                   <span class="n">dag_id</span> <span class="n">execution_date</span>
@@ -2633,8 +2633,8 @@ airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.do
 <p>Default: False</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2658,7 +2658,7 @@ airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.do
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat25" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>-c, --conf</kbd></dt>
-<dd><p>JSON string that gets pickled into the DagRun’s conf attribute</p>
+<dd><p>JSON string that gets pickled into the DagRun's conf attribute</p>
 </dd>
 <dt><kbd>-e, --exec-date</kbd></dt>
 <dd><p>The execution date of the DAG</p>
@@ -2667,8 +2667,8 @@ airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.do
 <dd><p>Helps to identify this run</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2691,8 +2691,8 @@ airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.do
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat26" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -2751,7 +2751,7 @@ airflow dags test &lt;DAG_ID&gt; &lt;EXECUTION_DATE&gt; –save-dagrun output.do
 <dt><kbd>--clean-before-timestamp</kbd></dt>
 <dd><p>The date or timestamp before which data should be purged.
 If no timezone info is supplied then dates are assumed to be in airflow default timezone.
-Example: ‘2022-01-01 00:00:00+01:00’</p>
+Example: '2022-01-01 00:00:00+01:00'</p>
 </dd>
 <dt><kbd>--dry-run</kbd></dt>
 <dd><p>Perform a dry run</p>
@@ -2759,7 +2759,7 @@ Example: ‘2022-01-01 00:00:00+01:00’</p>
 </dd>
 <dt><kbd>-t, --tables</kbd></dt>
 <dd><p>Table names to perform maintenance on (use comma-separated list).
-Options: [‘callback_request’, ‘celery_taskmeta’, ‘celery_tasksetmeta’, ‘dag’, ‘dag_run’, ‘import_error’, ‘job’, ‘log’, ‘rendered_task_instance_fields’, ‘sensor_instance’, ‘sla_miss’, ‘task_fail’, ‘task_instance’, ‘task_reschedule’, ‘xcom’]</p>
+Options: ['callback_request', 'celery_taskmeta', 'celery_tasksetmeta', 'dag', 'dag_run', 'import_error', 'job', 'log', 'rendered_task_instance_fields', 'sensor_instance', 'sla_miss', 'task_fail', 'task_instance', 'task_reschedule', 'xcom']</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2774,7 +2774,7 @@ Options: [‘callback_request’, ‘celery_taskmeta’, ‘celery_tasksetmeta
 </div>
 <div class="section" id="downgrade">
 <h6>downgrade<a class="headerlink" href="#downgrade" title="Permalink to this headline">¶</a></h6>
-<p>Downgrade the schema of the metadata database. You must provide either <cite>–to-revision</cite> or <cite>–to-version</cite>. To print but not execute commands, use option <cite>–show-sql-only</cite>. If using options <cite>–from-revision</cite> or <cite>–from-version</cite>, you must also use <cite>–show-sql-only</cite>, because if actually <em>running</em> migrations, we should only migrate from the <em>current</em> Alembic revision.</p>
+<p>Downgrade the schema of the metadata database. You must provide either <cite>--to-revision</cite> or <cite>--to-version</cite>. To print but not execute commands, use option <cite>--show-sql-only</cite>. If using options <cite>--from-revision</cite> or <cite>--from-version</cite>, you must also use <cite>--show-sql-only</cite>, because if actually <em>running</em> migrations, we should only migrate from the <em>current</em> Alembic revision.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">db</span> <span class="n">downgrade</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">from</span><span class="o">-</span><span class="n">revision</span> <span class="n">FROM_REVISION</span><span class="p">]</span>
                      <span class="p">[</span><span class="o">--</span><span class="n">from</span><span class="o">-</span><span class="n">version</span> <span class="n">FROM_VERSION</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">s</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">r</span> <span class="n">TO_REVISION</span><span class="p">]</span>
                      <span class="p">[</span><span class="o">-</span><span class="n">n</span> <span class="n">TO_VERSION</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">y</span><span class="p">]</span>
@@ -2790,11 +2790,11 @@ Options: [‘callback_request’, ‘celery_taskmeta’, ‘celery_tasksetmeta
 <dd><p>(Optional) If generating sql, may supply a <em>from</em> version</p>
 </dd>
 <dt><kbd>-s, --show-sql-only</kbd></dt>
-<dd><p>Don’t actually run migrations; just print out sql scripts for offline migration. Required if using either <cite>–from-version</cite> or <cite>–from-version</cite>.</p>
+<dd><p>Don't actually run migrations; just print out sql scripts for offline migration. Required if using either <cite>--from-version</cite> or <cite>--from-version</cite>.</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>-r, --to-revision</kbd></dt>
-<dd><p>The Alembic revision to downgrade to. Note: must provide either <cite>–to-revision</cite> or <cite>–to-version</cite>.</p>
+<dd><p>The Alembic revision to downgrade to. Note: must provide either <cite>--to-revision</cite> or <cite>--to-version</cite>.</p>
 </dd>
 <dt><kbd>-n, --to-version</kbd></dt>
 <dd><p>(Optional) If provided, only run migrations up to this version.</p>
@@ -2858,14 +2858,14 @@ Options: [‘callback_request’, ‘celery_taskmeta’, ‘celery_tasksetmeta
 <dd><p>(Optional) If generating sql, may supply a <em>from</em> version</p>
 </dd>
 <dt><kbd>-s, --show-sql-only</kbd></dt>
-<dd><p>Don’t actually run migrations; just print out sql scripts for offline migration. Required if using either <cite>–from-version</cite> or <cite>–from-version</cite>.</p>
+<dd><p>Don't actually run migrations; just print out sql scripts for offline migration. Required if using either <cite>--from-version</cite> or <cite>--from-version</cite>.</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>-r, --to-revision</kbd></dt>
 <dd><p>(Optional) If provided, only run migrations up to and including this Alembic revision.</p>
 </dd>
 <dt><kbd>-n, --to-version</kbd></dt>
-<dd><p>(Optional) The airflow version to upgrade to. Note: must provide either <cite>–to-revision</cite> or <cite>–to-version</cite>.</p>
+<dd><p>(Optional) The airflow version to upgrade to. Note: must provide either <cite>--to-revision</cite> or <cite>--to-version</cite>.</p>
 </dd>
 </dl>
 </div>
@@ -2892,7 +2892,7 @@ Options: [‘callback_request’, ‘celery_taskmeta’, ‘celery_tasksetmeta
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -2948,11 +2948,11 @@ Options: [‘callback_request’, ‘celery_taskmeta’, ‘celery_tasksetmeta
 <p>examples:
 To check if the local scheduler is still working properly, run:</p>
 <blockquote>
-<div><p>$ airflow jobs check –job-type SchedulerJob –hostname “$(hostname)”</p>
+<div><p>$ airflow jobs check --job-type SchedulerJob --hostname &quot;$(hostname)&quot;</p>
 </div></blockquote>
 <p>To check if any scheduler is running when you are using high availability, run:</p>
 <blockquote>
-<div><p>$ airflow jobs check –job-type SchedulerJob –allow-multiple –limit 100</p>
+<div><p>$ airflow jobs check --job-type SchedulerJob --allow-multiple --limit 100</p>
 </div></blockquote>
 </div>
 </div>
@@ -2982,7 +2982,7 @@ To check if the local scheduler is still working properly, run:</p>
 </dd>
 <dt><kbd>-k, --keytab</kbd></dt>
 <dd><p>keytab</p>
-<p>Default: “airflow.keytab”</p>
+<p>Default: &quot;airflow.keytab&quot;</p>
 </dd>
 <dt><kbd>-l, --log-file</kbd></dt>
 <dd><p>Location of the log file</p>
@@ -3032,7 +3032,7 @@ To check if the local scheduler is still working properly, run:</p>
 </dd>
 <dt><kbd>--namespace</kbd></dt>
 <dd><p>Kubernetes Namespace. Default value is <cite>[kubernetes] namespace</cite> in configuration.</p>
-<p>Default: “default”</p>
+<p>Default: &quot;default&quot;</p>
 </dd>
 </dl>
 </div>
@@ -3060,11 +3060,11 @@ To check if the local scheduler is still working properly, run:</p>
 <dl class="option-list">
 <dt><kbd>-o, --output-path</kbd></dt>
 <dd><p>The output for generated yaml files</p>
-<p>Default: “[CWD]”</p>
+<p>Default: &quot;[CWD]&quot;</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -3083,7 +3083,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3128,7 +3128,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3172,7 +3172,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3223,7 +3223,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3259,7 +3259,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3298,7 +3298,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3319,7 +3319,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3331,7 +3331,7 @@ To check if the local scheduler is still working properly, run:</p>
 <div class="section" id="get_repeat2">
 <h6>get<a class="headerlink" href="#get_repeat2" title="Permalink to this headline">¶</a></h6>
 <p>Get detailed information about a provider</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">providers</span> <span class="n">get</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">auto</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n">of [...]
+<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">providers</span> <span class="n">get</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="n">color</span> <span class="p">{</span><span class="n">off</span><span class="p">,</span><span class="n">on</span><span class="p">,</span><span class="n">aut [...]
                       <span class="p">[</span><span class="o">-</span><span class="n">o</span> <span class="n">table</span><span class="p">,</span> <span class="n">json</span><span class="p">,</span> <span class="n">yaml</span><span class="p">,</span> <span class="n">plain</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">v</span><span class="p">]</span>
                       <span class="n">provider_name</span>
 </pre></div>
@@ -3348,9 +3348,9 @@ To check if the local scheduler is still working properly, run:</p>
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat45" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>--color</kbd></dt>
-<dd><p>Possible choices: auto, on, off</p>
+<dd><p>Possible choices: off, on, auto</p>
 <p>Do emit colored output (default: auto)</p>
-<p>Default: “auto”</p>
+<p>Default: &quot;auto&quot;</p>
 </dd>
 <dt><kbd>-f, --full</kbd></dt>
 <dd><p>Full information about the provider, including documentation information.</p>
@@ -3359,7 +3359,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3380,7 +3380,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3401,7 +3401,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3422,7 +3422,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3443,7 +3443,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3464,7 +3464,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3485,7 +3485,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3600,7 +3600,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3647,7 +3647,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dd><p>PID file location</p>
 </dd>
 <dt><kbd>-s, --skip-serve-logs</kbd></dt>
-<dd><p>Don’t start the serve logs process along with the workers</p>
+<dd><p>Don't start the serve logs process along with the workers</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>--stderr</kbd></dt>
@@ -3657,8 +3657,8 @@ To check if the local scheduler is still working properly, run:</p>
 <dd><p>Redirect stdout to this file</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -3667,7 +3667,7 @@ To check if the local scheduler is still working properly, run:</p>
 <div><ul>
 <li><p>SIGUSR2: Dump a snapshot of task state being tracked by the executor.</p>
 <dl class="simple">
-<dt>Example:</dt><dd><p>pkill -f -USR2 “airflow scheduler”</p>
+<dt>Example:</dt><dd><p>pkill -f -USR2 &quot;airflow scheduler&quot;</p>
 </dd>
 </dl>
 </li>
@@ -3763,8 +3763,8 @@ To check if the local scheduler is still working properly, run:</p>
 <dd><p>Override start_date YYYY-MM-DD</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-t, --task-regex</kbd></dt>
 <dd><p>The regex to filter specific task_ids to backfill (optional)</p>
@@ -3782,7 +3782,7 @@ To check if the local scheduler is still working properly, run:</p>
 </div>
 <div class="section" id="failed-deps">
 <h6>failed-deps<a class="headerlink" href="#failed-deps" title="Permalink to this headline">¶</a></h6>
-<p>Returns the unmet dependencies for a task instance from the perspective of the scheduler. In other words, why a task instance doesn’t get scheduled and then queued by the scheduler, and then run by an executor.</p>
+<p>Returns the unmet dependencies for a task instance from the perspective of the scheduler. In other words, why a task instance doesn't get scheduled and then queued by the scheduler, and then run by an executor.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">tasks</span> <span class="n">failed</span><span class="o">-</span><span class="n">deps</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="nb">map</span><span class="o">-</span><span class="n">index</span> <span class="n">MAP_INDEX</span><span cla [...]
                           <span class="n">dag_id</span> <span class="n">task_id</span> <span class="n">execution_date_or_run_id</span>
 </pre></div>
@@ -3809,8 +3809,8 @@ To check if the local scheduler is still working properly, run:</p>
 <p>Default: -1</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -3833,8 +3833,8 @@ To check if the local scheduler is still working properly, run:</p>
 <h7>Named Arguments<a class="headerlink" href="#Named Arguments_repeat60" title="Permalink to this headline">¶</a></h7>
 <dl class="option-list">
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-t, --tree</kbd></dt>
 <dd><p>Tree view</p>
@@ -3849,7 +3849,7 @@ To check if the local scheduler is still working properly, run:</p>
 </div>
 <div class="section" id="render">
 <h6>render<a class="headerlink" href="#render" title="Permalink to this headline">¶</a></h6>
-<p>Render a task instance’s template(s)</p>
+<p>Render a task instance's template(s)</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">airflow</span> <span class="n">tasks</span> <span class="n">render</span> <span class="p">[</span><span class="o">-</span><span class="n">h</span><span class="p">]</span> <span class="p">[</span><span class="o">--</span><span class="nb">map</span><span class="o">-</span><span class="n">index</span> <span class="n">MAP_INDEX</span><span class="p">]</span> <span class="p">[</span><span class [...]
                      <span class="n">dag_id</span> <span class="n">task_id</span> <span class="n">execution_date_or_run_id</span>
 </pre></div>
@@ -3876,8 +3876,8 @@ To check if the local scheduler is still working properly, run:</p>
 <p>Default: -1</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -3961,8 +3961,8 @@ To check if the local scheduler is still working properly, run:</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 </dl>
 </div>
@@ -3996,8 +3996,8 @@ To check if the local scheduler is still working properly, run:</p>
 <p>Default: -1</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -4030,7 +4030,7 @@ To check if the local scheduler is still working properly, run:</p>
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -4080,8 +4080,8 @@ To check if the local scheduler is still working properly, run:</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>-S, --subdir</kbd></dt>
-<dd><p>File location or directory from which to look for the dag. Defaults to ‘[AIRFLOW_HOME]/dags’ where [AIRFLOW_HOME] is the value you set for ‘AIRFLOW_HOME’ config you set in ‘airflow.cfg’</p>
-<p>Default: “[AIRFLOW_HOME]/dags”</p>
+<dd><p>File location or directory from which to look for the dag. Defaults to '[AIRFLOW_HOME]/dags' where [AIRFLOW_HOME] is the value you set for 'AIRFLOW_HOME' config you set in 'airflow.cfg'</p>
+<p>Default: &quot;[AIRFLOW_HOME]/dags&quot;</p>
 </dd>
 <dt><kbd>-t, --task-params</kbd></dt>
 <dd><p>Sends a JSON params dict to the task</p>
@@ -4180,13 +4180,13 @@ To check if the local scheduler is still working properly, run:</p>
 <dd><p>Last name of the user</p>
 </dd>
 <dt><kbd>-p, --password</kbd></dt>
-<dd><p>Password of the user, required to create a user without –use-random-password</p>
+<dd><p>Password of the user, required to create a user without --use-random-password</p>
 </dd>
 <dt><kbd>-r, --role</kbd></dt>
 <dd><p>Role of the user. Existing roles include Admin, User, Op, Viewer, and Public</p>
 </dd>
 <dt><kbd>--use-random-password</kbd></dt>
-<dd><p>Do not prompt for password. Use random string instead. Required to create a user without –password</p>
+<dd><p>Do not prompt for password. Use random string instead. Required to create a user without --password</p>
 <p>Default: False</p>
 </dd>
 <dt><kbd>-u, --username</kbd></dt>
@@ -4195,10 +4195,10 @@ To check if the local scheduler is still working properly, run:</p>
 </dl>
 </div>
 <p>examples:
-To create an user with “Admin” role and username equals to “admin”, run:</p>
+To create an user with &quot;Admin&quot; role and username equals to &quot;admin&quot;, run:</p>
 <blockquote>
 <div><dl class="simple">
-<dt>$ airflow users create </dt><dd><p>–username admin –firstname FIRST_NAME –lastname LAST_NAME –role Admin –email <a class="reference external" href="mailto:admin&#37;&#52;&#48;example&#46;org">admin<span>&#64;</span>example<span>&#46;</span>org</a></p>
+<dt>$ airflow users create </dt><dd><p>--username admin --firstname FIRST_NAME --lastname LAST_NAME --role Admin --email <a class="reference external" href="mailto:admin&#37;&#52;&#48;example&#46;org">admin<span>&#64;</span>example<span>&#46;</span>org</a></p>
 </dd>
 </dl>
 </div></blockquote>
@@ -4274,7 +4274,7 @@ To create an user with “Admin” role and username equals to “admin”, run:
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -4410,7 +4410,7 @@ To create an user with “Admin” role and username equals to “admin”, run:
 <dt><kbd>-o, --output</kbd></dt>
 <dd><p>Possible choices: table, json, yaml, plain</p>
 <p>Output format. Allowed values: json, yaml, plain, table (default: table)</p>
-<p>Default: “table”</p>
+<p>Default: &quot;table&quot;</p>
 </dd>
 <dt><kbd>-v, --verbose</kbd></dt>
 <dd><p>Make logging output more verbose</p>
@@ -4469,12 +4469,12 @@ To create an user with “Admin” role and username equals to “admin”, run:
 <h5>Named Arguments<a class="headerlink" href="#Named Arguments_repeat75" title="Permalink to this headline">¶</a></h5>
 <dl class="option-list">
 <dt><kbd>-A, --access-logfile</kbd></dt>
-<dd><p>The logfile to store the webserver access log. Use ‘-‘ to print to stderr</p>
-<p>Default: “-“</p>
+<dd><p>The logfile to store the webserver access log. Use '-' to print to stderr</p>
+<p>Default: &quot;-&quot;</p>
 </dd>
 <dt><kbd>-L, --access-logformat</kbd></dt>
 <dd><p>The access log format for gunicorn logs</p>
-<p>Default: “”</p>
+<p>Default: &quot;&quot;</p>
 </dd>
 <dt><kbd>-D, --daemon</kbd></dt>
 <dd><p>Daemonize instead of running in the foreground</p>
@@ -4485,12 +4485,12 @@ To create an user with “Admin” role and username equals to “admin”, run:
 <p>Default: False</p>
 </dd>
 <dt><kbd>-E, --error-logfile</kbd></dt>
-<dd><p>The logfile to store the webserver error log. Use ‘-‘ to print to stderr</p>
-<p>Default: “-“</p>
+<dd><p>The logfile to store the webserver error log. Use '-' to print to stderr</p>
+<p>Default: &quot;-&quot;</p>
 </dd>
 <dt><kbd>-H, --hostname</kbd></dt>
 <dd><p>Set the hostname on which to run the web server</p>
-<p>Default: “0.0.0.0”</p>
+<p>Default: &quot;0.0.0.0&quot;</p>
 </dd>
 <dt><kbd>-l, --log-file</kbd></dt>
 <dd><p>Location of the log file</p>
@@ -4504,11 +4504,11 @@ To create an user with “Admin” role and username equals to “admin”, run:
 </dd>
 <dt><kbd>--ssl-cert</kbd></dt>
 <dd><p>Path to the SSL certificate for the webserver</p>
-<p>Default: “”</p>
+<p>Default: &quot;&quot;</p>
 </dd>
 <dt><kbd>--ssl-key</kbd></dt>
 <dd><p>Path to the key to use with the SSL certificate</p>
-<p>Default: “”</p>
+<p>Default: &quot;&quot;</p>
 </dd>
 <dt><kbd>--stderr</kbd></dt>
 <dd><p>Redirect stderr to this file</p>
@@ -4523,7 +4523,7 @@ To create an user with “Admin” role and username equals to “admin”, run:
 <dt><kbd>-k, --workerclass</kbd></dt>
 <dd><p>Possible choices: sync, eventlet, gevent, tornado</p>
 <p>The worker class to use for Gunicorn</p>
-<p>Default: “sync”</p>
+<p>Default: &quot;sync&quot;</p>
 </dd>
 <dt><kbd>-w, --workers</kbd></dt>
 <dd><p>Number of workers to run the webserver on</p>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/cluster-policies.html b/docs-archive/apache-airflow/2.3.0/concepts/cluster-policies.html
index 15d7e72d0..acafe068a 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/cluster-policies.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/cluster-policies.html
@@ -717,7 +717,7 @@
 <li><p><code class="docutils literal notranslate"><span class="pre">task_instance_mutation_hook</span></code>: Takes a <a class="reference internal" href="../_api/airflow/models/taskinstance/index.html#airflow.models.taskinstance.TaskInstance" title="airflow.models.taskinstance.TaskInstance"><code class="xref py py-class docutils literal notranslate"><span class="pre">TaskInstance</span></code></a> parameter called <code class="docutils literal notranslate"><span class="pre">task_instanc [...]
 </ul>
 <p>The DAG and Task cluster policies can raise the  <a class="reference internal" href="../_api/airflow/exceptions/index.html#airflow.exceptions.AirflowClusterPolicyViolation" title="airflow.exceptions.AirflowClusterPolicyViolation"><code class="xref py py-class docutils literal notranslate"><span class="pre">AirflowClusterPolicyViolation</span></code></a> exception to indicate that the dag/task they were passed is not compliant and should not be loaded.</p>
-<p>Any extra attributes set by a cluster policy take priority over those defined in your DAG file; for example, if you set an <code class="docutils literal notranslate"><span class="pre">sla</span></code> on your Task in the DAG file, and then your cluster policy also sets an <code class="docutils literal notranslate"><span class="pre">sla</span></code>, the cluster policy’s value will take precedence.</p>
+<p>Any extra attributes set by a cluster policy take priority over those defined in your DAG file; for example, if you set an <code class="docutils literal notranslate"><span class="pre">sla</span></code> on your Task in the DAG file, and then your cluster policy also sets an <code class="docutils literal notranslate"><span class="pre">sla</span></code>, the cluster policy's value will take precedence.</p>
 <p>To configure cluster policies, you should create an <code class="docutils literal notranslate"><span class="pre">airflow_local_settings.py</span></code> file in either the <code class="docutils literal notranslate"><span class="pre">config</span></code> folder under your <code class="docutils literal notranslate"><span class="pre">$AIRFLOW_HOME</span></code>, or place it on the <code class="docutils literal notranslate"><span class="pre">$PYTHONPATH</span></code>, and then add callabl [...]
 <div class="section" id="examples">
 <h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">¶</a></h2>
@@ -742,7 +742,7 @@
 </div>
 <div class="section" id="task-policies">
 <h2>Task policies<a class="headerlink" href="#task-policies" title="Permalink to this headline">¶</a></h2>
-<p>Here’s an example of enforcing a maximum timeout policy on every task:</p>
+<p>Here's an example of enforcing a maximum timeout policy on every task:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">task_policy</span><span class="p">(</span><span class="n">task</span><span class="p">:</span> <span class="n">TimedOperator</span><span class="p">):</span>
     <span class="k">if</span> <span class="n">task</span><span class="o">.</span><span class="n">task_type</span> <span class="o">==</span> <span class="s1">&#39;HivePartitionSensor&#39;</span><span class="p">:</span>
         <span class="n">task</span><span class="o">.</span><span class="n">queue</span> <span class="o">=</span> <span class="s2">&quot;sensor_queue&quot;</span>
@@ -752,7 +752,7 @@
 
 </pre></div>
 </div>
-<p>You could also implement to protect against common errors, rather than as technical security controls. For example, don’t run tasks without airflow owners:</p>
+<p>You could also implement to protect against common errors, rather than as technical security controls. For example, don't run tasks without airflow owners:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">task_must_have_owners</span><span class="p">(</span><span class="n">task</span><span class="p">:</span> <span class="n">BaseOperator</span><span class="p">):</span>
     <span class="k">if</span> <span class="ow">not</span> <span class="n">task</span><span class="o">.</span><span class="n">owner</span> <span class="ow">or</span> <span class="n">task</span><span class="o">.</span><span class="n">owner</span><span class="o">.</span><span class="n">lower</span><span class="p">()</span> <span class="o">==</span> <span class="n">conf</span><span class="o">.</span><span class="n">get</span><span class="p">(</span><span class="s1">&#39;operators&#39;</span> [...]
         <span class="k">raise</span> <span class="n">AirflowClusterPolicyViolation</span><span class="p">(</span>
@@ -796,7 +796,7 @@
 </div>
 <div class="section" id="task-instance-mutation">
 <h2>Task instance mutation<a class="headerlink" href="#task-instance-mutation" title="Permalink to this headline">¶</a></h2>
-<p>Here’s an example of re-routing tasks that are on their second (or greater) retry to a different queue:</p>
+<p>Here's an example of re-routing tasks that are on their second (or greater) retry to a different queue:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">task_instance_mutation_hook</span><span class="p">(</span><span class="n">task_instance</span><span class="p">:</span> <span class="n">TaskInstance</span><span class="p">):</span>
     <span class="k">if</span> <span class="n">task_instance</span><span class="o">.</span><span class="n">try_number</span> <span class="o">&gt;=</span> <span class="mi">1</span><span class="p">:</span>
         <span class="n">task_instance</span><span class="o">.</span><span class="n">queue</span> <span class="o">=</span> <span class="s1">&#39;retry_queue&#39;</span>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/connections.html b/docs-archive/apache-airflow/2.3.0/concepts/connections.html
index 48c056cdd..f61dd27a1 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/connections.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/connections.html
@@ -705,8 +705,8 @@
 </div>
 <div class="section" id="hooks">
 <span id="concepts-hooks"></span><h2>Hooks<a class="headerlink" href="#hooks" title="Permalink to this headline">¶</a></h2>
-<p>A Hook is a high-level interface to an external platform that lets you quickly and easily talk to them without having to write low-level code that hits their API or uses special libraries. They’re also often the building blocks that Operators are built out of.</p>
-<p>They integrate with Connections to gather credentials, and many have a default <code class="docutils literal notranslate"><span class="pre">conn_id</span></code>; for example, the <a class="reference external" href="/docs/apache-airflow-providers-postgres/stable/_api/airflow/providers/postgres/hooks/postgres/index.html#airflow.providers.postgres.hooks.postgres.PostgresHook" title="(in apache-airflow-providers-postgres v4.1.0)"><code class="xref py py-class docutils literal notranslate [...]
+<p>A Hook is a high-level interface to an external platform that lets you quickly and easily talk to them without having to write low-level code that hits their API or uses special libraries. They're also often the building blocks that Operators are built out of.</p>
+<p>They integrate with Connections to gather credentials, and many have a default <code class="docutils literal notranslate"><span class="pre">conn_id</span></code>; for example, the <a class="reference external" href="/docs/apache-airflow-providers-postgres/stable/_api/airflow/providers/postgres/hooks/postgres/index.html#airflow.providers.postgres.hooks.postgres.PostgresHook" title="(in apache-airflow-providers-postgres v4.1.0)"><code class="xref py py-class docutils literal notranslate [...]
 <p>You can view a <a class="reference internal" href="../python-api-ref.html#pythonapi-hooks"><span class="std std-ref">full list of airflow hooks</span></a> in our API documentation.</p>
 </div>
 <div class="section" id="custom-connections">
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/dags.html b/docs-archive/apache-airflow/2.3.0/concepts/dags.html
index c3e0f7b64..6ceffaeec 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/dags.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/dags.html
@@ -751,10 +751,10 @@
 <div class="section" id="dags">
 <span id="concepts-dags"></span><h1>DAGs<a class="headerlink" href="#dags" title="Permalink to this headline">¶</a></h1>
 <p>A <em>DAG</em> (Directed Acyclic Graph) is the core concept of Airflow, collecting <a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> together, organized with dependencies and relationships to say how they should run.</p>
-<p>Here’s a basic example DAG:</p>
+<p>Here's a basic example DAG:</p>
 <img alt="../_images/basic-dag.png" src="../_images/basic-dag.png" />
-<p>It defines four Tasks - A, B, C, and D - and dictates the order in which they have to run, and which tasks depend on what others. It will also say how often to run the DAG - maybe “every 5 minutes starting tomorrow”, or “every day since January 1st, 2020”.</p>
-<p>The DAG itself doesn’t care about <em>what</em> is happening inside the tasks; it is merely concerned with <em>how</em> to execute them - the order to run them in, how many times to retry them, if they have timeouts, and so on.</p>
+<p>It defines four Tasks - A, B, C, and D - and dictates the order in which they have to run, and which tasks depend on what others. It will also say how often to run the DAG - maybe &quot;every 5 minutes starting tomorrow&quot;, or &quot;every day since January 1st, 2020&quot;.</p>
+<p>The DAG itself doesn't care about <em>what</em> is happening inside the tasks; it is merely concerned with <em>how</em> to execute them - the order to run them in, how many times to retry them, if they have timeouts, and so on.</p>
 <div class="section" id="declaring-a-dag">
 <h2>Declaring a DAG<a class="headerlink" href="#declaring-a-dag" title="Permalink to this headline">¶</a></h2>
 <p>There are three ways to declare a DAG - either you can use a context manager,
@@ -796,7 +796,7 @@ operators you use:</p>
 <span class="n">third_task</span><span class="o">.</span><span class="n">set_upstream</span><span class="p">(</span><span class="n">fourth_task</span><span class="p">)</span>
 </pre></div>
 </div>
-<p>There are also shortcuts to declaring more complex dependencies. If you want to make two lists of tasks depend on all parts of each other, you can’t use either of the approaches above, so you need to use <code class="docutils literal notranslate"><span class="pre">cross_downstream</span></code>:</p>
+<p>There are also shortcuts to declaring more complex dependencies. If you want to make two lists of tasks depend on all parts of each other, you can't use either of the approaches above, so you need to use <code class="docutils literal notranslate"><span class="pre">cross_downstream</span></code>:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">airflow.models.baseoperator</span> <span class="kn">import</span> <span class="n">cross_downstream</span>
 
 <span class="c1"># Replaces</span>
@@ -845,7 +845,7 @@ operators you use:</p>
 <p>When searching for DAGs inside the <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code>, Airflow only considers Python files that contain the strings <code class="docutils literal notranslate"><span class="pre">airflow</span></code> and <code class="docutils literal notranslate"><span class="pre">dag</span></code> (case-insensitively) as an optimization.</p>
 <p>To consider all Python files instead, disable the <code class="docutils literal notranslate"><span class="pre">DAG_DISCOVERY_SAFE_MODE</span></code> configuration flag.</p>
 </div>
-<p>You can also provide an <code class="docutils literal notranslate"><span class="pre">.airflowignore</span></code> file inside your <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code>, or any of its subfolders, which describes patterns of files for the loader to ignore. It covers the directory it’s in plus all subfolders underneath it. See  <a class="reference internal" href="#concepts-airflowignore"><span class="std std-ref">.airflowignore</span></a>  [...]
+<p>You can also provide an <code class="docutils literal notranslate"><span class="pre">.airflowignore</span></code> file inside your <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code>, or any of its subfolders, which describes patterns of files for the loader to ignore. It covers the directory it's in plus all subfolders underneath it. See  <a class="reference internal" href="#concepts-airflowignore"><span class="std std-ref">.airflowignore</span></a>  [...]
 </div>
 <div class="section" id="running-dags">
 <span id="concepts-dag-run"></span><h2>Running DAGs<a class="headerlink" href="#running-dags" title="Permalink to this headline">¶</a></h2>
@@ -856,7 +856,7 @@ operators you use:</p>
 <li><p>On a defined <em>schedule</em>, which is defined as part of the DAG</p></li>
 </ul>
 </div></blockquote>
-<p>DAGs do not <em>require</em> a schedule, but it’s very common to define one. You define it via the <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> argument, like this:</p>
+<p>DAGs do not <em>require</em> a schedule, but it's very common to define one. You define it via the <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> argument, like this:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="k">with</span> <span class="n">DAG</span><span class="p">(</span><span class="s2">&quot;my_daily_dag&quot;</span><span class="p">,</span> <span class="n">schedule_interval</span><span class="o">=</span><span class="s2">&quot;@daily&quot;</span><span class="p">):</span>
     <span class="o">...</span>
 </pre></div>
@@ -869,7 +869,7 @@ operators you use:</p>
 <div class="admonition tip">
 <p class="admonition-title">Tip</p>
 <p>For more information on <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> values, see <a class="reference internal" href="../dag-run.html"><span class="doc">DAG Run</span></a>.</p>
-<p>If <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> is not enough to express the DAG’s schedule, see <a class="reference internal" href="../howto/timetable.html"><span class="doc">Timetables</span></a>.
+<p>If <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> is not enough to express the DAG's schedule, see <a class="reference internal" href="../howto/timetable.html"><span class="doc">Timetables</span></a>.
 For more information on <code class="docutils literal notranslate"><span class="pre">logical</span> <span class="pre">date</span></code>, see <a class="reference internal" href="../dag-run.html#data-interval"><span class="std std-ref">Data Interval</span></a> and
 <a class="reference internal" href="../faq.html#faq-what-does-execution-date-mean"><span class="std std-ref">What does execution_date mean?</span></a>.</p>
 </div>
@@ -878,28 +878,28 @@ Airflow calls a <a class="reference internal" href="../dag-run.html"><span class
 same DAG, and each has a defined data interval, which identifies the period of
 data the tasks should operate on.</p>
 <p>As an example of why this is useful, consider writing a DAG that processes a
-daily set of experimental data. It’s been rewritten, and you want to run it on
-the previous 3 months of data—no problem, since Airflow can <em>backfill</em> the DAG
+daily set of experimental data. It's been rewritten, and you want to run it on
+the previous 3 months of data---no problem, since Airflow can <em>backfill</em> the DAG
 and run copies of it for every day in those previous 3 months, all at once.</p>
 <p>Those DAG Runs will all have been started on the same actual day, but each DAG
 run will have one data interval covering a single day in that 3 month period,
 and that data interval is all the tasks, operators and sensors inside the DAG
 look at when they run.</p>
-<p>In much the same way a DAG instantiates into a DAG Run every time it’s run,
+<p>In much the same way a DAG instantiates into a DAG Run every time it's run,
 Tasks specified inside a DAG are also instantiated into
 <a class="reference internal" href="tasks.html#concepts-task-instances"><span class="std std-ref">Task Instances</span></a> along with it.</p>
 <p>A DAG run will have a start date when it starts, and end date when it ends.
-This period describes the time when the DAG actually ‘ran.’ Aside from the DAG
-run’s start and end date, there is another date called <em>logical date</em>
+This period describes the time when the DAG actually 'ran.' Aside from the DAG
+run's start and end date, there is another date called <em>logical date</em>
 (formally known as execution date), which describes the intended time a
 DAG run is scheduled or triggered. The reason why this is called
 <em>logical</em> is because of the abstract nature of it having multiple meanings,
 depending on the context of the DAG run itself.</p>
 <p>For example, if a DAG run is manually triggered by the user, its logical date would be the
 date and time of which the DAG run was triggered, and the value should be equal
-to DAG run’s start date. However, when the DAG is being automatically scheduled, with certain
+to DAG run's start date. However, when the DAG is being automatically scheduled, with certain
 schedule interval put in place, the logical date is going to indicate the time
-at which it marks the start of the data interval, where the DAG run’s start
+at which it marks the start of the data interval, where the DAG run's start
 date would then be the logical date + scheduled interval.</p>
 </div>
 <div class="section" id="dag-assignment">
@@ -1044,10 +1044,10 @@ date would then be the logical date + scheduled interval.</p>
 </div>
 <div class="section" id="latest-only">
 <span id="concepts-latest-only"></span><h3>Latest Only<a class="headerlink" href="#latest-only" title="Permalink to this headline">¶</a></h3>
-<p>Airflow’s DAG Runs are often run for a date that is not the same as the current date - for example, running one copy of a DAG for every day in the last month to backfill some data.</p>
-<p>There are situations, though, where you <em>don’t</em> want to let some (or all) parts of a DAG run for a previous date; in this case, you can use the <code class="docutils literal notranslate"><span class="pre">LatestOnlyOperator</span></code>.</p>
-<p>This special Operator skips all tasks downstream of itself if you are not on the “latest” DAG run (if the wall-clock time right now is between its execution_time and the next scheduled execution_time, and it was not an externally-triggered run).</p>
-<p>Here’s an example:</p>
+<p>Airflow's DAG Runs are often run for a date that is not the same as the current date - for example, running one copy of a DAG for every day in the last month to backfill some data.</p>
+<p>There are situations, though, where you <em>don't</em> want to let some (or all) parts of a DAG run for a previous date; in this case, you can use the <code class="docutils literal notranslate"><span class="pre">LatestOnlyOperator</span></code>.</p>
+<p>This special Operator skips all tasks downstream of itself if you are not on the &quot;latest&quot; DAG run (if the wall-clock time right now is between its execution_time and the next scheduled execution_time, and it was not an externally-triggered run).</p>
+<p>Here's an example:</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/example_latest_only_with_trigger.py</span><a class="example-header-button viewcode-button reference internal" href="../_modules/airflow/example_dags/example_latest_only_with_trigger.html"><span class="viewcode-link">[source]</span></a></p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">import</span> <span class="nn">datetime</span>
@@ -1089,7 +1089,7 @@ date would then be the logical date + scheduled interval.</p>
 <div class="section" id="depends-on-past">
 <span id="concepts-depends-on-past"></span><h3>Depends On Past<a class="headerlink" href="#depends-on-past" title="Permalink to this headline">¶</a></h3>
 <p>You can also say a task can only run if the <em>previous</em> run of the task in the previous DAG Run succeeded. To use this, you just need to set the <code class="docutils literal notranslate"><span class="pre">depends_on_past</span></code> argument on your Task to <code class="docutils literal notranslate"><span class="pre">True</span></code>.</p>
-<p>Note that if you are running the DAG at the very start of its life—specifically, its first ever <em>automated</em> run—then the Task will still run, as there is no previous run to depend on.</p>
+<p>Note that if you are running the DAG at the very start of its life---specifically, its first ever <em>automated</em> run---then the Task will still run, as there is no previous run to depend on.</p>
 </div>
 <div class="section" id="trigger-rules">
 <span id="concepts-trigger-rules"></span><h3>Trigger Rules<a class="headerlink" href="#trigger-rules" title="Permalink to this headline">¶</a></h3>
@@ -1110,7 +1110,7 @@ date would then be the logical date + scheduled interval.</p>
 <p>You can also combine this with the <a class="reference internal" href="#concepts-depends-on-past"><span class="std std-ref">Depends On Past</span></a> functionality if you wish.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>It’s important to be aware of the interaction between trigger rules and skipped tasks, especially tasks that are skipped as part of a branching operation. <em>You almost never want to use all_success or all_failed downstream of a branching operation</em>.</p>
+<p>It's important to be aware of the interaction between trigger rules and skipped tasks, especially tasks that are skipped as part of a branching operation. <em>You almost never want to use all_success or all_failed downstream of a branching operation</em>.</p>
 <p>Skipped tasks will cascade through trigger rules <code class="docutils literal notranslate"><span class="pre">all_success</span></code> and <code class="docutils literal notranslate"><span class="pre">all_failed</span></code>, and cause them to skip as well. Consider the following DAG:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="c1"># dags/branch_without_trigger.py</span>
 <span class="kn">import</span> <span class="nn">pendulum</span>
@@ -1170,7 +1170,7 @@ date would then be the logical date + scheduled interval.</p>
 <h2>DAG Visualization<a class="headerlink" href="#dag-visualization" title="Permalink to this headline">¶</a></h2>
 <p>If you want to see a visual representation of a DAG, you have two options:</p>
 <ul class="simple">
-<li><p>You can load up the Airflow UI, navigate to your DAG, and select “Graph”</p></li>
+<li><p>You can load up the Airflow UI, navigate to your DAG, and select &quot;Graph&quot;</p></li>
 <li><p>You can run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">show</span></code>, which renders it out as an image file</p></li>
 </ul>
 <p>We generally recommend you use the Graph view, as it will also show you the state of all the <a class="reference internal" href="tasks.html#concepts-task-instances"><span class="std std-ref">Task Instances</span></a> within any DAG Run you select.</p>
@@ -1229,7 +1229,7 @@ date would then be the logical date + scheduled interval.</p>
 <span class="n">my_task</span><span class="o">.</span><span class="n">set_downstream</span><span class="p">(</span><span class="n">other_task</span><span class="p">,</span> <span class="n">Label</span><span class="p">(</span><span class="s2">&quot;When empty&quot;</span><span class="p">))</span>
 </pre></div>
 </div>
-<p>Here’s an example DAG which illustrates labeling different branches:</p>
+<p>Here's an example DAG which illustrates labeling different branches:</p>
 <img alt="../_images/edge_label_example.png" src="../_images/edge_label_example.png" />
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/example_branch_labels.py</span><a class="example-header-button viewcode-button reference internal" href="../_modules/airflow/example_dags/example_branch_labels.html"><span class="viewcode-link">[source]</span></a></p>
@@ -1258,7 +1258,7 @@ date would then be the logical date + scheduled interval.</p>
 </div>
 <div class="section" id="dag-task-documentation">
 <h2>DAG &amp; Task Documentation<a class="headerlink" href="#dag-task-documentation" title="Permalink to this headline">¶</a></h2>
-<p>It’s possible to add documentation or notes to your DAGs &amp; task objects that are visible in the web interface (“Graph” &amp; “Tree” for DAGs, “Task Instance Details” for tasks).</p>
+<p>It's possible to add documentation or notes to your DAGs &amp; task objects that are visible in the web interface (&quot;Graph&quot; &amp; &quot;Tree&quot; for DAGs, &quot;Task Instance Details&quot; for tasks).</p>
 <p>There are a set of special task attributes that get rendered as rich content if defined:</p>
 <table class="docutils align-default">
 <colgroup>
@@ -1314,7 +1314,7 @@ date would then be the logical date + scheduled interval.</p>
 <div class="section" id="subdags">
 <span id="concepts-subdags"></span><h2>SubDAGs<a class="headerlink" href="#subdags" title="Permalink to this headline">¶</a></h2>
 <p>Sometimes, you will find that you are regularly adding exactly the same set of tasks to every DAG, or you want to group a lot of tasks into a single, logical unit. This is what SubDAGs are for.</p>
-<p>For example, here’s a DAG that has a lot of parallel tasks in two sections:</p>
+<p>For example, here's a DAG that has a lot of parallel tasks in two sections:</p>
 <img alt="../_images/subdag_before.png" src="../_images/subdag_before.png" />
 <p>We can combine all of the parallel <code class="docutils literal notranslate"><span class="pre">task-*</span></code> operators into a single SubDAG, so that the resulting DAG resembles the following:</p>
 <img alt="../_images/subdag_after.png" src="../_images/subdag_after.png" />
@@ -1407,9 +1407,9 @@ date would then be the logical date + scheduled interval.</p>
 <img alt="../_images/subdag_zoom.png" src="../_images/subdag_zoom.png" />
 <p>Some other tips when using SubDAGs:</p>
 <ul class="simple">
-<li><p>By convention, a SubDAG’s <code class="docutils literal notranslate"><span class="pre">dag_id</span></code> should be prefixed by the name of its parent DAG and a dot (<code class="docutils literal notranslate"><span class="pre">parent.child</span></code>)</p></li>
+<li><p>By convention, a SubDAG's <code class="docutils literal notranslate"><span class="pre">dag_id</span></code> should be prefixed by the name of its parent DAG and a dot (<code class="docutils literal notranslate"><span class="pre">parent.child</span></code>)</p></li>
 <li><p>You should share arguments between the main DAG and the SubDAG by passing arguments to the SubDAG operator (as demonstrated above)</p></li>
-<li><p>SubDAGs must have a schedule and be enabled. If the SubDAG’s schedule is set to <code class="docutils literal notranslate"><span class="pre">None</span></code> or <code class="docutils literal notranslate"><span class="pre">&#64;once</span></code>, the SubDAG will succeed without having done anything.</p></li>
+<li><p>SubDAGs must have a schedule and be enabled. If the SubDAG's schedule is set to <code class="docutils literal notranslate"><span class="pre">None</span></code> or <code class="docutils literal notranslate"><span class="pre">&#64;once</span></code>, the SubDAG will succeed without having done anything.</p></li>
 <li><p>Clearing a <a class="reference internal" href="../_api/airflow/operators/subdag/index.html#airflow.operators.subdag.SubDagOperator" title="airflow.operators.subdag.SubDagOperator"><code class="xref py py-class docutils literal notranslate"><span class="pre">SubDagOperator</span></code></a> also clears the state of the tasks within it.</p></li>
 <li><p>Marking success on a <a class="reference internal" href="../_api/airflow/operators/subdag/index.html#airflow.operators.subdag.SubDagOperator" title="airflow.operators.subdag.SubDagOperator"><code class="xref py py-class docutils literal notranslate"><span class="pre">SubDagOperator</span></code></a> does not affect the state of the tasks within it.</p></li>
 <li><p>Refrain from using <a class="reference internal" href="#concepts-depends-on-past"><span class="std std-ref">Depends On Past</span></a> in tasks within the SubDAG as this can be confusing.</p></li>
@@ -1427,7 +1427,7 @@ date would then be the logical date + scheduled interval.</p>
 <ul class="simple">
 <li><p>The SubDagOperator starts a BackfillJob, which ignores existing parallelism configurations potentially oversubscribing the worker environment.</p></li>
 <li><p>SubDAGs have their own DAG attributes. When the SubDAG DAG attributes are inconsistent with its parent DAG, unexpected behavior can occur.</p></li>
-<li><p>Unable to see the “full” DAG in one view as SubDAGs exists as a full fledged DAG.</p></li>
+<li><p>Unable to see the &quot;full&quot; DAG in one view as SubDAGs exists as a full fledged DAG.</p></li>
 <li><p>SubDAGs introduces all sorts of edge cases and caveats. This can disrupt user experience and expectation.</p></li>
 </ul>
 <p>TaskGroups, on the other hand, is a better option given that it is purely a UI grouping concept. All tasks within the TaskGroup still behave as any other tasks outside of the TaskGroup.</p>
@@ -1470,7 +1470,7 @@ newly spawned BackfillJob</p></td>
 </div>
 <div class="section" id="packaging-dags">
 <h2>Packaging DAGs<a class="headerlink" href="#packaging-dags" title="Permalink to this headline">¶</a></h2>
-<p>While simpler DAGs are usually only in a single Python file, it is not uncommon that more complex DAGs might be spread across multiple files and have dependencies that should be shipped with them (“vendored”).</p>
+<p>While simpler DAGs are usually only in a single Python file, it is not uncommon that more complex DAGs might be spread across multiple files and have dependencies that should be shipped with them (&quot;vendored&quot;).</p>
 <p>You can either do this all inside of the <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code>, with a standard filesystem layout, or you can package the DAG and all of its Python files up as a single zip file. For instance, you could ship two dags along with a dependency they need as a zip file with the following contents:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">my_dag1</span><span class="o">.</span><span class="n">py</span>
 <span class="n">my_dag2</span><span class="o">.</span><span class="n">py</span>
@@ -1482,7 +1482,7 @@ newly spawned BackfillJob</p></td>
 <ul class="simple">
 <li><p>They cannot be used if you have picking enabled for serialization</p></li>
 <li><p>They cannot contain compiled libraries (e.g. <code class="docutils literal notranslate"><span class="pre">libz.so</span></code>), only pure Python</p></li>
-<li><p>They will be inserted into Python’s <code class="docutils literal notranslate"><span class="pre">sys.path</span></code> and importable by any other code in the Airflow process, so ensure the package names don’t clash with other packages already installed on your system.</p></li>
+<li><p>They will be inserted into Python's <code class="docutils literal notranslate"><span class="pre">sys.path</span></code> and importable by any other code in the Airflow process, so ensure the package names don't clash with other packages already installed on your system.</p></li>
 </ul>
 <p>In general, if you have a complex set of compiled dependencies and modules, you are likely better off using the Python <code class="docutils literal notranslate"><span class="pre">virtualenv</span></code> system and installing the necessary packages on your target systems with <code class="docutils literal notranslate"><span class="pre">pip</span></code>.</p>
 </div>
@@ -1528,7 +1528,7 @@ a <code class="docutils literal notranslate"><span class="pre">.airflowignore</s
 </div>
 <p>Then files like <code class="docutils literal notranslate"><span class="pre">project_a_dag_1.py</span></code>, <code class="docutils literal notranslate"><span class="pre">TESTING_project_a.py</span></code>, <code class="docutils literal notranslate"><span class="pre">tenant_1.py</span></code>,
 <code class="docutils literal notranslate"><span class="pre">project_a/dag_1.py</span></code>, and <code class="docutils literal notranslate"><span class="pre">tenant_1/dag_1.py</span></code> in your <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code> would be ignored
-(If a directory’s name matches any of the patterns, this directory and all its subfolders
+(If a directory's name matches any of the patterns, this directory and all its subfolders
 would not be scanned by Airflow at all. This improves efficiency of DAG finding).</p>
 <p>The scope of a <code class="docutils literal notranslate"><span class="pre">.airflowignore</span></code> file is the directory it is in plus all its subfolders.
 You can also prepare <code class="docutils literal notranslate"><span class="pre">.airflowignore</span></code> file for a subfolder in <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code> and it
@@ -1554,10 +1554,10 @@ the dependency graph.</p>
 </div>
 <div class="section" id="dag-pausing-deactivation-and-deletion">
 <h2>DAG pausing, deactivation and deletion<a class="headerlink" href="#dag-pausing-deactivation-and-deletion" title="Permalink to this headline">¶</a></h2>
-<p>The DAGs have several states when it comes to being “not running”. DAGs can be paused, deactivated
+<p>The DAGs have several states when it comes to being &quot;not running&quot;. DAGs can be paused, deactivated
 and finally all metadata for the DAG can be deleted.</p>
 <p>Dag can be paused via UI when it is present in the <code class="docutils literal notranslate"><span class="pre">DAGS_FOLDER</span></code>, and scheduler stored it in
-the database, but the user chose to disable it via the UI. The “pause” and “unpause” actions are available
+the database, but the user chose to disable it via the UI. The &quot;pause&quot; and &quot;unpause&quot; actions are available
 via UI and API. Paused DAG is not scheduled by the Scheduler, but you can trigger them via UI for
 manual runs. In the UI, you can see Paused DAGs (in <code class="docutils literal notranslate"><span class="pre">Paused</span></code> tab). The DAGs that are un-paused
 can be found in the <code class="docutils literal notranslate"><span class="pre">Active</span></code> tab.</p>
@@ -1570,7 +1570,7 @@ can only be done by removing files from the <code class="docutils literal notran
 DAG are lost when it is deactivated by the scheduler. Note that the <code class="docutils literal notranslate"><span class="pre">Active</span></code> tab in Airflow UI
 refers to DAGs that are not both <code class="docutils literal notranslate"><span class="pre">Activated</span></code> and <code class="docutils literal notranslate"><span class="pre">Not</span> <span class="pre">paused</span></code> so this might initially be a
 little confusing.</p>
-<p>You can’t see the deactivated DAGs in the UI - you can sometimes see the historical runs, but when you try to
+<p>You can't see the deactivated DAGs in the UI - you can sometimes see the historical runs, but when you try to
 see the information about those you will see the error that the DAG is missing.</p>
 <p>You can also delete the DAG metadata from the metadata database using UI or API, but it does not
 always result in disappearing of the DAG from the UI - which might be also initially a bit confusing.
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/deferring.html b/docs-archive/apache-airflow/2.3.0/concepts/deferring.html
index b901cc2be..87ca68150 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/deferring.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/deferring.html
@@ -708,7 +708,7 @@
 <div></div></blockquote>
 <div class="section" id="deferrable-operators-triggers">
 <h1>Deferrable Operators &amp; Triggers<a class="headerlink" href="#deferrable-operators-triggers" title="Permalink to this headline">¶</a></h1>
-<p>Standard <a class="reference internal" href="operators.html"><span class="doc">Operators</span></a> and <a class="reference internal" href="sensors.html"><span class="doc">Sensors</span></a> take up a full <em>worker slot</em> for the entire time they are running, even if they are idle; for example, if you only have 100 worker slots available to run Tasks, and you have 100 DAGs waiting on a Sensor that’s currently running but idle, then you <em>cannot run anything else</em> - even tho [...]
+<p>Standard <a class="reference internal" href="operators.html"><span class="doc">Operators</span></a> and <a class="reference internal" href="sensors.html"><span class="doc">Sensors</span></a> take up a full <em>worker slot</em> for the entire time they are running, even if they are idle; for example, if you only have 100 worker slots available to run Tasks, and you have 100 DAGs waiting on a Sensor that's currently running but idle, then you <em>cannot run anything else</em> - even tho [...]
 <p>This is where <em>Deferrable Operators</em> come in. A deferrable operator is one that is written with the ability to suspend itself and free up the worker when it knows it has to wait, and hand off the job of resuming it to something called a <em>Trigger</em>. As a result, while it is suspended (deferred), it is not taking up a worker slot and your cluster will have a lot less resources wasted on idle Operators or Sensors.</p>
 <p><em>Triggers</em> are small, asynchronous pieces of Python code designed to be run all together in a single Python process; because they are asynchronous, they are able to all co-exist efficiently. As an overview of how this process works:</p>
 <ul class="simple">
@@ -730,7 +730,7 @@ on Python 3.7 or higher.</p>
 <li><p>Ensure your Airflow installation is running at least one <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> process, as well as the normal <code class="docutils literal notranslate"><span class="pre">scheduler</span></code></p></li>
 <li><p>Use deferrable operators/sensors in your DAGs</p></li>
 </ul>
-<p>That’s it; everything else will be automatically handled for you. If you’re upgrading existing DAGs, we even provide some API-compatible sensor variants (e.g. <code class="docutils literal notranslate"><span class="pre">TimeSensorAsync</span></code> for <code class="docutils literal notranslate"><span class="pre">TimeSensor</span></code>) that you can swap into your DAG with no other changes required.</p>
+<p>That's it; everything else will be automatically handled for you. If you're upgrading existing DAGs, we even provide some API-compatible sensor variants (e.g. <code class="docutils literal notranslate"><span class="pre">TimeSensorAsync</span></code> for <code class="docutils literal notranslate"><span class="pre">TimeSensor</span></code>) that you can swap into your DAG with no other changes required.</p>
 <p>Note that you cannot yet use the deferral ability from inside custom PythonOperator/TaskFlow Python functions; it is only available to traditional, class-based Operators at the moment.</p>
 </div>
 <div class="section" id="writing-deferrable-operators">
@@ -738,9 +738,9 @@ on Python 3.7 or higher.</p>
 <p>Writing a deferrable operator takes a bit more work. There are some main points to consider:</p>
 <ul class="simple">
 <li><p>Your Operator must defer itself with a Trigger. If there is a Trigger in core Airflow you can use, great; otherwise, you will have to write one.</p></li>
-<li><p>Your Operator will be stopped and removed from its worker while deferred, and no state will persist automatically. You can persist state by asking Airflow to resume you at a certain method or pass certain kwargs, but that’s it.</p></li>
+<li><p>Your Operator will be stopped and removed from its worker while deferred, and no state will persist automatically. You can persist state by asking Airflow to resume you at a certain method or pass certain kwargs, but that's it.</p></li>
 <li><p>You can defer multiple times, and you can defer before/after your Operator does significant work, or only defer if certain conditions are met (e.g. a system does not have an immediate answer). Deferral is entirely under your control.</p></li>
-<li><p>Any Operator can defer; no special marking on its class is needed, and it’s not limited to Sensors.</p></li>
+<li><p>Any Operator can defer; no special marking on its class is needed, and it's not limited to Sensors.</p></li>
 </ul>
 <div class="section" id="triggering-deferral">
 <h3>Triggering Deferral<a class="headerlink" href="#triggering-deferral" title="Permalink to this headline">¶</a></h3>
@@ -752,10 +752,10 @@ on Python 3.7 or higher.</p>
 <li><p><code class="docutils literal notranslate"><span class="pre">timeout</span></code>: A timedelta that specifies a timeout after which this deferral will fail, and fail the task instance. Optional, defaults to <code class="docutils literal notranslate"><span class="pre">None</span></code>, meaning no timeout.</p></li>
 </ul>
 <p>When you opt to defer, your Operator will <em>stop executing at that point and be removed from its current worker</em>. No state - such as local variables, or attributes set on <code class="docutils literal notranslate"><span class="pre">self</span></code> - will persist, and when your Operator is resumed it will be a <em>brand new instance</em> of it. The only way you can pass state from the old instance of the Operator to the new one is via <code class="docutils literal notranslate" [...]
-<p>When your Operator is resumed, an <code class="docutils literal notranslate"><span class="pre">event</span></code> item will be added to the kwargs passed to the <code class="docutils literal notranslate"><span class="pre">method_name</span></code> method. The <code class="docutils literal notranslate"><span class="pre">event</span></code> object contains the payload from the trigger event that resumed your Operator. Depending on the trigger, this may be useful to your operator (e.g.  [...]
-<p>If your Operator returns from either its first <code class="docutils literal notranslate"><span class="pre">execute()</span></code> method when it’s new, or a subsequent method specified by <code class="docutils literal notranslate"><span class="pre">method_name</span></code>, it will be considered complete and will finish executing.</p>
+<p>When your Operator is resumed, an <code class="docutils literal notranslate"><span class="pre">event</span></code> item will be added to the kwargs passed to the <code class="docutils literal notranslate"><span class="pre">method_name</span></code> method. The <code class="docutils literal notranslate"><span class="pre">event</span></code> object contains the payload from the trigger event that resumed your Operator. Depending on the trigger, this may be useful to your operator (e.g.  [...]
+<p>If your Operator returns from either its first <code class="docutils literal notranslate"><span class="pre">execute()</span></code> method when it's new, or a subsequent method specified by <code class="docutils literal notranslate"><span class="pre">method_name</span></code>, it will be considered complete and will finish executing.</p>
 <p>You are free to set <code class="docutils literal notranslate"><span class="pre">method_name</span></code> to <code class="docutils literal notranslate"><span class="pre">execute</span></code> if you want your Operator to have one entrypoint, but it, too, will have to accept <code class="docutils literal notranslate"><span class="pre">event</span></code> as an optional keyword argument.</p>
-<p>Here’s a basic example of how a sensor might trigger deferral:</p>
+<p>Here's a basic example of how a sensor might trigger deferral:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">WaitOneHourSensor</span><span class="p">(</span><span class="n">BaseSensorOperator</span><span class="p">):</span>
     <span class="k">def</span> <span class="nf">execute</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">context</span><span class="p">):</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">defer</span><span class="p">(</span><span class="n">trigger</span><span class="o">=</span><span class="n">TimeDeltaTrigger</span><span class="p">(</span><span class="n">timedelta</span><span class="p">(</span><span class="n">hours</span><span class="o">=</span><span class="mi">1</span><span class="p">)),</span> <span class="n">method_name</span><span class="o">=</span><span class="s2">&quot;execute_complete&quot; [...]
@@ -766,8 +766,8 @@ on Python 3.7 or higher.</p>
 </pre></div>
 </div>
 <p>This Sensor is literally just a thin wrapper around the Trigger, so all it does is defer to the trigger, and specify a different method to come back to when the trigger fires - which, as it returns immediately, marks the Sensor as successful.</p>
-<p>Under the hood, <code class="docutils literal notranslate"><span class="pre">self.defer</span></code> raises the <code class="docutils literal notranslate"><span class="pre">TaskDeferred</span></code> exception, so it will work anywhere inside your Operator’s code, even buried many nested calls deep inside <code class="docutils literal notranslate"><span class="pre">execute()</span></code>. You are free to raise <code class="docutils literal notranslate"><span class="pre">TaskDeferred [...]
-<p>Note that <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code> on Operators is considered over the <em>total runtime</em>, not individual executions in-between deferrals - this means that if <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code> is set, an Operator may fail while it’s deferred or while it’s running after a deferral, even if it’s only been resumed for a few seconds.</p>
+<p>Under the hood, <code class="docutils literal notranslate"><span class="pre">self.defer</span></code> raises the <code class="docutils literal notranslate"><span class="pre">TaskDeferred</span></code> exception, so it will work anywhere inside your Operator's code, even buried many nested calls deep inside <code class="docutils literal notranslate"><span class="pre">execute()</span></code>. You are free to raise <code class="docutils literal notranslate"><span class="pre">TaskDeferred [...]
+<p>Note that <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code> on Operators is considered over the <em>total runtime</em>, not individual executions in-between deferrals - this means that if <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code> is set, an Operator may fail while it's deferred or while it's running after a deferral, even if it's only been resumed for a few seconds.</p>
 </div>
 <div class="section" id="writing-triggers">
 <h3>Writing Triggers<a class="headerlink" href="#writing-triggers" title="Permalink to this headline">¶</a></h3>
@@ -777,19 +777,19 @@ on Python 3.7 or higher.</p>
 <li><p><code class="docutils literal notranslate"><span class="pre">run</span></code>, an asynchronous method that runs its logic and yields one or more <code class="docutils literal notranslate"><span class="pre">TriggerEvent</span></code> instances as an asynchronous generator</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">serialize</span></code>, which returns the information needed to re-construct this trigger, as a tuple of the classpath, and keyword arguments to pass to <code class="docutils literal notranslate"><span class="pre">__init__</span></code></p></li>
 </ul>
-<p>There’s also some design constraints to be aware of:</p>
+<p>There's also some design constraints to be aware of:</p>
 <ul class="simple">
-<li><p>The <code class="docutils literal notranslate"><span class="pre">run</span></code> method <em>must be asynchronous</em> (using Python’s asyncio), and correctly <code class="docutils literal notranslate"><span class="pre">await</span></code> whenever it does a blocking operation.</p></li>
+<li><p>The <code class="docutils literal notranslate"><span class="pre">run</span></code> method <em>must be asynchronous</em> (using Python's asyncio), and correctly <code class="docutils literal notranslate"><span class="pre">await</span></code> whenever it does a blocking operation.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">run</span></code> must <code class="docutils literal notranslate"><span class="pre">yield</span></code> its TriggerEvents, not return them. If it returns before yielding at least one event, Airflow will consider this an error and fail any Task Instances waiting on it. If it throws an exception, Airflow will also fail any dependent task instances.</p></li>
 <li><p>You should assume that a trigger instance may run <em>more than once</em> (this can happen if a network partition occurs and Airflow re-launches a trigger on a separated machine). So you must be mindful about side effects. For example you might not want to use a trigger to insert database rows.</p></li>
-<li><p>If your trigger is designed to emit more than one event (not currently supported), then each emitted event <em>must</em> contain a payload that can be used to deduplicate events if the trigger is being run in multiple places. If you only fire one event and don’t need to pass information back to the Operator, you can just set the payload to <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p></li>
+<li><p>If your trigger is designed to emit more than one event (not currently supported), then each emitted event <em>must</em> contain a payload that can be used to deduplicate events if the trigger is being run in multiple places. If you only fire one event and don't need to pass information back to the Operator, you can just set the payload to <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p></li>
 <li><p>A trigger may be suddenly removed from one triggerer service and started on a new one, for example if subnets are changed and a network partition results, or if there is a deployment. If desired you may implement the <code class="docutils literal notranslate"><span class="pre">cleanup</span></code> method, which is always called after <code class="docutils literal notranslate"><span class="pre">run</span></code> whether the trigger exits cleanly or otherwise.</p></li>
 </ul>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Currently Triggers are only used up to their first event, as they are only used for resuming deferred tasks (which happens on the first event fired). However, we plan to allow DAGs to be launched from triggers in future, which is where multi-event triggers will be more useful.</p>
 </div>
-<p>Here’s the structure of a basic Trigger:</p>
+<p>Here's the structure of a basic Trigger:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">DateTimeTrigger</span><span class="p">(</span><span class="n">BaseTrigger</span><span class="p">):</span>
 
     <span class="k">def</span> <span class="fm">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">moment</span><span class="p">):</span>
@@ -805,22 +805,22 @@ on Python 3.7 or higher.</p>
         <span class="k">yield</span> <span class="n">TriggerEvent</span><span class="p">(</span><span class="bp">self</span><span class="o">.</span><span class="n">moment</span><span class="p">)</span>
 </pre></div>
 </div>
-<p>This is a very simplified version of Airflow’s <code class="docutils literal notranslate"><span class="pre">DateTimeTrigger</span></code>, and you can see several things here:</p>
+<p>This is a very simplified version of Airflow's <code class="docutils literal notranslate"><span class="pre">DateTimeTrigger</span></code>, and you can see several things here:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">__init__</span></code> and <code class="docutils literal notranslate"><span class="pre">serialize</span></code> are written as a pair; the Trigger is instantiated once when it is submitted by the Operator as part of its deferral request, then serialized and re-instantiated on any <em>triggerer</em> process that runs the trigger.</p></li>
 <li><p>The <code class="docutils literal notranslate"><span class="pre">run</span></code> method is declared as an <code class="docutils literal notranslate"><span class="pre">async</span> <span class="pre">def</span></code>, as it <em>must</em> be asynchronous, and uses <code class="docutils literal notranslate"><span class="pre">asyncio.sleep</span></code> rather than the regular <code class="docutils literal notranslate"><span class="pre">time.sleep</span></code> (as that would block  [...]
 <li><p>When it emits its event it packs <code class="docutils literal notranslate"><span class="pre">self.moment</span></code> in there, so if this trigger is being run redundantly on multiple hosts, the event can be de-duplicated.</p></li>
 </ul>
 <p>Triggers can be as complex or as simple as you like provided you keep inside this contract; they are designed to be run in a highly-available fashion, auto-distributed among hosts running the <em>triggerer</em>. We encourage you to avoid any kind of persistent state in a trigger; they should get everything they need from their <code class="docutils literal notranslate"><span class="pre">__init__</span></code>, so they can be serialized and moved around freely.</p>
-<p>If you are new to writing asynchronous Python, you should be very careful writing your <code class="docutils literal notranslate"><span class="pre">run()</span></code> method; Python’s async model means that any code that does not correctly <code class="docutils literal notranslate"><span class="pre">await</span></code> when it does a blocking operation will block the <em>entire process</em>. Airflow will attempt to detect this and warn you in the triggerer logs when it happens, but w [...]
+<p>If you are new to writing asynchronous Python, you should be very careful writing your <code class="docutils literal notranslate"><span class="pre">run()</span></code> method; Python's async model means that any code that does not correctly <code class="docutils literal notranslate"><span class="pre">await</span></code> when it does a blocking operation will block the <em>entire process</em>. Airflow will attempt to detect this and warn you in the triggerer logs when it happens, but w [...]
 </div>
 </div>
 <div class="section" id="high-availability">
 <h2>High Availability<a class="headerlink" href="#high-availability" title="Permalink to this headline">¶</a></h2>
 <p>Triggers are designed from the ground-up to be highly-available; if you want to run a highly-available setup, simply run multiple copies of <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> on multiple hosts. Much like <code class="docutils literal notranslate"><span class="pre">scheduler</span></code>, they will automatically co-exist with correct locking and HA.</p>
 <p>Depending on how much work the triggers are doing, you can fit from hundreds to tens of thousands of triggers on a single <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> host. By default, every <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> will have a capacity of 1000 triggers it will try to run at once; you can change this with the <code class="docutils literal notranslate"><span class="pre">--capacity</span> [...]
-<p>Airflow tries to only run triggers in one place at once, and maintains a heartbeat to all <code class="docutils literal notranslate"><span class="pre">triggerers</span></code> that are currently running. If a <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> dies, or becomes partitioned from the network where Airflow’s database is running, Airflow will automatically re-schedule triggers that were on that host to run elsewhere (after waiting 30 second [...]
-<p>This means it’s possible, but unlikely, for triggers to run in multiple places at once; this is designed into the Trigger contract, however, and entirely expected. Airflow will de-duplicate events fired when a trigger is running in multiple places simultaneously, so this process should be transparent to your Operators.</p>
+<p>Airflow tries to only run triggers in one place at once, and maintains a heartbeat to all <code class="docutils literal notranslate"><span class="pre">triggerers</span></code> that are currently running. If a <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> dies, or becomes partitioned from the network where Airflow's database is running, Airflow will automatically re-schedule triggers that were on that host to run elsewhere (after waiting 30 second [...]
+<p>This means it's possible, but unlikely, for triggers to run in multiple places at once; this is designed into the Trigger contract, however, and entirely expected. Airflow will de-duplicate events fired when a trigger is running in multiple places simultaneously, so this process should be transparent to your Operators.</p>
 <p>Note that every extra <code class="docutils literal notranslate"><span class="pre">triggerer</span></code> you run will result in an extra persistent connection to your database.</p>
 </div>
 <div class="section" id="smart-sensors">
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/dynamic-task-mapping.html b/docs-archive/apache-airflow/2.3.0/concepts/dynamic-task-mapping.html
index ebb803757..10f685f61 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/dynamic-task-mapping.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/dynamic-task-mapping.html
@@ -755,16 +755,16 @@
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Values passed from the mapped task is a lazy proxy</p>
-<p>In the above example, <code class="docutils literal notranslate"><span class="pre">values</span></code> received by <code class="docutils literal notranslate"><span class="pre">sum_it</span></code> is an aggregation of all values returned by each mapped instance of <code class="docutils literal notranslate"><span class="pre">add_one</span></code>. However, since it is impossible to know how many instances of <code class="docutils literal notranslate"><span class="pre">add_one</span></ [...]
+<p>In the above example, <code class="docutils literal notranslate"><span class="pre">values</span></code> received by <code class="docutils literal notranslate"><span class="pre">sum_it</span></code> is an aggregation of all values returned by each mapped instance of <code class="docutils literal notranslate"><span class="pre">add_one</span></code>. However, since it is impossible to know how many instances of <code class="docutils literal notranslate"><span class="pre">add_one</span></ [...]
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">_LazyXComAccess</span><span class="p">(</span><span class="n">dag_id</span><span class="o">=</span><span class="s1">&#39;simple_mapping&#39;</span><span class="p">,</span> <span class="n">run_id</span><span class="o">=</span><span class="s1">&#39;test_run&#39;</span><span class="p">,</span> <span class="n">task_id</span><span class="o">=</span><span class="s1">&#39;add_one&#39;</span><span [...]
 </pre></div>
 </div>
-<p>You can use normal sequence syntax on this object (e.g. <code class="docutils literal notranslate"><span class="pre">values[0]</span></code>), or iterate through it normally with a <code class="docutils literal notranslate"><span class="pre">for</span></code> loop. <code class="docutils literal notranslate"><span class="pre">list(values)</span></code> will give you a “real” <code class="docutils literal notranslate"><span class="pre">list</span></code>, but please be aware of the pote [...]
+<p>You can use normal sequence syntax on this object (e.g. <code class="docutils literal notranslate"><span class="pre">values[0]</span></code>), or iterate through it normally with a <code class="docutils literal notranslate"><span class="pre">for</span></code> loop. <code class="docutils literal notranslate"><span class="pre">list(values)</span></code> will give you a &quot;real&quot; <code class="docutils literal notranslate"><span class="pre">list</span></code>, but please be aware o [...]
 </div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>A reduce task is not required.</p>
-<p>Although we show a “reduce” task here (<code class="docutils literal notranslate"><span class="pre">sum_it</span></code>) you don’t have to have one, the mapped tasks will still be executed even if they have no downstream tasks.</p>
+<p>Although we show a &quot;reduce&quot; task here (<code class="docutils literal notranslate"><span class="pre">sum_it</span></code>) you don't have to have one, the mapped tasks will still be executed even if they have no downstream tasks.</p>
 </div>
 </div>
 <div class="section" id="repeated-mapping">
@@ -784,7 +784,7 @@
 </div>
 <div class="section" id="constant-parameters">
 <h2>Constant parameters<a class="headerlink" href="#constant-parameters" title="Permalink to this headline">¶</a></h2>
-<p>As well as passing arguments that get expanded at run-time, it is possible to pass arguments that don’t change – in order to clearly differentiate between the two kinds we use different functions, <code class="docutils literal notranslate"><span class="pre">expand()</span></code> for mapped arguments, and <code class="docutils literal notranslate"><span class="pre">partial()</span></code> for unmapped ones.</p>
+<p>As well as passing arguments that get expanded at run-time, it is possible to pass arguments that don't change – in order to clearly differentiate between the two kinds we use different functions, <code class="docutils literal notranslate"><span class="pre">expand()</span></code> for mapped arguments, and <code class="docutils literal notranslate"><span class="pre">partial()</span></code> for unmapped ones.</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="nd">@task</span>
 <span class="k">def</span> <span class="nf">add</span><span class="p">(</span><span class="n">x</span><span class="p">:</span> <span class="nb">int</span><span class="p">,</span> <span class="n">y</span><span class="p">:</span> <span class="nb">int</span><span class="p">):</span>
     <span class="k">return</span> <span class="n">x</span> <span class="o">+</span> <span class="n">y</span>
@@ -802,7 +802,7 @@
 </div>
 <div class="section" id="mapping-over-multiple-parameters">
 <h2>Mapping over multiple parameters<a class="headerlink" href="#mapping-over-multiple-parameters" title="Permalink to this headline">¶</a></h2>
-<p>As well as a single parameter it is possible to pass multiple parameters to expand. This will have the effect of creating a “cross product”, calling the mapped task with each combination of parameters.</p>
+<p>As well as a single parameter it is possible to pass multiple parameters to expand. This will have the effect of creating a &quot;cross product&quot;, calling the mapped task with each combination of parameters.</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="nd">@task</span>
 <span class="k">def</span> <span class="nf">add</span><span class="p">(</span><span class="n">x</span><span class="p">:</span> <span class="nb">int</span><span class="p">,</span> <span class="n">y</span><span class="p">:</span> <span class="nb">int</span><span class="p">):</span>
     <span class="k">return</span> <span class="n">x</span> <span class="o">+</span> <span class="n">y</span>
@@ -819,11 +819,11 @@
 </pre></div>
 </div>
 <p>This would result in the add task being called 6 times. Please note however that the order of expansion is not guaranteed.</p>
-<p>It is not possible to achieve an effect similar to Python’s <code class="docutils literal notranslate"><span class="pre">zip</span></code> function with mapped arguments.</p>
+<p>It is not possible to achieve an effect similar to Python's <code class="docutils literal notranslate"><span class="pre">zip</span></code> function with mapped arguments.</p>
 </div>
 <div class="section" id="task-generated-mapping">
 <h2>Task-generated Mapping<a class="headerlink" href="#task-generated-mapping" title="Permalink to this headline">¶</a></h2>
-<p>Up until now the examples we’ve shown could all be achieved with a <code class="docutils literal notranslate"><span class="pre">for</span></code> loop in the DAG file, but the real power of dynamic task mapping comes from being able to have a task generate the list to iterate over.</p>
+<p>Up until now the examples we've shown could all be achieved with a <code class="docutils literal notranslate"><span class="pre">for</span></code> loop in the DAG file, but the real power of dynamic task mapping comes from being able to have a task generate the list to iterate over.</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="nd">@task</span>
 <span class="k">def</span> <span class="nf">make_list</span><span class="p">():</span>
     <span class="c1"># This can also be from an API call, checking a database, -- almost anything you like, as long as the</span>
@@ -900,7 +900,7 @@
 <div class="section" id="what-data-types-can-be-expanded">
 <h2>What data types can be expanded?<a class="headerlink" href="#what-data-types-can-be-expanded" title="Permalink to this headline">¶</a></h2>
 <p>Currently it is only possible to map against a dict, a list, or one of those types stored in XCom as the result of a task.</p>
-<p>If an upstream task returns an unmappable type, the mapped task will fail at run-time with an <code class="docutils literal notranslate"><span class="pre">UnmappableXComTypePushed</span></code> exception. For instance, you can’t have the upstream task return a plain string – it must be a list or a dict.</p>
+<p>If an upstream task returns an unmappable type, the mapped task will fail at run-time with an <code class="docutils literal notranslate"><span class="pre">UnmappableXComTypePushed</span></code> exception. For instance, you can't have the upstream task return a plain string – it must be a list or a dict.</p>
 </div>
 <div class="section" id="how-do-templated-fields-and-mapped-arguments-interact">
 <h2>How do templated fields and mapped arguments interact?<a class="headerlink" href="#how-do-templated-fields-and-mapped-arguments-interact" title="Permalink to this headline">¶</a></h2>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/index.html b/docs-archive/apache-airflow/2.3.0/concepts/index.html
index e9d43a112..09b545907 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/index.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/index.html
@@ -686,7 +686,7 @@
 <div></div></blockquote>
 <div class="section" id="concepts">
 <h1>Concepts<a class="headerlink" href="#concepts" title="Permalink to this headline">¶</a></h1>
-<p>Here you can find detailed documentation about each one of Airflow’s core concepts and how to use them, as well as a high-level <a class="reference internal" href="overview.html"><span class="doc">architectural overview</span></a>.</p>
+<p>Here you can find detailed documentation about each one of Airflow's core concepts and how to use them, as well as a high-level <a class="reference internal" href="overview.html"><span class="doc">architectural overview</span></a>.</p>
 <p><strong>Architecture</strong></p>
 <div class="toctree-wrapper compound">
 <ul>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/operators.html b/docs-archive/apache-airflow/2.3.0/concepts/operators.html
index 8f5ec5944..2ac1c706e 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/operators.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/operators.html
@@ -717,7 +717,7 @@
 <li><p><a class="reference internal" href="../_api/airflow/operators/email/index.html#airflow.operators.email.EmailOperator" title="airflow.operators.email.EmailOperator"><code class="xref py py-class docutils literal notranslate"><span class="pre">EmailOperator</span></code></a> - sends an email</p></li>
 </ul>
 <p>For a list of all core operators, see: <a class="reference internal" href="../operators-and-hooks-ref.html"><span class="doc">Core Operators and Hooks Reference</span></a>.</p>
-<p>If the operator you need isn’t installed with Airflow by default, you can probably find it as part of our huge set of community <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span class="xref std std-doc">provider packages</span></a>. Some popular operators from here include:</p>
+<p>If the operator you need isn't installed with Airflow by default, you can probably find it as part of our huge set of community <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span class="xref std std-doc">provider packages</span></a>. Some popular operators from here include:</p>
 <ul class="simple">
 <li><p><a class="reference external" href="/docs/apache-airflow-providers-http/stable/_api/airflow/providers/http/operators/http/index.html#airflow.providers.http.operators.http.SimpleHttpOperator" title="(in apache-airflow-providers-http v2.1.2)"><code class="xref py py-class docutils literal notranslate"><span class="pre">SimpleHttpOperator</span></code></a></p></li>
 <li><p><a class="reference external" href="/docs/apache-airflow-providers-mysql/stable/_api/airflow/providers/mysql/operators/mysql/index.html#airflow.providers.mysql.operators.mysql.MySqlOperator" title="(in apache-airflow-providers-mysql v2.2.3)"><code class="xref py py-class docutils literal notranslate"><span class="pre">MySqlOperator</span></code></a></p></li>
@@ -736,8 +736,8 @@ and transfers in our
 <a class="reference external" href="/docs/apache-airflow-providers/operators-and-hooks-ref/index.html" title="(in apache-airflow-providers vdevel)"><span class="xref std std-doc">providers packages</span></a> documentation.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>Inside Airflow’s code, we often mix the concepts of <a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> and Operators, and they are mostly
-interchangeable. However, when we talk about a <em>Task</em>, we mean the generic “unit of execution” of a
+<p>Inside Airflow's code, we often mix the concepts of <a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> and Operators, and they are mostly
+interchangeable. However, when we talk about a <em>Task</em>, we mean the generic &quot;unit of execution&quot; of a
 DAG; when we talk about an <em>Operator</em>, we mean a reusable, pre-made Task template whose logic
 is all done for you and that just needs some arguments.</p>
 </div>
@@ -755,8 +755,8 @@ is all done for you and that just needs some arguments.</p>
 <span class="p">)</span>
 </pre></div>
 </div>
-<p>Here, <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">ds</span> <span class="pre">}}</span></code> is a templated variable, and because the <code class="docutils literal notranslate"><span class="pre">env</span></code> parameter of the <code class="docutils literal notranslate"><span class="pre">BashOperator</span></code> is templated with Jinja, the data interval’s start date will be available as an environment variable named <code class="docu [...]
-<p>You can use Jinja templating with every parameter that is marked as “templated” in the documentation. Template substitution occurs just before the <code class="docutils literal notranslate"><span class="pre">pre_execute</span></code> function of your operator is called.</p>
+<p>Here, <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">ds</span> <span class="pre">}}</span></code> is a templated variable, and because the <code class="docutils literal notranslate"><span class="pre">env</span></code> parameter of the <code class="docutils literal notranslate"><span class="pre">BashOperator</span></code> is templated with Jinja, the data interval's start date will be available as an environment variable named <code class="docu [...]
+<p>You can use Jinja templating with every parameter that is marked as &quot;templated&quot; in the documentation. Template substitution occurs just before the <code class="docutils literal notranslate"><span class="pre">pre_execute</span></code> function of your operator is called.</p>
 <p>You can also use Jinja templating with nested fields, as long as these nested fields are marked as templated in the structure they belong to: fields registered in <code class="docutils literal notranslate"><span class="pre">template_fields</span></code> property will be submitted to template substitution, like the <code class="docutils literal notranslate"><span class="pre">path</span></code> field in the example below:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">MyDataReader</span><span class="p">:</span>
     <span class="n">template_fields</span><span class="p">:</span> <span class="n">Sequence</span><span class="p">[</span><span class="nb">str</span><span class="p">]</span> <span class="o">=</span> <span class="p">(</span><span class="s2">&quot;path&quot;</span><span class="p">,)</span>
@@ -820,7 +820,7 @@ is all done for you and that just needs some arguments.</p>
 <div class="section" id="rendering-fields-as-native-python-objects">
 <span id="concepts-templating-native-objects"></span><h3>Rendering Fields as Native Python Objects<a class="headerlink" href="#rendering-fields-as-native-python-objects" title="Permalink to this headline">¶</a></h3>
 <p>By default, all the <code class="docutils literal notranslate"><span class="pre">template_fields</span></code> are rendered as strings.</p>
-<p>Example, let’s say <code class="docutils literal notranslate"><span class="pre">extract</span></code> task pushes a dictionary
+<p>Example, let's say <code class="docutils literal notranslate"><span class="pre">extract</span></code> task pushes a dictionary
 (Example: <code class="docutils literal notranslate"><span class="pre">{&quot;1001&quot;:</span> <span class="pre">301.27,</span> <span class="pre">&quot;1002&quot;:</span> <span class="pre">433.21,</span> <span class="pre">&quot;1003&quot;:</span> <span class="pre">502.22}</span></code>) to <a class="reference internal" href="xcoms.html#concepts-xcom"><span class="std std-ref">XCom</span></a> table.
 Now, when the following task is run, <code class="docutils literal notranslate"><span class="pre">order_data</span></code> argument is passed a string, example:
 <code class="docutils literal notranslate"><span class="pre">'{&quot;1001&quot;:</span> <span class="pre">301.27,</span> <span class="pre">&quot;1002&quot;:</span> <span class="pre">433.21,</span> <span class="pre">&quot;1003&quot;:</span> <span class="pre">502.22}'</span></code>.</p>
@@ -866,7 +866,7 @@ you can pass <code class="docutils literal notranslate"><span class="pre">render
 </pre></div>
 </div>
 <p>In this case, <code class="docutils literal notranslate"><span class="pre">order_data</span></code> argument is passed: <code class="docutils literal notranslate"><span class="pre">{&quot;1001&quot;:</span> <span class="pre">301.27,</span> <span class="pre">&quot;1002&quot;:</span> <span class="pre">433.21,</span> <span class="pre">&quot;1003&quot;:</span> <span class="pre">502.22}</span></code>.</p>
-<p>Airflow uses Jinja’s <a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/nativetypes/">NativeEnvironment</a>
+<p>Airflow uses Jinja's <a class="reference external" href="https://jinja.palletsprojects.com/en/2.11.x/nativetypes/">NativeEnvironment</a>
 when <code class="docutils literal notranslate"><span class="pre">render_template_as_native_obj</span></code> is set to <code class="docutils literal notranslate"><span class="pre">True</span></code>.
 With <code class="docutils literal notranslate"><span class="pre">NativeEnvironment</span></code>, rendering a template produces a native Python type.</p>
 </div>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/overview.html b/docs-archive/apache-airflow/2.3.0/concepts/overview.html
index a67958be8..77a1622e0 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/overview.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/overview.html
@@ -711,7 +711,7 @@
 </ul>
 <img alt="../_images/arch-diag-basic.png" src="../_images/arch-diag-basic.png" />
 <p>Most executors will generally also introduce other components to let them talk to their workers - like a task queue - but you can still think of the executor and its workers as a single logical component in Airflow overall, handling the actual task execution.</p>
-<p>Airflow itself is agnostic to what you’re running - it will happily orchestrate and run anything, either with high-level support from one of our providers, or directly as a command using the shell or Python <a class="reference internal" href="operators.html"><span class="doc">Operators</span></a>.</p>
+<p>Airflow itself is agnostic to what you're running - it will happily orchestrate and run anything, either with high-level support from one of our providers, or directly as a command using the shell or Python <a class="reference internal" href="operators.html"><span class="doc">Operators</span></a>.</p>
 <div class="section" id="workloads">
 <h2>Workloads<a class="headerlink" href="#workloads" title="Permalink to this headline">¶</a></h2>
 <p>A DAG runs through a series of <a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a>, and there are three common types of task you will see:</p>
@@ -720,12 +720,12 @@
 <li><p><a class="reference internal" href="sensors.html"><span class="doc">Sensors</span></a>, a special subclass of Operators which are entirely about waiting for an external event to happen.</p></li>
 <li><p>A <a class="reference internal" href="taskflow.html"><span class="doc">TaskFlow</span></a>-decorated <code class="docutils literal notranslate"><span class="pre">&#64;task</span></code>, which is a custom Python function packaged up as a Task.</p></li>
 </ul>
-<p>Internally, these are all actually subclasses of Airflow’s <code class="docutils literal notranslate"><span class="pre">BaseOperator</span></code>, and the concepts of Task and Operator are somewhat interchangeable, but it’s useful to think of them as separate concepts - essentially, Operators and Sensors are <em>templates</em>, and when you call one in a DAG file, you’re making a Task.</p>
+<p>Internally, these are all actually subclasses of Airflow's <code class="docutils literal notranslate"><span class="pre">BaseOperator</span></code>, and the concepts of Task and Operator are somewhat interchangeable, but it's useful to think of them as separate concepts - essentially, Operators and Sensors are <em>templates</em>, and when you call one in a DAG file, you're making a Task.</p>
 </div>
 <div class="section" id="control-flow">
 <h2>Control Flow<a class="headerlink" href="#control-flow" title="Permalink to this headline">¶</a></h2>
-<p><a class="reference internal" href="dags.html"><span class="doc">DAGs</span></a> are designed to be run many times, and multiple runs of them can happen in parallel. DAGs are parameterized, always including an interval they are “running for” (the <a class="reference internal" href="../dag-run.html#data-interval"><span class="std std-ref">data interval</span></a>), but with other optional parameters as well.</p>
-<p><a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> have dependencies declared on each other. You’ll see this in a DAG either using the <code class="docutils literal notranslate"><span class="pre">&gt;&gt;</span></code> and <code class="docutils literal notranslate"><span class="pre">&lt;&lt;</span></code> operators:</p>
+<p><a class="reference internal" href="dags.html"><span class="doc">DAGs</span></a> are designed to be run many times, and multiple runs of them can happen in parallel. DAGs are parameterized, always including an interval they are &quot;running for&quot; (the <a class="reference internal" href="../dag-run.html#data-interval"><span class="std std-ref">data interval</span></a>), but with other optional parameters as well.</p>
+<p><a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> have dependencies declared on each other. You'll see this in a DAG either using the <code class="docutils literal notranslate"><span class="pre">&gt;&gt;</span></code> and <code class="docutils literal notranslate"><span class="pre">&lt;&lt;</span></code> operators:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">first_task</span> <span class="o">&gt;&gt;</span> <span class="p">[</span><span class="n">second_task</span><span class="p">,</span> <span class="n">third_task</span><span class="p">]</span>
 <span class="n">fourth_task</span> <span class="o">&lt;&lt;</span> <span class="n">third_task</span>
 </pre></div>
@@ -735,21 +735,21 @@
 <span class="n">fourth_task</span><span class="o">.</span><span class="n">set_upstream</span><span class="p">(</span><span class="n">third_task</span><span class="p">)</span>
 </pre></div>
 </div>
-<p>These dependencies are what make up the “edges” of the graph, and how Airflow works out which order to run your tasks in. By default, a task will wait for all of its upstream tasks to succeed before it runs, but this can be customized using features like <a class="reference internal" href="dags.html#concepts-branching"><span class="std std-ref">Branching</span></a>, <a class="reference internal" href="dags.html#concepts-latest-only"><span class="std std-ref">LatestOnly</span></a>, and [...]
+<p>These dependencies are what make up the &quot;edges&quot; of the graph, and how Airflow works out which order to run your tasks in. By default, a task will wait for all of its upstream tasks to succeed before it runs, but this can be customized using features like <a class="reference internal" href="dags.html#concepts-branching"><span class="std std-ref">Branching</span></a>, <a class="reference internal" href="dags.html#concepts-latest-only"><span class="std std-ref">LatestOnly</span [...]
 <p>To pass data between tasks you have two options:</p>
 <ul class="simple">
-<li><p><a class="reference internal" href="xcoms.html"><span class="doc">XComs</span></a> (“Cross-communications”), a system where you can have tasks push and pull small bits of metadata.</p></li>
+<li><p><a class="reference internal" href="xcoms.html"><span class="doc">XComs</span></a> (&quot;Cross-communications&quot;), a system where you can have tasks push and pull small bits of metadata.</p></li>
 <li><p>Uploading and downloading large files from a storage service (either one you run, or part of a public cloud)</p></li>
 </ul>
-<p>Airflow sends out Tasks to run on Workers as space becomes available, so there’s no guarantee all the tasks in your DAG will run on the same worker or the same machine.</p>
-<p>As you build out your DAGs, they are likely to get very complex, so Airflow provides several mechanisms for making this more sustainable - <a class="reference internal" href="dags.html#concepts-subdags"><span class="std std-ref">SubDAGs</span></a> let you make “reusable” DAGs you can embed into other ones, and <a class="reference internal" href="dags.html#concepts-taskgroups"><span class="std std-ref">TaskGroups</span></a> let you visually group tasks in the UI.</p>
+<p>Airflow sends out Tasks to run on Workers as space becomes available, so there's no guarantee all the tasks in your DAG will run on the same worker or the same machine.</p>
+<p>As you build out your DAGs, they are likely to get very complex, so Airflow provides several mechanisms for making this more sustainable - <a class="reference internal" href="dags.html#concepts-subdags"><span class="std std-ref">SubDAGs</span></a> let you make &quot;reusable&quot; DAGs you can embed into other ones, and <a class="reference internal" href="dags.html#concepts-taskgroups"><span class="std std-ref">TaskGroups</span></a> let you visually group tasks in the UI.</p>
 <p>There are also features for letting you easily pre-configure access to a central resource, like a datastore, in the form of <a class="reference internal" href="connections.html"><span class="doc">Connections &amp; Hooks</span></a>, and for limiting concurrency, via <a class="reference internal" href="pools.html"><span class="doc">Pools</span></a>.</p>
 </div>
 <div class="section" id="user-interface">
 <h2>User interface<a class="headerlink" href="#user-interface" title="Permalink to this headline">¶</a></h2>
 <p>Airflow comes with a user interface that lets you see what DAGs and their tasks are doing, trigger runs of DAGs, view logs, and do some limited debugging and resolution of problems with your DAGs.</p>
 <img alt="../_images/dags.png" src="../_images/dags.png" />
-<p>It’s generally the best way to see the status of your Airflow installation as a whole, as well as diving into individual DAGs to see their layout, the status of each task, and the logs from each task.</p>
+<p>It's generally the best way to see the status of your Airflow installation as a whole, as well as diving into individual DAGs to see their layout, the status of each task, and the logs from each task.</p>
 </div>
 </div>
 
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/params.html b/docs-archive/apache-airflow/2.3.0/concepts/params.html
index 60b184d20..4c878843b 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/params.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/params.html
@@ -704,12 +704,12 @@
 <span id="concepts-params"></span><h1>Params<a class="headerlink" href="#params" title="Permalink to this headline">¶</a></h1>
 <p>Params are how Airflow provides runtime configuration to tasks.
 When you trigger a DAG manually, you can modify its Params before the dagrun starts.
-If the user-supplied values don’t pass validation, Airflow shows a warning instead of creating the dagrun.
+If the user-supplied values don't pass validation, Airflow shows a warning instead of creating the dagrun.
 (For scheduled runs, the default values are used.)</p>
 <div class="section" id="adding-params-to-a-dag">
 <h2>Adding Params to a DAG<a class="headerlink" href="#adding-params-to-a-dag" title="Permalink to this headline">¶</a></h2>
 <p>To add Params to a <a class="reference internal" href="../_api/airflow/models/dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><code class="xref py py-class docutils literal notranslate"><span class="pre">DAG</span></code></a>, initialize it with the <code class="docutils literal notranslate"><span class="pre">params</span></code> kwarg.
-Use a dictionary that maps Param names to a either a <a class="reference internal" href="../_api/airflow/models/param/index.html#airflow.models.param.Param" title="airflow.models.param.Param"><code class="xref py py-class docutils literal notranslate"><span class="pre">Param</span></code></a> or an object indicating the parameter’s default value.</p>
+Use a dictionary that maps Param names to a either a <a class="reference internal" href="../_api/airflow/models/param/index.html#airflow.models.param.Param" title="airflow.models.param.Param"><code class="xref py py-class docutils literal notranslate"><span class="pre">Param</span></code></a> or an object indicating the parameter's default value.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">airflow</span> <span class="kn">import</span> <span class="n">DAG</span>
 <span class="kn">from</span> <span class="nn">airflow.models.param</span> <span class="kn">import</span> <span class="n">Param</span>
 
@@ -747,7 +747,7 @@ You can change this by setting <code class="docutils literal notranslate"><span
 <span class="p">)</span> <span class="k">as</span> <span class="n">the_dag</span><span class="p">:</span>
 </pre></div>
 </div>
-<p>This way, the Param’s type is respected when its provided to your task.</p>
+<p>This way, the Param's type is respected when its provided to your task.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># prints &lt;class &#39;str&#39;&gt; by default</span>
 <span class="c1"># prints &lt;class &#39;int&#39;&gt; if render_template_as_native_obj=True</span>
 <span class="n">PythonOperator</span><span class="p">(</span>
@@ -761,7 +761,7 @@ You can change this by setting <code class="docutils literal notranslate"><span
 <span class="p">)</span>
 </pre></div>
 </div>
-<p>Another way to access your param is via a task’s <code class="docutils literal notranslate"><span class="pre">context</span></code> kwarg.</p>
+<p>Another way to access your param is via a task's <code class="docutils literal notranslate"><span class="pre">context</span></code> kwarg.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">print_x</span><span class="p">(</span><span class="o">**</span><span class="n">context</span><span class="p">):</span>
     <span class="nb">print</span><span class="p">(</span><span class="n">context</span><span class="p">[</span><span class="s2">&quot;params&quot;</span><span class="p">][</span><span class="s2">&quot;x&quot;</span><span class="p">])</span>
 
@@ -782,8 +782,8 @@ You can change this by setting <code class="docutils literal notranslate"><span
 <span class="p">)</span>
 </pre></div>
 </div>
-<p>If there’s already a dag param with that name, the task-level default will take precedence over the dag-level default.
-If a user supplies their own value when the DAG was triggered, Airflow ignores all defaults and uses the user’s value.</p>
+<p>If there's already a dag param with that name, the task-level default will take precedence over the dag-level default.
+If a user supplies their own value when the DAG was triggered, Airflow ignores all defaults and uses the user's value.</p>
 </div>
 <div class="section" id="json-schema-validation">
 <h2>JSON Schema Validation<a class="headerlink" href="#json-schema-validation" title="Permalink to this headline">¶</a></h2>
@@ -816,7 +816,7 @@ If a user supplies their own value when the DAG was triggered, Airflow ignores a
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>As of now, for security reasons, one can not use Param objects derived out of custom classes. We are
-planning to have a registration system for custom Param classes, just like we’ve for Operator ExtraLinks.</p>
+planning to have a registration system for custom Param classes, just like we've for Operator ExtraLinks.</p>
 </div>
 </div>
 <div class="section" id="disabling-runtime-param-modification">
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/pools.html b/docs-archive/apache-airflow/2.3.0/concepts/pools.html
index 2d5a1f642..e5bb8df4a 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/pools.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/pools.html
@@ -717,7 +717,7 @@ initialized with 128 slots and can be modified through the UI or CLI (but cannot
 <div class="section" id="using-multiple-pool-slots">
 <h2>Using multiple pool slots<a class="headerlink" href="#using-multiple-pool-slots" title="Permalink to this headline">¶</a></h2>
 <p>Airflow tasks will each occupy a single pool slot by default, but they can be configured to occupy more with the <code class="docutils literal notranslate"><span class="pre">pool_slots</span></code> argument if required.
-This is particularly useful when several tasks that belong to the same pool don’t carry the same “computational weight”.</p>
+This is particularly useful when several tasks that belong to the same pool don't carry the same &quot;computational weight&quot;.</p>
 <p>For instance, consider a pool with 2 slots, <code class="docutils literal notranslate"><span class="pre">Pool(pool='maintenance',</span> <span class="pre">slots=2)</span></code>, and the following tasks:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="n">BashOperator</span><span class="p">(</span>
     <span class="n">task_id</span><span class="o">=</span><span class="s2">&quot;heavy_task&quot;</span><span class="p">,</span>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/priority-weight.html b/docs-archive/apache-airflow/2.3.0/concepts/priority-weight.html
index 16abc95a2..46e46abab 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/priority-weight.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/priority-weight.html
@@ -691,7 +691,7 @@
 <p><code class="docutils literal notranslate"><span class="pre">priority_weight</span></code> defines priorities in the executor queue. The default <code class="docutils literal notranslate"><span class="pre">priority_weight</span></code> is <code class="docutils literal notranslate"><span class="pre">1</span></code>, and can be
 bumped to any integer. Moreover, each task has a true <code class="docutils literal notranslate"><span class="pre">priority_weight</span></code> that is calculated based on its
 <code class="docutils literal notranslate"><span class="pre">weight_rule</span></code> which defines weighting method used for the effective total priority weight of the task.</p>
-<p>By default, Airflow’s weighting method is <code class="docutils literal notranslate"><span class="pre">downstream</span></code>. You can find other weighting methods in
+<p>By default, Airflow's weighting method is <code class="docutils literal notranslate"><span class="pre">downstream</span></code>. You can find other weighting methods in
 <code class="xref py py-class docutils literal notranslate"><span class="pre">airflow.utils.WeightRule</span></code>.</p>
 <p>There are three weighting methods.</p>
 <ul>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/scheduler.html b/docs-archive/apache-airflow/2.3.0/concepts/scheduler.html
index a52d64a56..035b8c103 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/scheduler.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/scheduler.html
@@ -357,10 +357,10 @@
 </ul>
 </li>
 <li class="toctree-l3"><a class="reference internal" href="#fine-tuning-your-scheduler-performance">Fine-tuning your Scheduler performance</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#what-impacts-scheduler-s-performance">What impacts scheduler’s performance</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#how-to-approach-scheduler-s-fine-tuning">How to approach Scheduler’s fine-tuning</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#what-resources-might-limit-scheduler-s-performance">What resources might limit Scheduler’s performance</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#what-can-you-do-to-improve-scheduler-s-performance">What can you do, to improve Scheduler’s performance</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#what-impacts-scheduler-s-performance">What impacts scheduler's performance</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#how-to-approach-scheduler-s-fine-tuning">How to approach Scheduler's fine-tuning</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#what-resources-might-limit-scheduler-s-performance">What resources might limit Scheduler's performance</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#what-can-you-do-to-improve-scheduler-s-performance">What can you do, to improve Scheduler's performance</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#scheduler-configuration-options">Scheduler Configuration options</a></li>
 </ul>
 </li>
@@ -564,10 +564,10 @@
 </ul>
 </li>
 <li class="toctree-l3"><a class="reference internal" href="#fine-tuning-your-scheduler-performance">Fine-tuning your Scheduler performance</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#what-impacts-scheduler-s-performance">What impacts scheduler’s performance</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#how-to-approach-scheduler-s-fine-tuning">How to approach Scheduler’s fine-tuning</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#what-resources-might-limit-scheduler-s-performance">What resources might limit Scheduler’s performance</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#what-can-you-do-to-improve-scheduler-s-performance">What can you do, to improve Scheduler’s performance</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#what-impacts-scheduler-s-performance">What impacts scheduler's performance</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#how-to-approach-scheduler-s-fine-tuning">How to approach Scheduler's fine-tuning</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#what-resources-might-limit-scheduler-s-performance">What resources might limit Scheduler's performance</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#what-can-you-do-to-improve-scheduler-s-performance">What can you do, to improve Scheduler's performance</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#scheduler-configuration-options">Scheduler Configuration options</a></li>
 </ul>
 </li>
@@ -743,7 +743,7 @@ execute the <code class="docutils literal notranslate"><span class="pre">airflow
 Subsequent DAG Runs are created by the scheduler process, based on your DAG’s <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>,
 sequentially.</p>
 </div>
-<p>The scheduler won’t trigger your tasks until the period it covers has ended e.g., A job with <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> set as <code class="docutils literal notranslate"><span class="pre">&#64;daily</span></code> runs after the day
+<p>The scheduler won't trigger your tasks until the period it covers has ended e.g., A job with <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> set as <code class="docutils literal notranslate"><span class="pre">&#64;daily</span></code> runs after the day
 has ended. This technique makes sure that whatever data is required for that period is fully available before the DAG is executed.
 In the UI, it appears as if Airflow is running your tasks a day <strong>late</strong></p>
 <div class="admonition note">
@@ -760,21 +760,21 @@ that contain tasks to be scheduled.</p>
 </div>
 <div class="section" id="triggering-dag-with-future-date">
 <h2>Triggering DAG with Future Date<a class="headerlink" href="#triggering-dag-with-future-date" title="Permalink to this headline">¶</a></h2>
-<p>If you want to use ‘external trigger’ to run future-dated data intervals, set <code class="docutils literal notranslate"><span class="pre">allow_trigger_in_future</span> <span class="pre">=</span> <span class="pre">True</span></code> in <code class="docutils literal notranslate"><span class="pre">scheduler</span></code> section in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>.
+<p>If you want to use 'external trigger' to run future-dated data intervals, set <code class="docutils literal notranslate"><span class="pre">allow_trigger_in_future</span> <span class="pre">=</span> <span class="pre">True</span></code> in <code class="docutils literal notranslate"><span class="pre">scheduler</span></code> section in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>.
 This only has effect if your DAG has no <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>.
-If you keep default <code class="docutils literal notranslate"><span class="pre">allow_trigger_in_future</span> <span class="pre">=</span> <span class="pre">False</span></code> and try ‘external trigger’ to run future-dated data intervals,
-the scheduler won’t execute it now but the scheduler will execute it in the future once the current date rolls over to the start of the data interval.</p>
+If you keep default <code class="docutils literal notranslate"><span class="pre">allow_trigger_in_future</span> <span class="pre">=</span> <span class="pre">False</span></code> and try 'external trigger' to run future-dated data intervals,
+the scheduler won't execute it now but the scheduler will execute it in the future once the current date rolls over to the start of the data interval.</p>
 </div>
 <div class="section" id="running-more-than-one-scheduler">
 <span id="scheduler-ha"></span><h2>Running More Than One Scheduler<a class="headerlink" href="#running-more-than-one-scheduler" title="Permalink to this headline">¶</a></h2>
-<p>Airflow supports running more than one scheduler concurrently – both for performance reasons and for
+<p>Airflow supports running more than one scheduler concurrently -- both for performance reasons and for
 resiliency.</p>
 <div class="section" id="overview">
 <h3>Overview<a class="headerlink" href="#overview" title="Permalink to this headline">¶</a></h3>
 <p>The <abbr title="highly available">HA</abbr> scheduler is designed to take advantage of the existing metadata database.
 This was primarily done for operational simplicity: every component already has to speak to this DB, and by
 not using direct communication or consensus algorithm between schedulers (Raft, Paxos, etc.) nor another
-consensus tool (Apache Zookeeper, or Consul for instance) we have kept the “operational surface area” to a
+consensus tool (Apache Zookeeper, or Consul for instance) we have kept the &quot;operational surface area&quot; to a
 minimum.</p>
 <p>The scheduler now uses the serialized DAG representation to make its scheduling decisions and the rough
 outline of the scheduling loop is:</p>
@@ -788,8 +788,8 @@ them for execution</p></li>
 </div>
 <div class="section" id="database-requirements">
 <span id="scheduler-ha-db-requirements"></span><h3>Database Requirements<a class="headerlink" href="#database-requirements" title="Permalink to this headline">¶</a></h3>
-<p>The short version is that users of PostgreSQL 10+ or MySQL 8+ are all ready to go – you can start running as
-many copies of the scheduler as you like – there is no further set up or config options needed. If you are
+<p>The short version is that users of PostgreSQL 10+ or MySQL 8+ are all ready to go -- you can start running as
+many copies of the scheduler as you like -- there is no further set up or config options needed. If you are
 using a different database please read on.</p>
 <p>To maintain performance and throughput there is one part of the scheduling loop that does a number of
 calculations in memory (because having to round-trip to the DB for each TaskInstance would be too slow) so we
@@ -799,7 +799,7 @@ be correctly respected. To achieve this we use database row-level locks (using <
 ensuring the various concurrency and pool limits are respected. The critical section is obtained by asking for
 a row-level write lock on every row of the Pool table (roughly equivalent to <code class="docutils literal notranslate"><span class="pre">SELECT</span> <span class="pre">*</span> <span class="pre">FROM</span> <span class="pre">slot_pool</span> <span class="pre">FOR</span>
 <span class="pre">UPDATE</span> <span class="pre">NOWAIT</span></code> but the exact query is slightly different).</p>
-<p>The following databases are fully supported and provide an “optimal” experience:</p>
+<p>The following databases are fully supported and provide an &quot;optimal&quot; experience:</p>
 <ul class="simple">
 <li><p>PostgreSQL 10+</p></li>
 <li><p>MySQL 8+</p></li>
@@ -826,7 +826,7 @@ recommended.</p>
 <div class="section" id="fine-tuning-your-scheduler-performance">
 <h2>Fine-tuning your Scheduler performance<a class="headerlink" href="#fine-tuning-your-scheduler-performance" title="Permalink to this headline">¶</a></h2>
 <div class="section" id="what-impacts-scheduler-s-performance">
-<h3>What impacts scheduler’s performance<a class="headerlink" href="#what-impacts-scheduler-s-performance" title="Permalink to this headline">¶</a></h3>
+<h3>What impacts scheduler's performance<a class="headerlink" href="#what-impacts-scheduler-s-performance" title="Permalink to this headline">¶</a></h3>
 <p>The Scheduler is responsible for two operations:</p>
 <ul class="simple">
 <li><p>continuously parsing DAG files and synchronizing with the DAG in the database</p></li>
@@ -872,13 +872,13 @@ more throughput/faster filesystem</p></li>
 </dl>
 </li>
 </ul>
-<p>In order to perform fine-tuning, it’s good to understand how Scheduler works under-the-hood.
+<p>In order to perform fine-tuning, it's good to understand how Scheduler works under-the-hood.
 You can take a look at the Airflow Summit 2021 talk
 <a class="reference external" href="https://youtu.be/DYC4-xElccE">Deep Dive into the Airflow Scheduler talk</a> to perform the fine-tuning.</p>
 </div>
 <div class="section" id="how-to-approach-scheduler-s-fine-tuning">
-<h3>How to approach Scheduler’s fine-tuning<a class="headerlink" href="#how-to-approach-scheduler-s-fine-tuning" title="Permalink to this headline">¶</a></h3>
-<p>Airflow gives you a lot of “knobs” to turn to fine tune the performance but it’s a separate task,
+<h3>How to approach Scheduler's fine-tuning<a class="headerlink" href="#how-to-approach-scheduler-s-fine-tuning" title="Permalink to this headline">¶</a></h3>
+<p>Airflow gives you a lot of &quot;knobs&quot; to turn to fine tune the performance but it's a separate task,
 depending on your particular deployment, your DAG structure, hardware availability and expectations,
 to decide which knobs to turn to get best effect for you. Part of the job when managing the
 deployment is to decide what you are going to optimize for. Some users are ok with
@@ -902,7 +902,7 @@ the observation of your performance, bottlenecks. Performance improvement is an
 </ul>
 </div>
 <div class="section" id="what-resources-might-limit-scheduler-s-performance">
-<h3>What resources might limit Scheduler’s performance<a class="headerlink" href="#what-resources-might-limit-scheduler-s-performance" title="Permalink to this headline">¶</a></h3>
+<h3>What resources might limit Scheduler's performance<a class="headerlink" href="#what-resources-might-limit-scheduler-s-performance" title="Permalink to this headline">¶</a></h3>
 <p>There are several areas of resource usage that you should pay attention to:</p>
 <ul class="simple">
 <li><p>FileSystem performance. Airflow Scheduler relies heavily on parsing (sometimes a lot) of Python
@@ -923,7 +923,7 @@ distribution mechanisms have other characteristics that might make them not the
 but if your problems with performance come from distributed filesystem performance, they might be the
 best approach to follow.</p></li>
 <li><p>Database connections and Database usage might become a problem as you want to increase performance and
-process more things in parallel. Airflow is known from being “database-connection hungry” - the more DAGs
+process more things in parallel. Airflow is known from being &quot;database-connection hungry&quot; - the more DAGs
 you have and the more you want to process in parallel, the more database connections will be opened.
 This is generally not a problem for MySQL as its model of handling connections is thread-based, but this
 might be a problem for Postgres, where connection handling is process-based. It is a general consensus
@@ -940,7 +940,7 @@ submitting the files and getting them available in Airflow UI and executed by Sc
 the way how your DAGs are built, avoiding external data sources is your best approach to improve CPU
 usage. If you have more CPUs available, you can increase number of processing threads
 <a class="reference internal" href="../configurations-ref.html#config-scheduler-parsing-processes"><span class="std std-ref">parsing_processes</span></a>, Also Airflow Scheduler scales almost linearly with
-several instances, so you can also add more Schedulers if your Scheduler’s performance is CPU-bound.</p></li>
+several instances, so you can also add more Schedulers if your Scheduler's performance is CPU-bound.</p></li>
 <li><p>Airflow might use quite significant amount of memory when you try to get more performance out of it.
 Often more performance is achieved in Airflow by increasing number of processes handling the load,
 and each process requires whole interpreter of Python loaded, a lot of classes imported, temporary
@@ -957,7 +957,7 @@ Usually you should look at <code class="docutils literal notranslate"><span clas
 </ul>
 </div>
 <div class="section" id="what-can-you-do-to-improve-scheduler-s-performance">
-<h3>What can you do, to improve Scheduler’s performance<a class="headerlink" href="#what-can-you-do-to-improve-scheduler-s-performance" title="Permalink to this headline">¶</a></h3>
+<h3>What can you do, to improve Scheduler's performance<a class="headerlink" href="#what-can-you-do-to-improve-scheduler-s-performance" title="Permalink to this headline">¶</a></h3>
 <p>When you know what your resource usage is, the improvements that you can consider might be:</p>
 <ul class="simple">
 <li><p>improve the logic, efficiency of parsing and reduce complexity of your top-level DAG Python code. It is
@@ -972,11 +972,11 @@ actions like increasing number of schedulers, parsing processes or decreasing in
 frequent actions might bring improvements in performance at the expense of higher utilization of those.</p></li>
 <li><p>increase hardware capacity (for example if you see that CPU is limiting you or that I/O you use for
 DAG filesystem is at its limits). Often the problem with scheduler performance is
-simply because your system is not “capable” enough and this might be the only way. For example if
+simply because your system is not &quot;capable&quot; enough and this might be the only way. For example if
 you see that you are using all CPU you have on machine, you might want to add another scheduler on
 a new machine - in most cases, when you add 2nd or 3rd scheduler, the capacity of scheduling grows
 linearly (unless the shared database or filesystem is a bottleneck).</p></li>
-<li><p>experiment with different values for the “scheduler tunables”. Often you might get better effects by
+<li><p>experiment with different values for the &quot;scheduler tunables&quot;. Often you might get better effects by
 simply exchanging one performance aspect for another. For example if you want to decrease the
 CPU usage, you might increase file processing interval (but the result will be that new DAGs will
 appear with bigger delay). Usually performance tuning is the art of balancing different aspects.</p></li>
@@ -993,7 +993,7 @@ However you can also look at other non-performance-related scheduler configurati
 <li><p><a class="reference internal" href="../configurations-ref.html#config-scheduler-max-dagruns-to-create-per-loop"><span class="std std-ref">max_dagruns_to_create_per_loop</span></a></p>
 <p>This changes the number of DAGs that are locked by each scheduler when
 creating DAG runs. One possible reason for setting this lower is if you
-have huge DAGs (in the order of 10k+ tasks per DAG) and are running multiple schedulers, you won’t want one
+have huge DAGs (in the order of 10k+ tasks per DAG) and are running multiple schedulers, you won't want one
 scheduler to do all the work.</p>
 </li>
 <li><p><a class="reference internal" href="../configurations-ref.html#config-scheduler-max-dagruns-per-loop-to-schedule"><span class="std std-ref">max_dagruns_per_loop_to_schedule</span></a></p>
@@ -1019,11 +1019,11 @@ period.</p>
 <p>How often (in seconds) should the scheduler check for orphaned tasks or dead
 SchedulerJobs.</p>
 <p>This setting controls how a dead scheduler will be noticed and the tasks it
-was “supervising” get picked up by another scheduler. The tasks will stay
+was &quot;supervising&quot; get picked up by another scheduler. The tasks will stay
 running, so there is no harm in not detecting this for a while.</p>
-<p>When a SchedulerJob is detected as “dead” (as determined by
+<p>When a SchedulerJob is detected as &quot;dead&quot; (as determined by
 <a class="reference internal" href="../configurations-ref.html#config-scheduler-scheduler-health-check-threshold"><span class="std std-ref">scheduler_health_check_threshold</span></a>) any running or
-queued tasks that were launched by the dead process will be “adopted” and
+queued tasks that were launched by the dead process will be &quot;adopted&quot; and
 monitored by this scheduler instead.</p>
 </li>
 <li><p><a class="reference internal" href="../configurations-ref.html#config-scheduler-dag-dir-list-interval"><span class="std std-ref">dag_dir_list_interval</span></a>
@@ -1141,10 +1141,10 @@ but might starve out other DAGs in some circumstances.</p></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#fine-tuning-your-scheduler-performance">Fine-tuning your Scheduler performance</a><ul>
-<li><a class="reference internal" href="#what-impacts-scheduler-s-performance">What impacts scheduler’s performance</a></li>
-<li><a class="reference internal" href="#how-to-approach-scheduler-s-fine-tuning">How to approach Scheduler’s fine-tuning</a></li>
-<li><a class="reference internal" href="#what-resources-might-limit-scheduler-s-performance">What resources might limit Scheduler’s performance</a></li>
-<li><a class="reference internal" href="#what-can-you-do-to-improve-scheduler-s-performance">What can you do, to improve Scheduler’s performance</a></li>
+<li><a class="reference internal" href="#what-impacts-scheduler-s-performance">What impacts scheduler's performance</a></li>
+<li><a class="reference internal" href="#how-to-approach-scheduler-s-fine-tuning">How to approach Scheduler's fine-tuning</a></li>
+<li><a class="reference internal" href="#what-resources-might-limit-scheduler-s-performance">What resources might limit Scheduler's performance</a></li>
+<li><a class="reference internal" href="#what-can-you-do-to-improve-scheduler-s-performance">What can you do, to improve Scheduler's performance</a></li>
 <li><a class="reference internal" href="#scheduler-configuration-options">Scheduler Configuration options</a></li>
 </ul>
 </li>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/smart-sensors.html b/docs-archive/apache-airflow/2.3.0/concepts/smart-sensors.html
index 49275ffd2..d5aed5617 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/smart-sensors.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/smart-sensors.html
@@ -747,7 +747,7 @@ The users use the same class names (e.g. HivePartitionSensor) in their DAGs and
 the control to use smart sensors or not, unless they exclude their tasks explicitly.</p></li>
 </ul>
 <p>Enabling/disabling the smart sensor service is a system level configuration change.
-It is transparent to the individual users. Existing DAGs don’t need to be changed for
+It is transparent to the individual users. Existing DAGs don't need to be changed for
 enabling/disabling the smart sensor. Rotating centralized smart sensor tasks will not
 cause any user’s sensor task failure.</p>
 <ul class="simple">
@@ -759,8 +759,8 @@ cause any user’s sensor task failure.</p>
 <ul class="simple">
 <li><p>Define <code class="docutils literal notranslate"><span class="pre">poke_context_fields</span></code> as class attribute in the sensor. <code class="docutils literal notranslate"><span class="pre">poke_context_fields</span></code>
 include all key names used for initializing a sensor object.</p></li>
-<li><p>In <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>, add the new operator’s classname to <code class="docutils literal notranslate"><span class="pre">[smart_sensor]</span> <span class="pre">sensors_enabled</span></code>.
-All supported sensors’ classname should be comma separated.</p></li>
+<li><p>In <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>, add the new operator's classname to <code class="docutils literal notranslate"><span class="pre">[smart_sensor]</span> <span class="pre">sensors_enabled</span></code>.
+All supported sensors' classname should be comma separated.</p></li>
 </ul>
 </div>
 <div class="section" id="migrating-to-deferrable-operators">
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/taskflow.html b/docs-archive/apache-airflow/2.3.0/concepts/taskflow.html
index 2b5690f25..f96db56fa 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/taskflow.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/taskflow.html
@@ -726,7 +726,7 @@
 <p>Here, there are three tasks - <code class="docutils literal notranslate"><span class="pre">get_ip</span></code>, <code class="docutils literal notranslate"><span class="pre">compose_email</span></code>, and <code class="docutils literal notranslate"><span class="pre">send_email</span></code>.</p>
 <p>The first two are declared using TaskFlow, and automatically pass the return value of <code class="docutils literal notranslate"><span class="pre">get_ip</span></code> into <code class="docutils literal notranslate"><span class="pre">compose_email</span></code>, not only linking the XCom across, but automatically declaring that <code class="docutils literal notranslate"><span class="pre">compose_email</span></code> is <em>downstream</em> of <code class="docutils literal notranslate">< [...]
 <p><code class="docutils literal notranslate"><span class="pre">send_email</span></code> is a more traditional Operator, but even it can use the return value of <code class="docutils literal notranslate"><span class="pre">compose_email</span></code> to set its parameters, and again, automatically work out that it must be <em>downstream</em> of <code class="docutils literal notranslate"><span class="pre">compose_email</span></code>.</p>
-<p>You can also use a plain value or variable to call a TaskFlow function - for example, this will work as you expect (but, of course, won’t run the code inside the task until the DAG is executed - the <code class="docutils literal notranslate"><span class="pre">name</span></code> value is persisted as a task parameter until that time):</p>
+<p>You can also use a plain value or variable to call a TaskFlow function - for example, this will work as you expect (but, of course, won't run the code inside the task until the DAG is executed - the <code class="docutils literal notranslate"><span class="pre">name</span></code> value is persisted as a task parameter until that time):</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="nd">@task</span>
 <span class="k">def</span> <span class="nf">hello_name</span><span class="p">(</span><span class="n">name</span><span class="p">:</span> <span class="nb">str</span><span class="p">):</span>
     <span class="nb">print</span><span class="p">(</span><span class="sa">f</span><span class="s1">&#39;Hello </span><span class="si">{</span><span class="n">name</span><span class="si">}</span><span class="s1">!&#39;</span><span class="p">)</span>
@@ -739,7 +739,7 @@
 <h2>History<a class="headerlink" href="#history" title="Permalink to this headline">¶</a></h2>
 <p>The TaskFlow API is new as of Airflow 2.0, and you are likely to encounter DAGs written for previous versions of Airflow that instead use <code class="docutils literal notranslate"><span class="pre">PythonOperator</span></code> to achieve similar goals, albeit with a lot more code.</p>
 <p>More context around the addition and design of the TaskFlow API can be found as part of its Airflow Improvement Proposal
-<a class="reference external" href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148638736">AIP-31: “TaskFlow API” for clearer/simpler DAG definition</a></p>
+<a class="reference external" href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148638736">AIP-31: &quot;TaskFlow API&quot; for clearer/simpler DAG definition</a></p>
 </div>
 </div>
 
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/tasks.html b/docs-archive/apache-airflow/2.3.0/concepts/tasks.html
index 6c526fe7c..58648b7fc 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/tasks.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/tasks.html
@@ -725,7 +725,7 @@
 <li><p><a class="reference internal" href="sensors.html"><span class="doc">Sensors</span></a>, a special subclass of Operators which are entirely about waiting for an external event to happen.</p></li>
 <li><p>A <a class="reference internal" href="taskflow.html"><span class="doc">TaskFlow</span></a>-decorated <code class="docutils literal notranslate"><span class="pre">&#64;task</span></code>, which is a custom Python function packaged up as a Task.</p></li>
 </ul>
-<p>Internally, these are all actually subclasses of Airflow’s <code class="docutils literal notranslate"><span class="pre">BaseOperator</span></code>, and the concepts of Task and Operator are somewhat interchangeable, but it’s useful to think of them as separate concepts - essentially, Operators and Sensors are <em>templates</em>, and when you call one in a DAG file, you’re making a Task.</p>
+<p>Internally, these are all actually subclasses of Airflow's <code class="docutils literal notranslate"><span class="pre">BaseOperator</span></code>, and the concepts of Task and Operator are somewhat interchangeable, but it's useful to think of them as separate concepts - essentially, Operators and Sensors are <em>templates</em>, and when you call one in a DAG file, you're making a Task.</p>
 <div class="section" id="relationships">
 <h2>Relationships<a class="headerlink" href="#relationships" title="Permalink to this headline">¶</a></h2>
 <p>The key part of using Tasks is defining how they relate to each other - their <em>dependencies</em>, or as we say in Airflow, their <em>upstream</em> and <em>downstream</em> tasks. You declare your Tasks first, and then you declare their dependencies second.</p>
@@ -746,7 +746,7 @@ Same definition applies to <em>downstream</em> task, which needs to be a direct
 </div>
 <p>These both do exactly the same thing, but in general we recommend you use the bitshift operators, as they are easier to read in most cases.</p>
 <p>By default, a Task will run when all of its upstream (parent) tasks have succeeded, but there are many ways of modifying this behaviour to add branching, to only wait for some upstream tasks, or to change behaviour based on where the current run is in history. For more, see <a class="reference internal" href="dags.html#concepts-control-flow"><span class="std std-ref">Control Flow</span></a>.</p>
-<p>Tasks don’t pass information to each other by default, and run entirely independently. If you want to pass information from one Task to another, you should use <a class="reference internal" href="xcoms.html"><span class="doc">XComs</span></a>.</p>
+<p>Tasks don't pass information to each other by default, and run entirely independently. If you want to pass information from one Task to another, you should use <a class="reference internal" href="xcoms.html"><span class="doc">XComs</span></a>.</p>
 </div>
 <div class="section" id="task-instances">
 <span id="concepts-task-instances"></span><h2>Task Instances<a class="headerlink" href="#task-instances" title="Permalink to this headline">¶</a></h2>
@@ -755,7 +755,7 @@ Same definition applies to <em>downstream</em> task, which needs to be a direct
 <p id="concepts-task-states">The possible states for a Task Instance are:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">none</span></code>: The Task has not yet been queued for execution (its dependencies are not yet met)</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">scheduled</span></code>: The scheduler has determined the Task’s dependencies are met and it should run</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">scheduled</span></code>: The scheduler has determined the Task's dependencies are met and it should run</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">queued</span></code>: The task has been assigned to an Executor and is awaiting a worker</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">running</span></code>: The task is running on a worker (or on a local/synchronous executor)</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">success</span></code>: The task finished running without errors</p></li>
@@ -784,7 +784,7 @@ Same definition applies to <em>downstream</em> task, which needs to be a direct
 <p>There may also be instances of the <em>same task</em>, but for different data intervals - from other runs of the same DAG. We call these <em>previous</em> and <em>next</em> - it is a different relationship to <em>upstream</em> and <em>downstream</em>!</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>Some older Airflow documentation may still use “previous” to mean “upstream”. If you find an occurrence of this, please help us fix it!</p>
+<p>Some older Airflow documentation may still use &quot;previous&quot; to mean &quot;upstream&quot;. If you find an occurrence of this, please help us fix it!</p>
 </div>
 </div>
 </div>
@@ -803,7 +803,7 @@ is periodically executed and rescheduled until it succeeds.</p>
 <li><p>Each time the sensor pokes the SFTP server, it is allowed to take maximum 60 seconds as defined by <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code>.</p></li>
 <li><p>If it takes the sensor more than 60 seconds to poke the SFTP server, <code class="docutils literal notranslate"><span class="pre">AirflowTaskTimeout</span></code> will be raised.
 The sensor is allowed to retry when this happens. It can retry up to 2 times as defined by <code class="docutils literal notranslate"><span class="pre">retries</span></code>.</p></li>
-<li><p>From the start of the first execution, till it eventually succeeds (i.e. after the file ‘root/test’ appears),
+<li><p>From the start of the first execution, till it eventually succeeds (i.e. after the file 'root/test' appears),
 the sensor is allowed maximum 3600 seconds as defined by <code class="docutils literal notranslate"><span class="pre">timeout</span></code>. In other words, if the file
 does not appear on the SFTP server within 3600 seconds, the sensor will raise <code class="docutils literal notranslate"><span class="pre">AirflowSensorTimeout</span></code>.
 It will not retry when this error is raised.</p></li>
@@ -825,10 +825,10 @@ still have up to 3600 seconds in total for it to succeed.</p></li>
 </div>
 <div class="section" id="slas">
 <span id="concepts-slas"></span><h2>SLAs<a class="headerlink" href="#slas" title="Permalink to this headline">¶</a></h2>
-<p>An SLA, or a Service Level Agreement, is an expectation for the maximum time a Task should take. If a task takes longer than this to run, it is then visible in the “SLA Misses” part of the user interface, as well as going out in an email of all tasks that missed their SLA.</p>
+<p>An SLA, or a Service Level Agreement, is an expectation for the maximum time a Task should take. If a task takes longer than this to run, it is then visible in the &quot;SLA Misses&quot; part of the user interface, as well as going out in an email of all tasks that missed their SLA.</p>
 <p>Tasks over their SLA are not cancelled, though - they are allowed to run to completion. If you want to cancel a task after a certain runtime is reached, you want <a class="reference internal" href="#concepts-timeouts"><span class="std std-ref">Timeouts</span></a> instead.</p>
-<p>To set an SLA for a task, pass a <code class="docutils literal notranslate"><span class="pre">datetime.timedelta</span></code> object to the Task/Operator’s <code class="docutils literal notranslate"><span class="pre">sla</span></code> parameter.  You can also supply an <code class="docutils literal notranslate"><span class="pre">sla_miss_callback</span></code> that will be called when the SLA is missed if you want to run your own logic.</p>
-<p>If you want to disable SLA checking entirely, you can set <code class="docutils literal notranslate"><span class="pre">check_slas</span> <span class="pre">=</span> <span class="pre">False</span></code> in Airflow’s <code class="docutils literal notranslate"><span class="pre">[core]</span></code> configuration.</p>
+<p>To set an SLA for a task, pass a <code class="docutils literal notranslate"><span class="pre">datetime.timedelta</span></code> object to the Task/Operator's <code class="docutils literal notranslate"><span class="pre">sla</span></code> parameter.  You can also supply an <code class="docutils literal notranslate"><span class="pre">sla_miss_callback</span></code> that will be called when the SLA is missed if you want to run your own logic.</p>
+<p>If you want to disable SLA checking entirely, you can set <code class="docutils literal notranslate"><span class="pre">check_slas</span> <span class="pre">=</span> <span class="pre">False</span></code> in Airflow's <code class="docutils literal notranslate"><span class="pre">[core]</span></code> configuration.</p>
 <p>To read more about configuring the emails, see <a class="reference internal" href="../howto/email-config.html"><span class="doc">Email Configuration</span></a>.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
@@ -860,7 +860,7 @@ since the last time that the <code class="docutils literal notranslate"><span cl
 <div><ul class="simple">
 <li><p>Any task in the <a class="reference internal" href="../dag-run.html"><span class="doc">DAGRun(s)</span></a> (with the same <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> as a task that missed
 <a class="reference internal" href="#concepts-slas"><span class="std std-ref">SLA</span></a>) that is not in a <strong>SUCCESS</strong> state at the time that the <code class="docutils literal notranslate"><span class="pre">sla_miss_callback</span></code>
-runs. i.e. ‘running’, ‘failed’.  These tasks are described as tasks that are blocking itself or another
+runs. i.e. 'running', 'failed'.  These tasks are described as tasks that are blocking itself or another
 task from completing before its SLA window is complete.</p></li>
 </ul>
 </div></blockquote>
@@ -937,12 +937,12 @@ in the <code class="docutils literal notranslate"><span class="pre">blocking_tas
 </div>
 <div class="section" id="special-exceptions">
 <h2>Special Exceptions<a class="headerlink" href="#special-exceptions" title="Permalink to this headline">¶</a></h2>
-<p>If you want to control your task’s state from within custom Task/Operator code, Airflow provides two special exceptions you can raise:</p>
+<p>If you want to control your task's state from within custom Task/Operator code, Airflow provides two special exceptions you can raise:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">AirflowSkipException</span></code> will mark the current task as skipped</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">AirflowFailException</span></code> will mark the current task as failed <em>ignoring any remaining retry attempts</em></p></li>
 </ul>
-<p>These can be useful if your code has extra knowledge about its environment and wants to fail/skip faster - e.g., skipping when it knows there’s no data available, or fast-failing when it detects its API key is invalid (as that will not be fixed by a retry).</p>
+<p>These can be useful if your code has extra knowledge about its environment and wants to fail/skip faster - e.g., skipping when it knows there's no data available, or fast-failing when it detects its API key is invalid (as that will not be fixed by a retry).</p>
 </div>
 <div class="section" id="zombie-undead-tasks">
 <h2>Zombie/Undead Tasks<a class="headerlink" href="#zombie-undead-tasks" title="Permalink to this headline">¶</a></h2>
@@ -955,7 +955,7 @@ in the <code class="docutils literal notranslate"><span class="pre">blocking_tas
 <div class="section" id="executor-configuration">
 <h2>Executor Configuration<a class="headerlink" href="#executor-configuration" title="Permalink to this headline">¶</a></h2>
 <p>Some <a class="reference internal" href="../executor/index.html"><span class="doc">Executors</span></a> allow optional per-task configuration - such as the <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>, which lets you set an image to run the task on.</p>
-<p>This is achieved via the <code class="docutils literal notranslate"><span class="pre">executor_config</span></code> argument to a Task or Operator. Here’s an example of setting the Docker image for a task that will run on the <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>:</p>
+<p>This is achieved via the <code class="docutils literal notranslate"><span class="pre">executor_config</span></code> argument to a Task or Operator. Here's an example of setting the Docker image for a task that will run on the <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">MyOperator</span><span class="p">(</span><span class="o">...</span><span class="p">,</span>
     <span class="n">executor_config</span><span class="o">=</span><span class="p">{</span>
         <span class="s2">&quot;KubernetesExecutor&quot;</span><span class="p">:</span>
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/timetable.html b/docs-archive/apache-airflow/2.3.0/concepts/timetable.html
index 5a97e14fc..639606cfe 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/timetable.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/timetable.html
@@ -688,8 +688,8 @@
 <div></div></blockquote>
 <div class="section" id="timetables">
 <h1>Timetables<a class="headerlink" href="#timetables" title="Permalink to this headline">¶</a></h1>
-<p>A DAG’s scheduling strategy is determined by its internal “timetable”. This
-timetable can be created by specifying the DAG’s <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> argument,
+<p>A DAG's scheduling strategy is determined by its internal &quot;timetable&quot;. This
+timetable can be created by specifying the DAG's <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> argument,
 as described in <a class="reference internal" href="../dag-run.html"><span class="doc">DAG Run</span></a>, or by passing a <code class="docutils literal notranslate"><span class="pre">timetable</span></code> argument
 directly. The timetable also dictates the data interval and the logical time of each
 run created for the DAG.</p>
@@ -698,7 +698,7 @@ run created for the DAG.</p>
 respectively), however, there are situations where they cannot properly express
 the schedule. Some examples are:</p>
 <ul class="simple">
-<li><p>Data intervals with “holes” between. (Instead of continuous, as both the cron
+<li><p>Data intervals with &quot;holes&quot; between. (Instead of continuous, as both the cron
 expression and <code class="docutils literal notranslate"><span class="pre">timedelta</span></code> schedules represent.)</p></li>
 <li><p>Run tasks at different times each day. For example, an astronomer may find it
 useful to run a task at dawn to process data collected from the previous
@@ -708,7 +708,7 @@ each month in the <a class="reference external" href="https://en.wikipedia.org/w
 similar to the sunset case above, but for a different time scale.</p></li>
 <li><p>Rolling windows, or overlapping data intervals. For example, one may want to
 have a run each day, but make each run cover the period of the previous seven
-days. It is possible to “hack” this with a cron expression, but a custom data
+days. It is possible to &quot;hack&quot; this with a cron expression, but a custom data
 interval would be a more natural representation.</p></li>
 </ul>
 <p>As such, Airflow allows for custom timetables to be written in plugins and used by
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/variables.html b/docs-archive/apache-airflow/2.3.0/concepts/variables.html
index 72ea974e4..a9be8e75f 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/variables.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/variables.html
@@ -688,7 +688,7 @@
 <div></div></blockquote>
 <div class="section" id="variables">
 <h1>Variables<a class="headerlink" href="#variables" title="Permalink to this headline">¶</a></h1>
-<p>Variables are Airflow’s runtime configuration concept - a general key/value store that is global and can be queried from your tasks, and easily set via Airflow’s user interface, or bulk-uploaded as a JSON file.</p>
+<p>Variables are Airflow's runtime configuration concept - a general key/value store that is global and can be queried from your tasks, and easily set via Airflow's user interface, or bulk-uploaded as a JSON file.</p>
 <p>To use them, just import and call <code class="docutils literal notranslate"><span class="pre">get</span></code> on the Variable model:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">airflow.models</span> <span class="kn">import</span> <span class="n">Variable</span>
 
diff --git a/docs-archive/apache-airflow/2.3.0/concepts/xcoms.html b/docs-archive/apache-airflow/2.3.0/concepts/xcoms.html
index 01c29d972..d5e1a96d4 100644
--- a/docs-archive/apache-airflow/2.3.0/concepts/xcoms.html
+++ b/docs-archive/apache-airflow/2.3.0/concepts/xcoms.html
@@ -698,10 +698,10 @@
 <div></div></blockquote>
 <div class="section" id="xcoms">
 <span id="concepts-xcom"></span><h1>XComs<a class="headerlink" href="#xcoms" title="Permalink to this headline">¶</a></h1>
-<p>XComs (short for “cross-communications”) are a mechanism that let <a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> talk to each other, as by default Tasks are entirely isolated and may be running on entirely different machines.</p>
+<p>XComs (short for &quot;cross-communications&quot;) are a mechanism that let <a class="reference internal" href="tasks.html"><span class="doc">Tasks</span></a> talk to each other, as by default Tasks are entirely isolated and may be running on entirely different machines.</p>
 <p>An XCom is identified by a <code class="docutils literal notranslate"><span class="pre">key</span></code> (essentially its name), as well as the <code class="docutils literal notranslate"><span class="pre">task_id</span></code> and <code class="docutils literal notranslate"><span class="pre">dag_id</span></code> it came from. They can have any (serializable) value, but they are only designed for small amounts of data; do not use them to pass around large values, like dataframes.</p>
-<p>XComs are explicitly “pushed” and “pulled” to/from their storage using the <code class="docutils literal notranslate"><span class="pre">xcom_push</span></code> and <code class="docutils literal notranslate"><span class="pre">xcom_pull</span></code> methods on Task Instances. Many operators will auto-push their results into an XCom key called <code class="docutils literal notranslate"><span class="pre">return_value</span></code> if the <code class="docutils literal notranslate"><span c [...]
-<p><code class="docutils literal notranslate"><span class="pre">xcom_pull</span></code> defaults to using this key if no key is passed to it, meaning it’s possible to write code like this:</p>
+<p>XComs are explicitly &quot;pushed&quot; and &quot;pulled&quot; to/from their storage using the <code class="docutils literal notranslate"><span class="pre">xcom_push</span></code> and <code class="docutils literal notranslate"><span class="pre">xcom_pull</span></code> methods on Task Instances. Many operators will auto-push their results into an XCom key called <code class="docutils literal notranslate"><span class="pre">return_value</span></code> if the <code class="docutils literal  [...]
+<p><code class="docutils literal notranslate"><span class="pre">xcom_pull</span></code> defaults to using this key if no key is passed to it, meaning it's possible to write code like this:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># Pulls the return_value XCOM from &quot;pushing_task&quot;</span>
 <span class="n">value</span> <span class="o">=</span> <span class="n">task_instance</span><span class="o">.</span><span class="n">xcom_pull</span><span class="p">(</span><span class="n">task_ids</span><span class="o">=</span><span class="s1">&#39;pushing_task&#39;</span><span class="p">)</span>
 </pre></div>
@@ -731,7 +731,7 @@
 </pre></div>
 </div>
 <p>which will print the actual class that is being used.</p>
-<p>You can also examine Airflow’s configuration:</p>
+<p>You can also examine Airflow's configuration:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">airflow.settings</span> <span class="kn">import</span> <span class="n">conf</span>
 
 <span class="n">conf</span><span class="o">.</span><span class="n">get</span><span class="p">(</span><span class="s2">&quot;core&quot;</span><span class="p">,</span> <span class="s2">&quot;xcom_backend&quot;</span><span class="p">)</span>
diff --git a/docs-archive/apache-airflow/2.3.0/configurations-ref.html b/docs-archive/apache-airflow/2.3.0/configurations-ref.html
index 5ffac467c..40e831aec 100644
--- a/docs-archive/apache-airflow/2.3.0/configurations-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/configurations-ref.html
@@ -1515,7 +1515,7 @@ should be same on the Webserver and Worker to allow Webserver to fetch logs from
 <p>The webserver key is also used to authorize requests to Celery workers when logs are retrieved. The token
 generated using the secret key has a short expiry time though - make sure that time on ALL the machines
 that you run airflow components on is synchronized (for example using ntpd) otherwise you might get
-“forbidden” errors when the logs are accessed.</p>
+&quot;forbidden&quot; errors when the logs are accessed.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>For more information on setting the configuration, see <a class="reference internal" href="howto/set-config.html"><span class="doc">Setting Configuration Options</span></a></p>
@@ -1564,7 +1564,7 @@ that you run airflow components on is synchronized (for example using ntpd) othe
 </div>
 <p>Used in response to a preflight request to indicate which HTTP
 headers can be used when making the actual request. This header is
-the server side response to the browser’s
+the server side response to the browser's
 Access-Control-Request-Headers header.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
@@ -1619,7 +1619,7 @@ Separate URLs with space.</p>
 <span id="config-api-auth-backends"></span><h3>auth_backends<a class="headerlink" href="#auth-backends" title="Permalink to this headline">¶</a></h3>
 <p>Comma separated list of auth backends to authenticate users of the API. See
 <a class="reference external" href="https://airflow.apache.org/docs/apache-airflow/stable/security/api.html">https://airflow.apache.org/docs/apache-airflow/stable/security/api.html</a> for possible values.
-(“airflow.api.auth.backend.default” allows all requests for historic reasons)</p>
+(&quot;airflow.api.auth.backend.default&quot; allows all requests for historic reasons)</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -2136,7 +2136,7 @@ due to <code class="docutils literal notranslate"><span class="pre">AirflowTaskT
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
-<p>Celery task will report its status as ‘started’ when the task is executed by a worker.
+<p>Celery task will report its status as 'started' when the task is executed by a worker.
 This is used in Airflow to keep track of the running tasks and if a Scheduler is restarted
 or run in HA mode, it can adopt the orphan tasks launched by previous SchedulerJob.</p>
 <dl class="field-list simple">
@@ -2199,7 +2199,7 @@ your worker box and the nature of your tasks</p>
 </div>
 <p>Specify if remote control of the workers is enabled.
 When using Amazon SQS as the broker, Celery creates lots of <code class="docutils literal notranslate"><span class="pre">.*reply-celery-pidbox</span></code> queues. You can
-prevent this by setting this to false. However, with this disabled Flower won’t work.</p>
+prevent this by setting this to false. However, with this disabled Flower won't work.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>boolean</p>
@@ -2297,7 +2297,7 @@ underlying celery broker transport. See:
 <p>The visibility timeout defines the number of seconds to wait for the worker
 to acknowledge the task before the message is redelivered to another worker.
 Make sure to increase the visibility timeout to match the time of the longest
-ETA you’re planning to use.
+ETA you're planning to use.
 visibility_timeout is only supported for Redis and SQS celery brokers.
 See:
 <a class="reference external" href="http://docs.celeryproject.org/en/master/userguide/configuration.html#std:setting-broker_transport_options">http://docs.celeryproject.org/en/master/userguide/configuration.html#std:setting-broker_transport_options</a></p>
@@ -2424,7 +2424,7 @@ Note: this will disable the DAG dependencies view</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 1.10.3.</span></p>
 </div>
-<p>When discovering DAGs, ignore any files that don’t contain the strings <code class="docutils literal notranslate"><span class="pre">DAG</span></code> and <code class="docutils literal notranslate"><span class="pre">airflow</span></code>.</p>
+<p>When discovering DAGs, ignore any files that don't contain the strings <code class="docutils literal notranslate"><span class="pre">DAG</span></code> and <code class="docutils literal notranslate"><span class="pre">airflow</span></code>.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -2460,7 +2460,7 @@ Note: this will disable the DAG dependencies view</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.3.0.</span></p>
 </div>
-<p>The pattern syntax used in the “.airflowignore” files in the DAG directories. Valid values are
+<p>The pattern syntax used in the &quot;.airflowignore&quot; files in the DAG directories. Valid values are
 <code class="docutils literal notranslate"><span class="pre">regexp</span></code> or <code class="docutils literal notranslate"><span class="pre">glob</span></code>.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
@@ -2722,8 +2722,8 @@ RCE exploits).</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
-<p>Should tasks be executed via forking of the parent process (“False”,
-the speedier option) or by spawning a new python process (“True” slow,
+<p>Should tasks be executed via forking of the parent process (&quot;False&quot;,
+the speedier option) or by spawning a new python process (&quot;True&quot; slow,
 but means plugin changes picked up by tasks straight away)</p>
 <div class="admonition seealso">
 <p class="admonition-title">See also</p>
@@ -2798,8 +2798,8 @@ full import path to the class when using a custom executor.</p>
 <div class="section" id="hostname-callable">
 <span id="config-core-hostname-callable"></span><h3>hostname_callable<a class="headerlink" href="#hostname-callable" title="Permalink to this headline">¶</a></h3>
 <p>Hostname by providing a path to a callable, which will resolve the hostname.
-The format is “package.function”.</p>
-<p>For example, default value “socket.getfqdn” means that result from getfqdn() of “socket”
+The format is &quot;package.function&quot;.</p>
+<p>For example, default value &quot;socket.getfqdn&quot; means that result from getfqdn() of &quot;socket&quot;
 package will be used as hostname.</p>
 <p>No argument should be required in the function specified.
 If using IP address as hostname is preferred, use value <code class="docutils literal notranslate"><span class="pre">airflow.utils.net.get_host_ip_address</span></code></p>
@@ -2837,7 +2837,7 @@ it has to cleanup after it is sent a SIGTERM, before it is SIGKILLED</p>
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
 <p>By default Airflow providers are lazily-discovered (discovery and imports happen only when required).
-Set it to False, if you want to discover providers whenever ‘airflow’ is invoked via cli or
+Set it to False, if you want to discover providers whenever 'airflow' is invoked via cli or
 loaded from module.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
@@ -2857,7 +2857,7 @@ loaded from module.</p>
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
 <p>By default Airflow plugins are lazily-loaded (only loaded when required). Set it to <code class="docutils literal notranslate"><span class="pre">False</span></code>,
-if you want to load plugins whenever ‘airflow’ is invoked via cli or loaded from module.</p>
+if you want to load plugins whenever 'airflow' is invoked via cli or loaded from module.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>boolean</p>
@@ -2872,7 +2872,7 @@ if you want to load plugins whenever ‘airflow’ is invoked via cli or loaded
 </div>
 <div class="section" id="load-examples">
 <span id="config-core-load-examples"></span><h3>load_examples<a class="headerlink" href="#load-examples" title="Permalink to this headline">¶</a></h3>
-<p>Whether to load the DAG examples that ship with Airflow. It’s good to
+<p>Whether to load the DAG examples that ship with Airflow. It's good to
 get started, but you probably want to set this to <code class="docutils literal notranslate"><span class="pre">False</span></code> in a production
 environment</p>
 <dl class="field-list simple">
@@ -3058,7 +3058,7 @@ the number of task instances with the running state in the metadata database.</p
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.1.0.</span></p>
 </div>
-<p>A comma-separated list of extra sensitive keywords to look for in variables names or connection’s
+<p>A comma-separated list of extra sensitive keywords to look for in variables names or connection's
 extra JSON.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
@@ -3331,7 +3331,7 @@ values at runtime)</p>
 [core] section above</p>
 <div class="section" id="cluster-address">
 <span id="config-dask-cluster-address"></span><h3>cluster_address<a class="headerlink" href="#cluster-address" title="Permalink to this headline">¶</a></h3>
-<p>The IP address and port of the Dask cluster’s scheduler.</p>
+<p>The IP address and port of the Dask cluster's scheduler.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -3395,7 +3395,7 @@ values at runtime)</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.3.0.</span></p>
 </div>
-<p>Whether to load the default connections that ship with Airflow. It’s good to
+<p>Whether to load the default connections that ship with Airflow. It's good to
 get started, but you probably want to set this to <code class="docutils literal notranslate"><span class="pre">False</span></code> in a production
 environment</p>
 <dl class="field-list simple">
@@ -3459,7 +3459,7 @@ More information here:
 <p><span class="versionmodified added">New in version 2.3.0.</span></p>
 </div>
 <p>Import path for connect args in SqlAlchemy. Defaults to an empty dict.
-This is useful when you want to configure db engine args that SqlAlchemy won’t parse
+This is useful when you want to configure db engine args that SqlAlchemy won't parse
 in connection string.
 See <a class="reference external" href="https://docs.sqlalchemy.org/en/13/core/engines.html#sqlalchemy.create_engine.params.connect_args">https://docs.sqlalchemy.org/en/13/core/engines.html#sqlalchemy.create_engine.params.connect_args</a></p>
 <dl class="field-list simple">
@@ -3479,7 +3479,7 @@ See <a class="reference external" href="https://docs.sqlalchemy.org/en/13/core/e
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.3.0.</span></p>
 </div>
-<p>Extra engine specific keyword args passed to SQLAlchemy’s create_engine, as a JSON-encoded value</p>
+<p>Extra engine specific keyword args passed to SQLAlchemy's create_engine, as a JSON-encoded value</p>
 <dl class="field-list">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -3508,7 +3508,7 @@ additional connections will be returned up to this limit.
 When those additional connections are returned to the pool, they are disconnected and discarded.
 It follows then that the total number of simultaneous connections the pool will allow
 is pool_size + max_overflow,
-and the total number of “sleeping” connections the pool will allow is pool_size.
+and the total number of &quot;sleeping&quot; connections the pool will allow is pool_size.
 max_overflow can be set to <code class="docutils literal notranslate"><span class="pre">-1</span></code> to indicate no overflow limit;
 no limit will be placed on the total number of concurrent connections. Defaults to <code class="docutils literal notranslate"><span class="pre">10</span></code>.</p>
 <dl class="field-list simple">
@@ -3547,7 +3547,7 @@ no limit will be placed on the total number of concurrent connections. Defaults
 <p><span class="versionmodified added">New in version 2.3.0.</span></p>
 </div>
 <p>Check connection at the start of each connection pool checkout.
-Typically, this is a simple statement like “SELECT 1”.
+Typically, this is a simple statement like &quot;SELECT 1&quot;.
 More information here:
 <a class="reference external" href="https://docs.sqlalchemy.org/en/13/core/pooling.html#disconnect-handling-pessimistic">https://docs.sqlalchemy.org/en/13/core/pooling.html#disconnect-handling-pessimistic</a></p>
 <dl class="field-list simple">
@@ -4325,7 +4325,7 @@ when idle connection is time-outed on services like cloud load balancers or fire
 <div class="section" id="in-cluster">
 <span id="config-kubernetes-in-cluster"></span><h3>in_cluster<a class="headerlink" href="#in-cluster" title="Permalink to this headline">¶</a></h3>
 <p>Use the service account kubernetes gives to pods to connect to kubernetes cluster.
-It’s intended for clients that expect to be running inside a pod running on kubernetes.
+It's intended for clients that expect to be running inside a pod running on kubernetes.
 It will raise an exception if called from a process not running in a kubernetes environment.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
@@ -4529,7 +4529,7 @@ to a keepalive probe, TCP retransmits the probe after <cite>tcp_keep_intvl</cite
 <p><span class="versionmodified added">New in version 1.10.3.</span></p>
 </div>
 <p>Number of Kubernetes Worker Pod creation calls per scheduler loop.
-Note that the current default of “1” will only launch a single pod
+Note that the current default of &quot;1&quot; will only launch a single pod
 per-heartbeat. It is HIGHLY recommended that users increase this
 number to match the tolerance of their kubernetes cluster for
 better performance.</p>
@@ -4605,7 +4605,7 @@ You may want this higher if you have a very large cluster and/or use <code class
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.2.0.</span></p>
 </div>
-<p>How often in seconds to check for task instances stuck in “queued” status without a pod</p>
+<p>How often in seconds to check for task instances stuck in &quot;queued&quot; status without a pod</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>integer</p>
@@ -4959,11 +4959,11 @@ This class has to be on the python classpath</p>
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
 <p>Storage bucket URL for remote logging
-S3 buckets should start with “s3://”
-Cloudwatch log groups should start with “cloudwatch://”
-GCS buckets should start with “gs://”
-WASB buckets should start with “wasb” just to help Airflow select correct handler
-Stackdriver logs should start with “stackdriver://”</p>
+S3 buckets should start with &quot;s3://&quot;
+Cloudwatch log groups should start with &quot;cloudwatch://&quot;
+GCS buckets should start with &quot;gs://&quot;
+WASB buckets should start with &quot;wasb&quot; just to help Airflow select correct handler
+Stackdriver logs should start with &quot;stackdriver://&quot;</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -5126,7 +5126,7 @@ def func_name(stat_name: str) -&gt; str:</p>
 </div>
 <p>If you want to avoid sending all the available metrics to StatsD,
 you can configure an allow list of prefixes (comma separated) to send only the metrics that
-start with the elements of the list (e.g: “scheduler,executor,dagrun”)</p>
+start with the elements of the list (e.g: &quot;scheduler,executor,dagrun&quot;)</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -5744,7 +5744,7 @@ This defines how many processes will run.</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
-<p>Should the Task supervisor process perform a “mini scheduler” to attempt to schedule more tasks of the
+<p>Should the Task supervisor process perform a &quot;mini scheduler&quot; to attempt to schedule more tasks of the
 same DAG. Leaving this on will mean tasks in the same DAG execute quicker, but might starve out other
 dags in some circumstances</p>
 <dl class="field-list simple">
@@ -5766,7 +5766,7 @@ dags in some circumstances</p>
 </div>
 <p>If the last scheduler heartbeat happened more than scheduler_health_check_threshold
 ago (in seconds), scheduler is considered unhealthy.
-This is used by the health check in the “/health” endpoint</p>
+This is used by the health check in the &quot;/health&quot; endpoint</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -6369,7 +6369,7 @@ smtp server here</p>
 <span id="config-webserver"></span><h2><a class="toc-backref" href="#id34">[webserver]</a><a class="headerlink" href="#webserver" title="Permalink to this headline">¶</a></h2>
 <div class="section" id="access-logfile">
 <span id="config-webserver-access-logfile"></span><h3>access_logfile<a class="headerlink" href="#access-logfile" title="Permalink to this headline">¶</a></h3>
-<p>Log files for the gunicorn webserver. ‘-‘ means log to stderr.</p>
+<p>Log files for the gunicorn webserver. '-' means log to stderr.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -6388,7 +6388,7 @@ smtp server here</p>
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
 <p>Access log format for gunicorn webserver.
-default format is %%(h)s %%(l)s %%(u)s %%(t)s “%%(r)s” %%(s)s %%(b)s “%%(f)s” “%%(a)s”
+default format is %%(h)s %%(l)s %%(u)s %%(t)s &quot;%%(r)s&quot; %%(s)s %%(b)s &quot;%%(f)s&quot; &quot;%%(a)s&quot;
 documentation - <a class="reference external" href="https://docs.gunicorn.org/en/stable/settings.html#access-log-format">https://docs.gunicorn.org/en/stable/settings.html#access-log-format</a></p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
@@ -6658,7 +6658,7 @@ default value of core/default_timezone will be used</p>
 </div>
 <div class="section" id="error-logfile">
 <span id="config-webserver-error-logfile"></span><h3>error_logfile<a class="headerlink" href="#error-logfile" title="Permalink to this headline">¶</a></h3>
-<p>Log files for the gunicorn webserver. ‘-‘ means log to stderr.</p>
+<p>Log files for the gunicorn webserver. '-' means log to stderr.</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -6988,11 +6988,11 @@ then reload the gunicorn.</p>
 <span id="config-webserver-secret-key"></span><h3>secret_key<a class="headerlink" href="#secret-key" title="Permalink to this headline">¶</a></h3>
 <p>Secret key used to run your flask app. It should be as random as possible. However, when running
 more than 1 instances of webserver, make sure all of them use the same <code class="docutils literal notranslate"><span class="pre">secret_key</span></code> otherwise
-one of them will error with “CSRF session token is missing”.
+one of them will error with &quot;CSRF session token is missing&quot;.
 The webserver key is also used to authorize requests to Celery workers when logs are retrieved.
 The token generated using the secret key has a short expiry time though - make sure that time on
 ALL the machines that you run airflow components on is synchronized (for example using ntpd)
-otherwise you might get “forbidden” errors when the logs are accessed.</p>
+otherwise you might get &quot;forbidden&quot; errors when the logs are accessed.</p>
 <dl class="field-list">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -7012,7 +7012,7 @@ otherwise you might get “forbidden” errors when the logs are accessed.</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.2.4.</span></p>
 </div>
-<p>The type of backend used to store web session data, can be ‘database’ or ‘securecookie’</p>
+<p>The type of backend used to store web session data, can be 'database' or 'securecookie'</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
@@ -7052,7 +7052,7 @@ otherwise you might get “forbidden” errors when the logs are accessed.</p>
 <div class="versionadded">
 <p><span class="versionmodified added">New in version 2.0.0.</span></p>
 </div>
-<p>‘Recent Tasks’ stats will show for old DagRuns if set</p>
+<p>'Recent Tasks' stats will show for old DagRuns if set</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>boolean</p>
@@ -7119,7 +7119,7 @@ on webserver startup</p>
 </div>
 <div class="section" id="web-server-master-timeout">
 <span id="config-webserver-web-server-master-timeout"></span><h3>web_server_master_timeout<a class="headerlink" href="#web-server-master-timeout" title="Permalink to this headline">¶</a></h3>
-<p>Number of seconds the webserver waits before killing gunicorn master that doesn’t respond</p>
+<p>Number of seconds the webserver waits before killing gunicorn master that doesn't respond</p>
 <dl class="field-list simple">
 <dt class="field-odd">Type</dt>
 <dd class="field-odd"><p>string</p>
diff --git a/docs-archive/apache-airflow/2.3.0/dag-run.html b/docs-archive/apache-airflow/2.3.0/dag-run.html
index bfb3c7085..ed5005217 100644
--- a/docs-archive/apache-airflow/2.3.0/dag-run.html
+++ b/docs-archive/apache-airflow/2.3.0/dag-run.html
@@ -694,7 +694,7 @@ Each DAG Run is run separately from another, meaning that you can have running D
 <p>A DAG Run status is determined when the execution of the DAG is finished.
 The execution of the DAG depends on its containing tasks and their dependencies.
 The status is assigned to the DAG Run when all of the tasks are in the one of the terminal states (i.e. if there is no possible transition to another state) like <code class="docutils literal notranslate"><span class="pre">success</span></code>, <code class="docutils literal notranslate"><span class="pre">failed</span></code> or <code class="docutils literal notranslate"><span class="pre">skipped</span></code>.
-The DAG Run is having the status assigned based on the so-called “leaf nodes” or simply “leaves”. Leaf nodes are the tasks with no children.</p>
+The DAG Run is having the status assigned based on the so-called &quot;leaf nodes&quot; or simply &quot;leaves&quot;. Leaf nodes are the tasks with no children.</p>
 <p>There are two possible terminal states for the DAG Run:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">success</span></code> if all of the leaf nodes states are either <code class="docutils literal notranslate"><span class="pre">success</span></code> or <code class="docutils literal notranslate"><span class="pre">skipped</span></code>,</p></li>
@@ -703,7 +703,7 @@ The DAG Run is having the status assigned based on the so-called “leaf nodes
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Be careful if some of your tasks have defined some specific <a class="reference external" href="dags.html#trigger-rules">trigger rule</a>.
-These can lead to some unexpected behavior, e.g. if you have a leaf task with trigger rule <cite>“all_done”</cite>, it will be executed regardless of the states of the rest of the tasks and if it will succeed, then the whole DAG Run will also be marked as <code class="docutils literal notranslate"><span class="pre">success</span></code>, even if something failed in the middle.</p>
+These can lead to some unexpected behavior, e.g. if you have a leaf task with trigger rule <cite>&quot;all_done&quot;</cite>, it will be executed regardless of the states of the rest of the tasks and if it will succeed, then the whole DAG Run will also be marked as <code class="docutils literal notranslate"><span class="pre">success</span></code>, even if something failed in the middle.</p>
 </div>
 </div>
 <div class="section" id="cron-presets">
@@ -711,7 +711,7 @@ These can lead to some unexpected behavior, e.g. if you have a leaf task with tr
 <p>Each DAG may or may not have a schedule, which informs how DAG Runs are
 created. <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> is defined as a DAG argument, which can be passed a
 <a class="reference external" href="https://en.wikipedia.org/wiki/Cron#CRON_expression">cron expression</a> as
-a <code class="docutils literal notranslate"><span class="pre">str</span></code>, a <code class="docutils literal notranslate"><span class="pre">datetime.timedelta</span></code> object, or one of the following cron “presets”.</p>
+a <code class="docutils literal notranslate"><span class="pre">str</span></code>, a <code class="docutils literal notranslate"><span class="pre">datetime.timedelta</span></code> object, or one of the following cron &quot;presets&quot;.</p>
 <div class="admonition tip">
 <p class="admonition-title">Tip</p>
 <p>You can use an online editor for CRON expressions such as <a class="reference external" href="https://crontab.guru/">Crontab guru</a></p>
@@ -730,7 +730,7 @@ a <code class="docutils literal notranslate"><span class="pre">str</span></code>
 </thead>
 <tbody>
 <tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">None</span></code></p></td>
-<td><p>Don’t schedule, use for exclusively “externally triggered”
+<td><p>Don't schedule, use for exclusively &quot;externally triggered&quot;
 DAGs</p></td>
 <td></td>
 </tr>
@@ -768,7 +768,7 @@ DAGs</p></td>
 DAG Run entry in the database backend.</p>
 <div class="section" id="data-interval">
 <span id="id1"></span><h3>Data Interval<a class="headerlink" href="#data-interval" title="Permalink to this headline">¶</a></h3>
-<p>Each DAG run in Airflow has an assigned “data interval” that represents the time
+<p>Each DAG run in Airflow has an assigned &quot;data interval&quot; that represents the time
 range it operates in. For a DAG scheduled with <code class="docutils literal notranslate"><span class="pre">&#64;daily</span></code>, for example, each of
 its data interval would start at midnight of each day and end at midnight of the
 next day.</p>
@@ -777,16 +777,16 @@ to ensure the run is able to collect all the data within the time period. In
 other words, a run covering the data period of 2020-01-01 generally does not
 start to run until 2020-01-01 has ended, i.e. after 2020-01-02 00:00:00.</p>
 <p>All dates in Airflow are tied to the data interval concept in some way. The
-“logical date” (also called <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> in Airflow versions prior to 2.2)
+&quot;logical date&quot; (also called <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> in Airflow versions prior to 2.2)
 of a DAG run, for example, denotes the start of the data interval, not when the
 DAG is actually executed.</p>
 <p>Similarly, since the <code class="docutils literal notranslate"><span class="pre">start_date</span></code> argument for the DAG and its tasks points to
-the same logical date, it marks the start of <em>the DAG’s first data interval</em>, not
+the same logical date, it marks the start of <em>the DAG's first data interval</em>, not
 when tasks in the DAG will start running. In other words, a DAG run will only be
 scheduled one interval after <code class="docutils literal notranslate"><span class="pre">start_date</span></code>.</p>
 <div class="admonition tip">
 <p class="admonition-title">Tip</p>
-<p>If <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> is not enough to express your DAG’s schedule,
+<p>If <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> is not enough to express your DAG's schedule,
 logical date, or data interval, see <a class="reference internal" href="concepts/timetable.html"><span class="doc">Timetables</span></a>.
 For more information on <code class="docutils literal notranslate"><span class="pre">logical</span> <span class="pre">date</span></code>, see <a class="reference internal" href="concepts/dags.html#concepts-dag-run"><span class="std std-ref">Running DAGs</span></a> and
 <a class="reference internal" href="faq.html#faq-what-does-execution-date-mean"><span class="std std-ref">What does execution_date mean?</span></a></p>
@@ -860,18 +860,18 @@ Run the below command</p>
 <h3>Re-run Tasks<a class="headerlink" href="#re-run-tasks" title="Permalink to this headline">¶</a></h3>
 <p>Some of the tasks can fail during the scheduled run. Once you have fixed
 the errors after going through the logs, you can re-run the tasks by clearing them for the
-scheduled date. Clearing a task instance doesn’t delete the task instance record.
+scheduled date. Clearing a task instance doesn't delete the task instance record.
 Instead, it updates <code class="docutils literal notranslate"><span class="pre">max_tries</span></code> to <code class="docutils literal notranslate"><span class="pre">0</span></code> and sets the current task instance state to <code class="docutils literal notranslate"><span class="pre">None</span></code>, which causes the task to re-run.</p>
 <p>Click on the failed task in the Tree or Graph views and then click on <strong>Clear</strong>.
 The executor will re-run it.</p>
 <p>There are multiple options you can select to re-run -</p>
 <ul class="simple">
-<li><p><strong>Past</strong> - All the instances of the task in the runs before the DAG’s most recent data interval</p></li>
-<li><p><strong>Future</strong> -  All the instances of the task in the runs after the DAG’s most recent data interval</p></li>
+<li><p><strong>Past</strong> - All the instances of the task in the runs before the DAG's most recent data interval</p></li>
+<li><p><strong>Future</strong> -  All the instances of the task in the runs after the DAG's most recent data interval</p></li>
 <li><p><strong>Upstream</strong> - The upstream tasks in the current DAG</p></li>
 <li><p><strong>Downstream</strong> - The downstream tasks in the current DAG</p></li>
 <li><p><strong>Recursive</strong> - All the tasks in the child DAGs and parent DAGs</p></li>
-<li><p><strong>Failed</strong> - Only the failed tasks in the DAG’s most recent run</p></li>
+<li><p><strong>Failed</strong> - Only the failed tasks in the DAG's most recent run</p></li>
 </ul>
 <p>You can also clear the task through CLI using the command:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>airflow tasks clear dag_id <span class="se">\</span>
diff --git a/docs-archive/apache-airflow/2.3.0/dag-serialization.html b/docs-archive/apache-airflow/2.3.0/dag-serialization.html
index 732debfd5..a8bb76b3a 100644
--- a/docs-archive/apache-airflow/2.3.0/dag-serialization.html
+++ b/docs-archive/apache-airflow/2.3.0/dag-serialization.html
@@ -714,7 +714,7 @@ It is useful when there are very large DAGs in your cluster. When <code class="d
 <h2>Limitations<a class="headerlink" href="#limitations" title="Permalink to this headline">¶</a></h2>
 <ul class="simple">
 <li><p>When using user-defined filters and macros, the Rendered View in the Webserver might show incorrect results
-for TIs that have not yet executed as it might be using external modules that the Webserver won’t have access to.
+for TIs that have not yet executed as it might be using external modules that the Webserver won't have access to.
 Use <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">tasks</span> <span class="pre">render</span></code> CLI command in such situation to debug or test rendering of your template_fields.
 Once the tasks execution starts the Rendered Template Fields will be stored in the DB in a separate table and
 after which the correct values would be showed in the Webserver (Rendered View tab).</p></li>
diff --git a/docs-archive/apache-airflow/2.3.0/deprecated-rest-api-ref.html b/docs-archive/apache-airflow/2.3.0/deprecated-rest-api-ref.html
index 33cd215ed..9a85714d1 100644
--- a/docs-archive/apache-airflow/2.3.0/deprecated-rest-api-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/deprecated-rest-api-ref.html
@@ -685,7 +685,7 @@
 <p>This REST API is deprecated since version 2.0. Please consider using the <a class="reference internal" href="stable-rest-api-ref.html"><span class="doc">stable REST API</span></a>.
 For more information on migration, see <a class="reference external" href="https://github.com/apache/airflow/blob/main/UPDATING.md">UPDATING.md</a></p>
 </div>
-<p>Before Airflow 2.0 this REST API was known as the “experimental” API, but now that the <a class="reference internal" href="stable-rest-api-ref.html"><span class="doc">stable REST API</span></a> is available, it has been renamed.</p>
+<p>Before Airflow 2.0 this REST API was known as the &quot;experimental&quot; API, but now that the <a class="reference internal" href="stable-rest-api-ref.html"><span class="doc">stable REST API</span></a> is available, it has been renamed.</p>
 <p>The endpoints for this API are available at <code class="docutils literal notranslate"><span class="pre">/api/experimental/</span></code>.</p>
 <div class="versionchanged">
 <p><span class="versionmodified changed">Changed in version 2.0: </span>This REST API is disabled by default. To restore these APIs while migrating to
@@ -727,13 +727,13 @@ In order to create multiple DagRun within one second, you should set parameter <
 <dl class="http get">
 <dt class="sig sig-object http" id="get--api-experimental-dags--string-dag_id--dag_runs--string-execution_date-">
 <span class="sig-name descname"><span class="pre">GET</span> </span><span class="sig-name descname"><span class="pre">/api/experimental/dags/&lt;string:dag_id&gt;/dag_runs/&lt;string:execution_date&gt;</span></span><a class="headerlink" href="#get--api-experimental-dags--string-dag_id--dag_runs--string-execution_date-" title="Permalink to this definition">¶</a></dt>
-<dd><p>Returns a JSON with a dag_run’s public instance variables. The format for the <code class="docutils literal notranslate"><span class="pre">&lt;string:execution_date&gt;</span></code> is expected to be <code class="docutils literal notranslate"><span class="pre">YYYY-mm-DDTHH:MM:SS</span></code>, for example: <code class="docutils literal notranslate"><span class="pre">&quot;2016-11-16T11:34:15&quot;</span></code>.</p>
+<dd><p>Returns a JSON with a dag_run's public instance variables. The format for the <code class="docutils literal notranslate"><span class="pre">&lt;string:execution_date&gt;</span></code> is expected to be <code class="docutils literal notranslate"><span class="pre">YYYY-mm-DDTHH:MM:SS</span></code>, for example: <code class="docutils literal notranslate"><span class="pre">&quot;2016-11-16T11:34:15&quot;</span></code>.</p>
 </dd></dl>
 
 <dl class="http get">
 <dt class="sig sig-object http" id="get--api-experimental-test">
 <span class="sig-name descname"><span class="pre">GET</span> </span><span class="sig-name descname"><span class="pre">/api/experimental/test</span></span><a class="headerlink" href="#get--api-experimental-test" title="Permalink to this definition">¶</a></dt>
-<dd><p>To check REST API server correct work. Return status ‘OK’.</p>
+<dd><p>To check REST API server correct work. Return status 'OK'.</p>
 </dd></dl>
 
 <dl class="http get">
@@ -745,13 +745,13 @@ In order to create multiple DagRun within one second, you should set parameter <
 <dl class="http get">
 <dt class="sig sig-object http" id="get--api-experimental-dags--DAG_ID--dag_runs--string-execution_date--tasks--TASK_ID-">
 <span class="sig-name descname"><span class="pre">GET</span> </span><span class="sig-name descname"><span class="pre">/api/experimental/dags/&lt;DAG_ID&gt;/dag_runs/&lt;string:execution_date&gt;/tasks/&lt;TASK_ID&gt;</span></span><a class="headerlink" href="#get--api-experimental-dags--DAG_ID--dag_runs--string-execution_date--tasks--TASK_ID-" title="Permalink to this definition">¶</a></dt>
-<dd><p>Returns a JSON with a task instance’s public instance variables. The format for the <code class="docutils literal notranslate"><span class="pre">&lt;string:execution_date&gt;</span></code> is expected to be <code class="docutils literal notranslate"><span class="pre">YYYY-mm-DDTHH:MM:SS</span></code>, for example: <code class="docutils literal notranslate"><span class="pre">&quot;2016-11-16T11:34:15&quot;</span></code>.</p>
+<dd><p>Returns a JSON with a task instance's public instance variables. The format for the <code class="docutils literal notranslate"><span class="pre">&lt;string:execution_date&gt;</span></code> is expected to be <code class="docutils literal notranslate"><span class="pre">YYYY-mm-DDTHH:MM:SS</span></code>, for example: <code class="docutils literal notranslate"><span class="pre">&quot;2016-11-16T11:34:15&quot;</span></code>.</p>
 </dd></dl>
 
 <dl class="http get">
 <dt class="sig sig-object http" id="get--api-experimental-dags--DAG_ID--paused--string-paused-">
 <span class="sig-name descname"><span class="pre">GET</span> </span><span class="sig-name descname"><span class="pre">/api/experimental/dags/&lt;DAG_ID&gt;/paused/&lt;string:paused&gt;</span></span><a class="headerlink" href="#get--api-experimental-dags--DAG_ID--paused--string-paused-" title="Permalink to this definition">¶</a></dt>
-<dd><p>‘&lt;string:paused&gt;’ must be a ‘true’ to pause a DAG and ‘false’ to unpause.</p>
+<dd><p>'&lt;string:paused&gt;' must be a 'true' to pause a DAG and 'false' to unpause.</p>
 </dd></dl>
 
 <dl class="http get">
diff --git a/docs-archive/apache-airflow/2.3.0/executor/celery.html b/docs-archive/apache-airflow/2.3.0/executor/celery.html
index b9a3abdf8..13dfee8fb 100644
--- a/docs-archive/apache-airflow/2.3.0/executor/celery.html
+++ b/docs-archive/apache-airflow/2.3.0/executor/celery.html
@@ -683,7 +683,7 @@
 <div class="section" id="celery-executor">
 <span id="executor-celeryexecutor"></span><h1>Celery Executor<a class="headerlink" href="#celery-executor" title="Permalink to this headline">¶</a></h1>
 <p><code class="docutils literal notranslate"><span class="pre">CeleryExecutor</span></code> is one of the ways you can scale out the number of workers. For this
-to work, you need to setup a Celery backend (<strong>RabbitMQ</strong>, <strong>Redis</strong>, …) and
+to work, you need to setup a Celery backend (<strong>RabbitMQ</strong>, <strong>Redis</strong>, ...) and
 change your <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> to point the executor parameter to
 <code class="docutils literal notranslate"><span class="pre">CeleryExecutor</span></code> and provide the related Celery settings.</p>
 <p>For more information about setting up a Celery broker, refer to the
@@ -791,17 +791,17 @@ to start a Flower web server:</p>
 </ul>
 <p>The components communicate with each other in many places</p>
 <ul class="simple">
-<li><p>[1] <strong>Web server</strong> –&gt; <strong>Workers</strong> - Fetches task execution logs</p></li>
-<li><p>[2] <strong>Web server</strong> –&gt; <strong>DAG files</strong> - Reveal the DAG structure</p></li>
-<li><p>[3] <strong>Web server</strong> –&gt; <strong>Database</strong> - Fetch the status of the tasks</p></li>
-<li><p>[4] <strong>Workers</strong> –&gt; <strong>DAG files</strong> - Reveal the DAG structure and execute the tasks</p></li>
-<li><p>[5] <strong>Workers</strong> –&gt; <strong>Database</strong> - Gets and stores information about connection configuration, variables and XCOM.</p></li>
-<li><p>[6] <strong>Workers</strong> –&gt; <strong>Celery’s result backend</strong> - Saves the status of tasks</p></li>
-<li><p>[7] <strong>Workers</strong> –&gt; <strong>Celery’s broker</strong> - Stores commands for execution</p></li>
-<li><p>[8] <strong>Scheduler</strong> –&gt; <strong>DAG files</strong> - Reveal the DAG structure and execute the tasks</p></li>
-<li><p>[9] <strong>Scheduler</strong> –&gt; <strong>Database</strong> - Store a DAG run and related tasks</p></li>
-<li><p>[10] <strong>Scheduler</strong> –&gt; <strong>Celery’s result backend</strong> - Gets information about the status of completed tasks</p></li>
-<li><p>[11] <strong>Scheduler</strong> –&gt; <strong>Celery’s broker</strong> - Put the commands to be executed</p></li>
+<li><p>[1] <strong>Web server</strong> --&gt; <strong>Workers</strong> - Fetches task execution logs</p></li>
+<li><p>[2] <strong>Web server</strong> --&gt; <strong>DAG files</strong> - Reveal the DAG structure</p></li>
+<li><p>[3] <strong>Web server</strong> --&gt; <strong>Database</strong> - Fetch the status of the tasks</p></li>
+<li><p>[4] <strong>Workers</strong> --&gt; <strong>DAG files</strong> - Reveal the DAG structure and execute the tasks</p></li>
+<li><p>[5] <strong>Workers</strong> --&gt; <strong>Database</strong> - Gets and stores information about connection configuration, variables and XCOM.</p></li>
+<li><p>[6] <strong>Workers</strong> --&gt; <strong>Celery's result backend</strong> - Saves the status of tasks</p></li>
+<li><p>[7] <strong>Workers</strong> --&gt; <strong>Celery's broker</strong> - Stores commands for execution</p></li>
+<li><p>[8] <strong>Scheduler</strong> --&gt; <strong>DAG files</strong> - Reveal the DAG structure and execute the tasks</p></li>
+<li><p>[9] <strong>Scheduler</strong> --&gt; <strong>Database</strong> - Store a DAG run and related tasks</p></li>
+<li><p>[10] <strong>Scheduler</strong> --&gt; <strong>Celery's result backend</strong> - Gets information about the status of completed tasks</p></li>
+<li><p>[11] <strong>Scheduler</strong> --&gt; <strong>Celery's broker</strong> - Put the commands to be executed</p></li>
 </ul>
 </div>
 <div class="section" id="task-execution-process">
@@ -844,7 +844,7 @@ to start a Flower web server:</p>
 <p>When using the CeleryExecutor, the Celery queues that tasks are sent to
 can be specified. <code class="docutils literal notranslate"><span class="pre">queue</span></code> is an attribute of BaseOperator, so any
 task can be assigned to any queue. The default queue for the environment
-is defined in the <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>’s <code class="docutils literal notranslate"><span class="pre">operators</span> <span class="pre">-&gt;</span> <span class="pre">default_queue</span></code>. This defines
+is defined in the <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>'s <code class="docutils literal notranslate"><span class="pre">operators</span> <span class="pre">-&gt;</span> <span class="pre">default_queue</span></code>. This defines
 the queue that tasks get assigned to when not specified, as well as which
 queue Airflow workers listen to when started.</p>
 <p>Workers can listen to one or multiple queues of tasks. When a worker is
diff --git a/docs-archive/apache-airflow/2.3.0/executor/celery_kubernetes.html b/docs-archive/apache-airflow/2.3.0/executor/celery_kubernetes.html
index a8d614f45..45a150ef5 100644
--- a/docs-archive/apache-airflow/2.3.0/executor/celery_kubernetes.html
+++ b/docs-archive/apache-airflow/2.3.0/executor/celery_kubernetes.html
@@ -680,7 +680,7 @@
 <span id="executor-celerykubernetesexecutor"></span><h1>CeleryKubernetes Executor<a class="headerlink" href="#celerykubernetes-executor" title="Permalink to this headline">¶</a></h1>
 <p>The <a class="reference internal" href="../_api/airflow/executors/celery_kubernetes_executor/index.html#airflow.executors.celery_kubernetes_executor.CeleryKubernetesExecutor" title="airflow.executors.celery_kubernetes_executor.CeleryKubernetesExecutor"><code class="xref py py-class docutils literal notranslate"><span class="pre">CeleryKubernetesExecutor</span></code></a> allows users
 to run simultaneously a <code class="docutils literal notranslate"><span class="pre">CeleryExecutor</span></code> and a <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>.
-An executor is chosen to run a task based on the task’s queue.</p>
+An executor is chosen to run a task based on the task's queue.</p>
 <p><code class="docutils literal notranslate"><span class="pre">CeleryKubernetesExecutor</span></code> inherits the scalability of the <code class="docutils literal notranslate"><span class="pre">CeleryExecutor</span></code> to
 handle the high load at the peak time and runtime isolation of the <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>.</p>
 <div class="section" id="when-to-use-celerykubernetesexecutor">
diff --git a/docs-archive/apache-airflow/2.3.0/executor/index.html b/docs-archive/apache-airflow/2.3.0/executor/index.html
index ad2f042be..f48991995 100644
--- a/docs-archive/apache-airflow/2.3.0/executor/index.html
+++ b/docs-archive/apache-airflow/2.3.0/executor/index.html
@@ -670,7 +670,7 @@
 <div></div></blockquote>
 <div class="section" id="executor">
 <h1>Executor<a class="headerlink" href="#executor" title="Permalink to this headline">¶</a></h1>
-<p>Executors are the mechanism by which <a class="reference internal" href="../concepts/tasks.html"><span class="doc">task instances</span></a> get run. They have a common API and are “pluggable”, meaning you can swap executors based on your installation needs.</p>
+<p>Executors are the mechanism by which <a class="reference internal" href="../concepts/tasks.html"><span class="doc">task instances</span></a> get run. They have a common API and are &quot;pluggable&quot;, meaning you can swap executors based on your installation needs.</p>
 <p>Airflow can only have one executor configured at a time; this is set by the <code class="docutils literal notranslate"><span class="pre">executor</span></code> option in the <code class="docutils literal notranslate"><span class="pre">[core]</span></code>
 section of <a class="reference internal" href="../howto/set-config.html"><span class="doc">the configuration file</span></a>.</p>
 <p>Built-in executors are referred to by name, for example:</p>
@@ -685,7 +685,7 @@ section of <a class="reference internal" href="../howto/set-config.html"><span c
 </div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>For more information on Airflow’s configuration, see <a class="reference internal" href="../howto/set-config.html"><span class="doc">Setting Configuration Options</span></a>.</p>
+<p>For more information on Airflow's configuration, see <a class="reference internal" href="../howto/set-config.html"><span class="doc">Setting Configuration Options</span></a>.</p>
 </div>
 <p>If you want to check which executor is currently set, you can use the <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">config</span> <span class="pre">get-value</span> <span class="pre">core</span> <span class="pre">executor</span></code> command:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$ airflow config get-value core executor
@@ -715,7 +715,7 @@ SequentialExecutor
 </div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>Something that often confuses new users of Airflow is that they don’t need to run a separate <code class="docutils literal notranslate"><span class="pre">executor</span></code> process. This is because the executor’s logic runs <em>inside</em> the <code class="docutils literal notranslate"><span class="pre">scheduler</span></code> process - if you’re running a scheduler, you’re running the executor.</p>
+<p>Something that often confuses new users of Airflow is that they don't need to run a separate <code class="docutils literal notranslate"><span class="pre">executor</span></code> process. This is because the executor's logic runs <em>inside</em> the <code class="docutils literal notranslate"><span class="pre">scheduler</span></code> process - if you're running a scheduler, you're running the executor.</p>
 </div>
 </div>
 </div>
diff --git a/docs-archive/apache-airflow/2.3.0/executor/kubernetes.html b/docs-archive/apache-airflow/2.3.0/executor/kubernetes.html
index d338d97c1..1677fd851 100644
--- a/docs-archive/apache-airflow/2.3.0/executor/kubernetes.html
+++ b/docs-archive/apache-airflow/2.3.0/executor/kubernetes.html
@@ -743,7 +743,7 @@ configuration; but it must be present in the template file and must not be blank
 </div>
 <div class="section" id="pod-name">
 <h4>Pod name<a class="headerlink" href="#pod-name" title="Permalink to this headline">¶</a></h4>
-<p>The pod’s <code class="docutils literal notranslate"><span class="pre">metadata.name</span></code> must be set in the template file.  This field will <em>always</em> be set dynamically at
+<p>The pod's <code class="docutils literal notranslate"><span class="pre">metadata.name</span></code> must be set in the template file.  This field will <em>always</em> be set dynamically at
 pod launch to guarantee uniqueness across all pods. But again, it must be included in the template, and cannot
 be left blank.</p>
 </div>
@@ -1097,7 +1097,7 @@ This will replace the default <code class="docutils literal notranslate"><span c
 </div></blockquote>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>If you don’t enable logging persistence, and if you have not enabled remote logging, logs will be lost after the worker pods shut down.</p>
+<p>If you don't enable logging persistence, and if you have not enabled remote logging, logs will be lost after the worker pods shut down.</p>
 </div>
 </div>
 </div>
@@ -1117,7 +1117,7 @@ the task will keep running until it completes (or times out, etc). But with Cele
 task will only keep running up until the grace period has elapsed, at which time the task will be terminated.  Another scenario where
 KubernetesExecutor can work well is when your tasks are not very uniform with respect to resource requirements or images.</p>
 <p>Finally, note that it does not have to be either-or; with CeleryKubernetesExecutor, it is possible to use both CeleryExecutor and
-KubernetesExecutor simultaneously on the same cluster. CeleryKubernetesExecutor will look at a task’s <code class="docutils literal notranslate"><span class="pre">queue</span></code> to determine
+KubernetesExecutor simultaneously on the same cluster. CeleryKubernetesExecutor will look at a task's <code class="docutils literal notranslate"><span class="pre">queue</span></code> to determine
 whether to run on Celery or Kubernetes.  By default, tasks are sent to Celery workers, but if you want a task to run using KubernetesExecutor,
 you send it to the  <code class="docutils literal notranslate"><span class="pre">kubernetes</span></code> queue and it will run in its own pod.  And KubernetesPodOperator can be used
 to similar effect, no matter what executor you are using.</p>
@@ -1134,13 +1134,13 @@ This command generates the pods as they will be launched in Kubernetes and dumps
 <p>When dealing with distributed systems, we need a system that assumes that any component can crash at any moment for reasons ranging from OOM errors to node upgrades.</p>
 <p>In the case where a worker dies before it can report its status to the backend DB, the executor can use a Kubernetes watcher thread to discover the failed pod.</p>
 <img alt="../_images/k8s-failed-pod.png" src="../_images/k8s-failed-pod.png" />
-<p>A Kubernetes watcher is a thread that can subscribe to every change that occurs in Kubernetes’ database. It is alerted when pods start, run, end, and fail.
+<p>A Kubernetes watcher is a thread that can subscribe to every change that occurs in Kubernetes' database. It is alerted when pods start, run, end, and fail.
 By monitoring this stream, the KubernetesExecutor can discover that the worker crashed and correctly report the task as failed.</p>
 </div>
 <div class="section" id="but-what-about-cases-where-the-scheduler-pod-crashes">
 <h3>But What About Cases Where the Scheduler Pod Crashes?<a class="headerlink" href="#but-what-about-cases-where-the-scheduler-pod-crashes" title="Permalink to this headline">¶</a></h3>
-<p>In cases of scheduler crashes, the scheduler will recover its state using the watcher’s <code class="docutils literal notranslate"><span class="pre">resourceVersion</span></code>.</p>
-<p>When monitoring the Kubernetes cluster’s watcher thread, each event has a monotonically rising number called a <code class="docutils literal notranslate"><span class="pre">resourceVersion</span></code>.
+<p>In cases of scheduler crashes, the scheduler will recover its state using the watcher's <code class="docutils literal notranslate"><span class="pre">resourceVersion</span></code>.</p>
+<p>When monitoring the Kubernetes cluster's watcher thread, each event has a monotonically rising number called a <code class="docutils literal notranslate"><span class="pre">resourceVersion</span></code>.
 Every time the executor reads a <code class="docutils literal notranslate"><span class="pre">resourceVersion</span></code>, the executor stores the latest value in the backend database.
 Because the resourceVersion is stored, the scheduler can restart and continue reading the watcher stream from where it left off.
 Since the tasks are run independently of the executor and report results directly to the database, scheduler failures will not lead to task failures or re-runs.</p>
diff --git a/docs-archive/apache-airflow/2.3.0/executor/local_kubernetes.html b/docs-archive/apache-airflow/2.3.0/executor/local_kubernetes.html
index 9986e912d..c71610b4f 100644
--- a/docs-archive/apache-airflow/2.3.0/executor/local_kubernetes.html
+++ b/docs-archive/apache-airflow/2.3.0/executor/local_kubernetes.html
@@ -674,7 +674,7 @@
 <span id="executor-localkubernetesexecutor"></span><h1>LocalKubernetes Executor<a class="headerlink" href="#localkubernetes-executor" title="Permalink to this headline">¶</a></h1>
 <p>The <a class="reference internal" href="../_api/airflow/executors/local_kubernetes_executor/index.html#airflow.executors.local_kubernetes_executor.LocalKubernetesExecutor" title="airflow.executors.local_kubernetes_executor.LocalKubernetesExecutor"><code class="xref py py-class docutils literal notranslate"><span class="pre">LocalKubernetesExecutor</span></code></a> allows users
 to simultaneously run a <code class="docutils literal notranslate"><span class="pre">LocalExecutor</span></code> and a <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>.
-An executor is chosen to run a task based on the task’s queue.</p>
+An executor is chosen to run a task based on the task's queue.</p>
 <p><code class="docutils literal notranslate"><span class="pre">LocalKubernetesExecutor</span></code> provides the capability of running tasks with either <code class="docutils literal notranslate"><span class="pre">LocalExecutor</span></code>,
 which runs tasks within the scheduler service, or with <code class="docutils literal notranslate"><span class="pre">KubernetesExecutor</span></code>, which runs each task
 in its own pod on a kubernetes cluster.</p>
diff --git a/docs-archive/apache-airflow/2.3.0/executor/sequential.html b/docs-archive/apache-airflow/2.3.0/executor/sequential.html
index 9826df9ec..dee58f04e 100644
--- a/docs-archive/apache-airflow/2.3.0/executor/sequential.html
+++ b/docs-archive/apache-airflow/2.3.0/executor/sequential.html
@@ -673,7 +673,7 @@
 <div class="section" id="sequential-executor">
 <span id="executor-sequentialexecutor"></span><h1>Sequential Executor<a class="headerlink" href="#sequential-executor" title="Permalink to this headline">¶</a></h1>
 <p>The <a class="reference internal" href="../_api/airflow/executors/sequential_executor/index.html#airflow.executors.sequential_executor.SequentialExecutor" title="airflow.executors.sequential_executor.SequentialExecutor"><code class="xref py py-class docutils literal notranslate"><span class="pre">SequentialExecutor</span></code></a> is the default executor when you first install <code class="docutils literal notranslate"><span class="pre">airflow</span></code>.
-It is the only executor that can be used with <code class="docutils literal notranslate"><span class="pre">sqlite</span></code> since <code class="docutils literal notranslate"><span class="pre">sqlite</span></code> doesn’t support multiple connections.
+It is the only executor that can be used with <code class="docutils literal notranslate"><span class="pre">sqlite</span></code> since <code class="docutils literal notranslate"><span class="pre">sqlite</span></code> doesn't support multiple connections.
 This executor will only run one task instance at a time. For production use case, please use other executors.</p>
 </div>
 
diff --git a/docs-archive/apache-airflow/2.3.0/extra-packages-ref.html b/docs-archive/apache-airflow/2.3.0/extra-packages-ref.html
index 801016e32..e71808a65 100644
--- a/docs-archive/apache-airflow/2.3.0/extra-packages-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/extra-packages-ref.html
@@ -668,7 +668,7 @@
 <div></div></blockquote>
 <div class="section" id="reference-for-package-extras">
 <h1>Reference for package extras<a class="headerlink" href="#reference-for-package-extras" title="Permalink to this headline">¶</a></h1>
-<p>Here’s the list of all the extra dependencies of Apache Airflow.</p>
+<p>Here's the list of all the extra dependencies of Apache Airflow.</p>
 <p>The entries with <code class="docutils literal notranslate"><span class="pre">*</span></code> in the <code class="docutils literal notranslate"><span class="pre">Preinstalled</span></code> column indicate that those extras (providers) are always
 pre-installed when Airflow is installed.</p>
 <div class="admonition note">
@@ -772,7 +772,7 @@ python dependencies for the provided package.</p>
 <h2>Providers extras<a class="headerlink" href="#providers-extras" title="Permalink to this headline">¶</a></h2>
 <p>Those providers extras are simply convenience extras to install provider packages so that you can install the providers with simple command - including
 provider package and necessary dependencies in single command, which allows PIP to resolve any conflicting dependencies. This is extremely useful
-for first time installation where you want to repeatably install version of dependencies which are ‘valid’ for both airflow and providers installed.</p>
+for first time installation where you want to repeatably install version of dependencies which are 'valid' for both airflow and providers installed.</p>
 <p>For example the below command will install:</p>
 <blockquote>
 <div><ul class="simple">
diff --git a/docs-archive/apache-airflow/2.3.0/faq.html b/docs-archive/apache-airflow/2.3.0/faq.html
index 3a8488039..c9fbfc420 100644
--- a/docs-archive/apache-airflow/2.3.0/faq.html
+++ b/docs-archive/apache-airflow/2.3.0/faq.html
@@ -360,13 +360,13 @@
 <li class="toctree-l3"><a class="reference internal" href="#why-is-task-not-getting-scheduled">Why is task not getting scheduled?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-improve-dag-performance">How to improve DAG performance?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-reduce-dag-scheduling-latency-task-delay">How to reduce DAG scheduling latency / task delay?</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure">How do I trigger tasks based on another task’s failure?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure">How do I trigger tasks based on another task's failure?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-control-dag-file-parsing-timeout-for-different-dag-files">How to control DAG file parsing timeout for different DAG files?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#when-there-are-a-lot-1000-of-dags-files-how-to-speed-up-parsing-of-new-files">When there are a lot (&gt;1000) of dags files, how to speed up parsing of new files?</a></li>
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#dag-construction">DAG construction</a><ul>
-<li class="toctree-l3"><a class="reference internal" href="#what-s-the-deal-with-start-date">What’s the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#what-s-the-deal-with-start-date">What's the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#using-time-zones">Using time zones</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#what-does-execution-date-mean">What does <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> mean?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-create-dags-dynamically">How to create DAGs dynamically?</a></li>
@@ -377,7 +377,7 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#task-execution-interactions">Task execution interactions</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#what-does-templatenotfound-mean">What does <code class="docutils literal notranslate"><span class="pre">TemplateNotFound</span></code> mean?</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#how-to-trigger-tasks-based-on-another-task-s-failure">How to trigger tasks based on another task’s failure?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#how-to-trigger-tasks-based-on-another-task-s-failure">How to trigger tasks based on another task's failure?</a></li>
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#airflow-ui">Airflow UI</a><ul>
@@ -387,7 +387,7 @@
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#mysql-and-mysql-variant-databases">MySQL and MySQL variant Databases</a><ul>
-<li class="toctree-l3"><a class="reference internal" href="#what-does-mysql-server-has-gone-away-mean">What does “MySQL Server has gone away” mean?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#what-does-mysql-server-has-gone-away-mean">What does &quot;MySQL Server has gone away&quot; mean?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#does-airflow-support-extended-ascii-or-unicode-characters">Does Airflow support extended ASCII or unicode characters?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-fix-exception-global-variable-explicit-defaults-for-timestamp-needs-to-be-on-1">How to fix Exception: Global variable <code class="docutils literal notranslate"><span class="pre">explicit_defaults_for_timestamp</span></code> needs to be on (1)?</a></li>
 </ul>
@@ -566,13 +566,13 @@
 <li class="toctree-l3"><a class="reference internal" href="#why-is-task-not-getting-scheduled">Why is task not getting scheduled?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-improve-dag-performance">How to improve DAG performance?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-reduce-dag-scheduling-latency-task-delay">How to reduce DAG scheduling latency / task delay?</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure">How do I trigger tasks based on another task’s failure?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure">How do I trigger tasks based on another task's failure?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-control-dag-file-parsing-timeout-for-different-dag-files">How to control DAG file parsing timeout for different DAG files?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#when-there-are-a-lot-1000-of-dags-files-how-to-speed-up-parsing-of-new-files">When there are a lot (&gt;1000) of dags files, how to speed up parsing of new files?</a></li>
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#dag-construction">DAG construction</a><ul>
-<li class="toctree-l3"><a class="reference internal" href="#what-s-the-deal-with-start-date">What’s the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#what-s-the-deal-with-start-date">What's the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#using-time-zones">Using time zones</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#what-does-execution-date-mean">What does <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> mean?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-create-dags-dynamically">How to create DAGs dynamically?</a></li>
@@ -583,7 +583,7 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#task-execution-interactions">Task execution interactions</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#what-does-templatenotfound-mean">What does <code class="docutils literal notranslate"><span class="pre">TemplateNotFound</span></code> mean?</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#how-to-trigger-tasks-based-on-another-task-s-failure">How to trigger tasks based on another task’s failure?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#how-to-trigger-tasks-based-on-another-task-s-failure">How to trigger tasks based on another task's failure?</a></li>
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#airflow-ui">Airflow UI</a><ul>
@@ -593,7 +593,7 @@
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#mysql-and-mysql-variant-databases">MySQL and MySQL variant Databases</a><ul>
-<li class="toctree-l3"><a class="reference internal" href="#what-does-mysql-server-has-gone-away-mean">What does “MySQL Server has gone away” mean?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#what-does-mysql-server-has-gone-away-mean">What does &quot;MySQL Server has gone away&quot; mean?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#does-airflow-support-extended-ascii-or-unicode-characters">Does Airflow support extended ASCII or unicode characters?</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#how-to-fix-exception-global-variable-explicit-defaults-for-timestamp-needs-to-be-on-1">How to fix Exception: Global variable <code class="docutils literal notranslate"><span class="pre">explicit_defaults_for_timestamp</span></code> needs to be on (1)?</a></li>
 </ul>
@@ -724,25 +724,25 @@
 <h3>Why is task not getting scheduled?<a class="headerlink" href="#why-is-task-not-getting-scheduled" title="Permalink to this headline">¶</a></h3>
 <p>There are very many reasons why your task might not be getting scheduled. Here are some of the common causes:</p>
 <ul class="simple">
-<li><p>Does your script “compile”, can the Airflow engine parse it and find your
+<li><p>Does your script &quot;compile&quot;, can the Airflow engine parse it and find your
 DAG object? To test this, you can run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">list</span></code> and
 confirm that your DAG shows up in the list. You can also run
 <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">tasks</span> <span class="pre">list</span> <span class="pre">foo_dag_id</span> <span class="pre">--tree</span></code> and confirm that your task
 shows up in the list as expected. If you use the CeleryExecutor, you
 may want to confirm that this works both where the scheduler runs as well
 as where the worker runs.</p></li>
-<li><p>Does the file containing your DAG contain the string “airflow” and “DAG” somewhere
+<li><p>Does the file containing your DAG contain the string &quot;airflow&quot; and &quot;DAG&quot; somewhere
 in the contents? When searching the DAG directory, Airflow ignores files not containing
-“airflow” and “DAG” in order to prevent the DagBag parsing from importing all python
-files collocated with user’s DAGs.</p></li>
+&quot;airflow&quot; and &quot;DAG&quot; in order to prevent the DagBag parsing from importing all python
+files collocated with user's DAGs.</p></li>
 <li><p>Is your <code class="docutils literal notranslate"><span class="pre">start_date</span></code> set properly? The Airflow scheduler triggers the
 task soon after the <code class="docutils literal notranslate"><span class="pre">start_date</span> <span class="pre">+</span> <span class="pre">schedule_interval</span></code> is passed.</p></li>
 <li><p>Is your <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> set properly? The default <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>
 is one day (<code class="docutils literal notranslate"><span class="pre">datetime.timedelta(1)</span></code>). You must specify a different <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>
 directly to the DAG object you instantiate, not as a <code class="docutils literal notranslate"><span class="pre">default_param</span></code>, as task instances
-do not override their parent DAG’s <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>.</p></li>
+do not override their parent DAG's <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code>.</p></li>
 <li><p>Is your <code class="docutils literal notranslate"><span class="pre">start_date</span></code> beyond where you can see it in the UI? If you
-set your <code class="docutils literal notranslate"><span class="pre">start_date</span></code> to some time say 3 months ago, you won’t be able to see
+set your <code class="docutils literal notranslate"><span class="pre">start_date</span></code> to some time say 3 months ago, you won't be able to see
 it in the main view in the UI, but you should be able to see it in the
 <code class="docutils literal notranslate"><span class="pre">Menu</span> <span class="pre">-&gt;</span> <span class="pre">Browse</span> <span class="pre">-&gt;Task</span> <span class="pre">Instances</span></code>.</p></li>
 <li><p>Are the dependencies for the task met? The task instances directly
@@ -755,7 +755,7 @@ task instance must have succeeded.
 You can view how these properties are set from the <code class="docutils literal notranslate"><span class="pre">Task</span> <span class="pre">Instance</span> <span class="pre">Details</span></code>
 page for your task.</p></li>
 <li><p>Are the DagRuns you need created and active? A DagRun represents a specific
-execution of an entire DAG and has a state (running, success, failed, …).
+execution of an entire DAG and has a state (running, success, failed, ...).
 The scheduler creates new DagRun as it moves forward, but never goes back
 in time to create new ones. The scheduler only evaluates <code class="docutils literal notranslate"><span class="pre">running</span></code> DagRuns
 to see what task instances it can trigger. Note that clearing tasks
@@ -799,7 +799,7 @@ per task.</p></li>
 however if you need more throughput you can <a class="reference internal" href="concepts/scheduler.html#scheduler-ha"><span class="std std-ref">start multiple schedulers</span></a>.</p>
 </div>
 <div class="section" id="how-do-i-trigger-tasks-based-on-another-task-s-failure">
-<h3>How do I trigger tasks based on another task’s failure?<a class="headerlink" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure" title="Permalink to this headline">¶</a></h3>
+<h3>How do I trigger tasks based on another task's failure?<a class="headerlink" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure" title="Permalink to this headline">¶</a></h3>
 <p>You can achieve this with <a class="reference internal" href="concepts/dags.html#concepts-trigger-rules"><span class="std std-ref">Trigger Rules</span></a>.</p>
 </div>
 <div class="section" id="how-to-control-dag-file-parsing-timeout-for-different-dag-files">
@@ -837,7 +837,7 @@ or a higher value.</p>
 <p>The dag parser will skip the <code class="docutils literal notranslate"><span class="pre">min_file_process_interval</span></code> check if a file is recently modified.</p>
 <p>This might not work for case where the DAG is imported/created from a separate file. Example:
 <code class="docutils literal notranslate"><span class="pre">dag_file.py</span></code> that imports <code class="docutils literal notranslate"><span class="pre">dag_loader.py</span></code> where the actual logic of the DAG file is as shown below.
-In this case if <code class="docutils literal notranslate"><span class="pre">dag_loader.py</span></code> is updated but <code class="docutils literal notranslate"><span class="pre">dag_file.py</span></code> is not updated, the changes won’t be reflected
+In this case if <code class="docutils literal notranslate"><span class="pre">dag_loader.py</span></code> is updated but <code class="docutils literal notranslate"><span class="pre">dag_file.py</span></code> is not updated, the changes won't be reflected
 until <code class="docutils literal notranslate"><span class="pre">min_file_process_interval</span></code> is reached since DAG Parser will look for modified time for <code class="docutils literal notranslate"><span class="pre">dag_file.py</span></code> file.</p>
 <div class="literal-block-wrapper docutils container" id="dag-file-py">
 <div class="code-block-caption"><span class="caption-text">dag_file.py</span><a class="headerlink" href="#dag-file-py" title="Permalink to this code">¶</a></div>
@@ -879,7 +879,7 @@ until <code class="docutils literal notranslate"><span class="pre">min_file_proc
 <div class="section" id="dag-construction">
 <h2>DAG construction<a class="headerlink" href="#dag-construction" title="Permalink to this headline">¶</a></h2>
 <div class="section" id="what-s-the-deal-with-start-date">
-<h3>What’s the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?<a class="headerlink" href="#what-s-the-deal-with-start-date" title="Permalink to this headline">¶</a></h3>
+<h3>What's the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?<a class="headerlink" href="#what-s-the-deal-with-start-date" title="Permalink to this headline">¶</a></h3>
 <p><code class="docutils literal notranslate"><span class="pre">start_date</span></code> is partly legacy from the pre-DagRun era, but it is still
 relevant in many ways. When creating a new DAG, you probably want to set
 a global <code class="docutils literal notranslate"><span class="pre">start_date</span></code> for your tasks. This can be done by declaring your
@@ -905,21 +905,21 @@ the execution of tasks within the schedule interval.
 While <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> does allow specifying a <code class="docutils literal notranslate"><span class="pre">datetime.timedelta</span></code>
 object, we recommend using the macros or cron expressions instead, as
 it enforces this idea of rounded schedules.</p>
-<p>When using <code class="docutils literal notranslate"><span class="pre">depends_on_past=True</span></code>, it’s important to pay special attention
+<p>When using <code class="docutils literal notranslate"><span class="pre">depends_on_past=True</span></code>, it's important to pay special attention
 to <code class="docutils literal notranslate"><span class="pre">start_date</span></code>, as the past dependency is not enforced only on the specific
-schedule of the <code class="docutils literal notranslate"><span class="pre">start_date</span></code> specified for the task. It’s also
+schedule of the <code class="docutils literal notranslate"><span class="pre">start_date</span></code> specified for the task. It's also
 important to watch DagRun activity status in time when introducing
 new <code class="docutils literal notranslate"><span class="pre">depends_on_past=True</span></code>, unless you are planning on running a backfill
 for the new task(s).</p>
-<p>It is also important to note that the task’s <code class="docutils literal notranslate"><span class="pre">start_date</span></code>, in the context of a
-backfill CLI command, gets overridden by the backfill’s <code class="docutils literal notranslate"><span class="pre">start_date</span></code> commands.
+<p>It is also important to note that the task's <code class="docutils literal notranslate"><span class="pre">start_date</span></code>, in the context of a
+backfill CLI command, gets overridden by the backfill's <code class="docutils literal notranslate"><span class="pre">start_date</span></code> commands.
 This allows for a backfill on tasks that have <code class="docutils literal notranslate"><span class="pre">depends_on_past=True</span></code> to
 actually start. If this were not the case, the backfill just would not start.</p>
 </div>
 <div class="section" id="using-time-zones">
 <h3>Using time zones<a class="headerlink" href="#using-time-zones" title="Permalink to this headline">¶</a></h3>
-<p>Creating a time zone aware datetime (e.g. DAG’s <code class="docutils literal notranslate"><span class="pre">start_date</span></code>) is quite simple. Just make sure to supply
-a time zone aware dates using <code class="docutils literal notranslate"><span class="pre">pendulum</span></code>. Don’t try to use standard library
+<p>Creating a time zone aware datetime (e.g. DAG's <code class="docutils literal notranslate"><span class="pre">start_date</span></code>) is quite simple. Just make sure to supply
+a time zone aware dates using <code class="docutils literal notranslate"><span class="pre">pendulum</span></code>. Don't try to use standard library
 <a class="reference external" href="https://docs.python.org/3/library/datetime.html#timezone-objects">timezone</a> as they are known to
 have limitations and we deliberately disallow using them in DAGs.</p>
 </div>
@@ -934,12 +934,12 @@ you would do it at <code class="docutils literal notranslate"><span class="pre">
 data for <code class="docutils literal notranslate"><span class="pre">2016-02-19</span></code> becomes available. This interval between midnights of
 <code class="docutils literal notranslate"><span class="pre">2016-02-19</span></code> and <code class="docutils literal notranslate"><span class="pre">2016-02-20</span></code> is called the <em>data interval</em>, and since it
 represents data in the date of <code class="docutils literal notranslate"><span class="pre">2016-02-19</span></code>, this date is also called the
-run’s <em>logical date</em>, or the date that this DAG run is executed for, thus
+run's <em>logical date</em>, or the date that this DAG run is executed for, thus
 <em>execution date</em>.</p>
 <p>For backward compatibility, a datetime value <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> is still
 as <a class="reference internal" href="templates-ref.html#templates-variables"><span class="std std-ref">Template variables</span></a> with various formats in Jinja
-templated fields, and in Airflow’s Python API. It is also included in the
-context dictionary given to an Operator’s execute function.</p>
+templated fields, and in Airflow's Python API. It is also included in the
+context dictionary given to an Operator's execute function.</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">MyOperator</span><span class="p">(</span><span class="n">BaseOperator</span><span class="p">):</span>
     <span class="k">def</span> <span class="nf">execute</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">context</span><span class="p">):</span>
         <span class="n">logging</span><span class="o">.</span><span class="n">info</span><span class="p">(</span><span class="n">context</span><span class="p">[</span><span class="s2">&quot;execution_date&quot;</span><span class="p">])</span>
@@ -1008,12 +1008,12 @@ commonly attempted in <code class="docutils literal notranslate"><span class="pr
 <span class="n">bo</span> <span class="o">=</span> <span class="n">BashOperator</span><span class="p">(</span><span class="n">task_id</span><span class="o">=</span><span class="s2">&quot;my_task&quot;</span><span class="p">,</span> <span class="n">bash_command</span><span class="o">=</span><span class="s2">&quot;echo {{ my_custom_macro }}&quot;</span><span class="p">,</span> <span class="n">dag</span><span class="o">=</span><span class="n">dag</span><span class="p">)</span>
 </pre></div>
 </div>
-<p>This will echo “day={{ ds }}” instead of “day=2020-01-01” for a DAG run with a
+<p>This will echo &quot;day={{ ds }}&quot; instead of &quot;day=2020-01-01&quot; for a DAG run with a
 <code class="docutils literal notranslate"><span class="pre">data_interval_start</span></code> of 2020-01-01 00:00:00.</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="n">bo</span> <span class="o">=</span> <span class="n">BashOperator</span><span class="p">(</span><span class="n">task_id</span><span class="o">=</span><span class="s2">&quot;my_task&quot;</span><span class="p">,</span> <span class="n">bash_command</span><span class="o">=</span><span class="s2">&quot;echo day={{ ds }}&quot;</span><span class="p">,</span> <span class="n">dag</span><span class="o [...]
 </pre></div>
 </div>
-<p>By using the ds macros directly in the template_field, the rendered value results in “day=2020-01-01”.</p>
+<p>By using the ds macros directly in the template_field, the rendered value results in &quot;day=2020-01-01&quot;.</p>
 </div>
 <div class="section" id="why-next-ds-or-prev-ds-might-not-contain-expected-values">
 <h3>Why <code class="docutils literal notranslate"><span class="pre">next_ds</span></code> or <code class="docutils literal notranslate"><span class="pre">prev_ds</span></code> might not contain expected values?<a class="headerlink" href="#why-next-ds-or-prev-ds-might-not-contain-expected-values" title="Permalink to this headline">¶</a></h3>
@@ -1035,7 +1035,7 @@ that trigger Jinja templating. A common occurrence is with <a class="reference i
 other directories to the <code class="docutils literal notranslate"><span class="pre">template_searchpath</span></code> of the DAG object to allow for other non-relative location.</p>
 </div>
 <div class="section" id="how-to-trigger-tasks-based-on-another-task-s-failure">
-<h3>How to trigger tasks based on another task’s failure?<a class="headerlink" href="#how-to-trigger-tasks-based-on-another-task-s-failure" title="Permalink to this headline">¶</a></h3>
+<h3>How to trigger tasks based on another task's failure?<a class="headerlink" href="#how-to-trigger-tasks-based-on-another-task-s-failure" title="Permalink to this headline">¶</a></h3>
 <p>For tasks that are related through dependency, you can set the <code class="docutils literal notranslate"><span class="pre">trigger_rule</span></code> to <code class="docutils literal notranslate"><span class="pre">TriggerRule.ALL_FAILED</span></code> if the
 task execution depends on the failure of ALL its upstream tasks or <code class="docutils literal notranslate"><span class="pre">TriggerRule.ONE_FAILED</span></code> for just one of the
 upstream task.</p>
@@ -1096,8 +1096,8 @@ issue recurs.</p>
 <div class="section" id="mysql-and-mysql-variant-databases">
 <h2>MySQL and MySQL variant Databases<a class="headerlink" href="#mysql-and-mysql-variant-databases" title="Permalink to this headline">¶</a></h2>
 <div class="section" id="what-does-mysql-server-has-gone-away-mean">
-<h3>What does “MySQL Server has gone away” mean?<a class="headerlink" href="#what-does-mysql-server-has-gone-away-mean" title="Permalink to this headline">¶</a></h3>
-<p>You may occasionally experience <code class="docutils literal notranslate"><span class="pre">OperationalError</span></code> with the message “MySQL Server has gone away”. This is due to the
+<h3>What does &quot;MySQL Server has gone away&quot; mean?<a class="headerlink" href="#what-does-mysql-server-has-gone-away-mean" title="Permalink to this headline">¶</a></h3>
+<p>You may occasionally experience <code class="docutils literal notranslate"><span class="pre">OperationalError</span></code> with the message &quot;MySQL Server has gone away&quot;. This is due to the
 connection pool keeping connections open too long and you are given an old connection that has expired. To ensure a
 valid connection, you can set <a class="reference internal" href="configurations-ref.html#config-core-sql-alchemy-pool-recycle"><span class="std std-ref">sql_alchemy_pool_recycle (Deprecated)</span></a> to ensure connections are invalidated after
 that many seconds and new ones are created.</p>
@@ -1205,13 +1205,13 @@ the MySQL database since they define charset explicitly.</p>
 <li><a class="reference internal" href="#why-is-task-not-getting-scheduled">Why is task not getting scheduled?</a></li>
 <li><a class="reference internal" href="#how-to-improve-dag-performance">How to improve DAG performance?</a></li>
 <li><a class="reference internal" href="#how-to-reduce-dag-scheduling-latency-task-delay">How to reduce DAG scheduling latency / task delay?</a></li>
-<li><a class="reference internal" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure">How do I trigger tasks based on another task’s failure?</a></li>
+<li><a class="reference internal" href="#how-do-i-trigger-tasks-based-on-another-task-s-failure">How do I trigger tasks based on another task's failure?</a></li>
 <li><a class="reference internal" href="#how-to-control-dag-file-parsing-timeout-for-different-dag-files">How to control DAG file parsing timeout for different DAG files?</a></li>
 <li><a class="reference internal" href="#when-there-are-a-lot-1000-of-dags-files-how-to-speed-up-parsing-of-new-files">When there are a lot (&gt;1000) of dags files, how to speed up parsing of new files?</a></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#dag-construction">DAG construction</a><ul>
-<li><a class="reference internal" href="#what-s-the-deal-with-start-date">What’s the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?</a></li>
+<li><a class="reference internal" href="#what-s-the-deal-with-start-date">What's the deal with <code class="docutils literal notranslate"><span class="pre">start_date</span></code>?</a></li>
 <li><a class="reference internal" href="#using-time-zones">Using time zones</a></li>
 <li><a class="reference internal" href="#what-does-execution-date-mean">What does <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> mean?</a></li>
 <li><a class="reference internal" href="#how-to-create-dags-dynamically">How to create DAGs dynamically?</a></li>
@@ -1222,7 +1222,7 @@ the MySQL database since they define charset explicitly.</p>
 </li>
 <li><a class="reference internal" href="#task-execution-interactions">Task execution interactions</a><ul>
 <li><a class="reference internal" href="#what-does-templatenotfound-mean">What does <code class="docutils literal notranslate"><span class="pre">TemplateNotFound</span></code> mean?</a></li>
-<li><a class="reference internal" href="#how-to-trigger-tasks-based-on-another-task-s-failure">How to trigger tasks based on another task’s failure?</a></li>
+<li><a class="reference internal" href="#how-to-trigger-tasks-based-on-another-task-s-failure">How to trigger tasks based on another task's failure?</a></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#airflow-ui">Airflow UI</a><ul>
@@ -1232,7 +1232,7 @@ the MySQL database since they define charset explicitly.</p>
 </ul>
 </li>
 <li><a class="reference internal" href="#mysql-and-mysql-variant-databases">MySQL and MySQL variant Databases</a><ul>
-<li><a class="reference internal" href="#what-does-mysql-server-has-gone-away-mean">What does “MySQL Server has gone away” mean?</a></li>
+<li><a class="reference internal" href="#what-does-mysql-server-has-gone-away-mean">What does &quot;MySQL Server has gone away&quot; mean?</a></li>
 <li><a class="reference internal" href="#does-airflow-support-extended-ascii-or-unicode-characters">Does Airflow support extended ASCII or unicode characters?</a></li>
 <li><a class="reference internal" href="#how-to-fix-exception-global-variable-explicit-defaults-for-timestamp-needs-to-be-on-1">How to fix Exception: Global variable <code class="docutils literal notranslate"><span class="pre">explicit_defaults_for_timestamp</span></code> needs to be on (1)?</a></li>
 </ul>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/connection.html b/docs-archive/apache-airflow/2.3.0/howto/connection.html
index a068481d6..2845292a0 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/connection.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/connection.html
@@ -738,7 +738,7 @@
 <p class="admonition-title">See also</p>
 <p>For an overview of hooks and connections, see <a class="reference internal" href="../concepts/connections.html"><span class="doc">Connections &amp; Hooks</span></a>.</p>
 </div>
-<p>Airflow’s <a class="reference internal" href="../_api/airflow/models/connection/index.html#airflow.models.connection.Connection" title="airflow.models.connection.Connection"><code class="xref py py-class docutils literal notranslate"><span class="pre">Connection</span></code></a> object is used for storing credentials and other information necessary for connecting to external services.</p>
+<p>Airflow's <a class="reference internal" href="../_api/airflow/models/connection/index.html#airflow.models.connection.Connection" title="airflow.models.connection.Connection"><code class="xref py py-class docutils literal notranslate"><span class="pre">Connection</span></code></a> object is used for storing credentials and other information necessary for connecting to external services.</p>
 <p>Connections may be defined in the following ways:</p>
 <blockquote>
 <div><ul class="simple">
@@ -752,7 +752,7 @@
 <h2>Storing connections in environment variables<a class="headerlink" href="#storing-connections-in-environment-variables" title="Permalink to this headline">¶</a></h2>
 <p>Airflow connections may be defined in environment variables.</p>
 <p>The naming convention is <span class="target" id="index-0"></span><a class="reference internal" href="../cli-and-env-variables-ref.html#envvar-AIRFLOW_CONN_-CONN_ID"><code class="xref std std-envvar docutils literal notranslate"><span class="pre">AIRFLOW_CONN_{CONN_ID}</span></code></a>, all uppercase (note the single underscores surrounding <code class="docutils literal notranslate"><span class="pre">CONN</span></code>).  So if your connection id is <code class="docutils literal notr [...]
-<p>The value can be either JSON or Airflow’s URI format.</p>
+<p>The value can be either JSON or Airflow's URI format.</p>
 <div class="section" id="json-format-example">
 <span id="connection-serialization-json-example"></span><h3>JSON format example<a class="headerlink" href="#json-format-example" title="Permalink to this headline">¶</a></h3>
 <div class="versionadded">
@@ -841,7 +841,7 @@ changes.</p>
 <span class="s1">    }&#39;</span>
 </pre></div>
 </div>
-<p>Alternatively you may use Airflow’ Connection URI format (see <a class="reference internal" href="#generating-connection-uri"><span class="std std-ref">Generating a Connection URI</span></a>).</p>
+<p>Alternatively you may use Airflow' Connection URI format (see <a class="reference internal" href="#generating-connection-uri"><span class="std std-ref">Generating a Connection URI</span></a>).</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>airflow connections add <span class="s1">&#39;my_prod_db&#39;</span> <span class="se">\</span>
     --conn-uri <span class="s1">&#39;&lt;conn-type&gt;://&lt;login&gt;:&lt;password&gt;@&lt;host&gt;:&lt;port&gt;/&lt;schema&gt;?param1=val1&amp;param2=val2&amp;...&#39;</span>
 </pre></div>
@@ -873,16 +873,16 @@ Passwords cannot be manipulated or read without the key. For information on conf
 <a class="reference internal" href="#creating-connection-ui"><span class="std std-ref">create</span></a> or <a class="reference internal" href="#editing-connection-ui"><span class="std std-ref">edit</span></a> connection page, or through calling
 <a class="reference internal" href="../stable-rest-api-ref.html"><span class="doc">Connections REST API</span></a>.</p>
 <p>To test a connection Airflow calls out the <code class="docutils literal notranslate"><span class="pre">test_connection</span></code> method from the associated hook class and reports the
-results of it. It may happen that the connection type does not have any associated hook or the hook doesn’t have the
+results of it. It may happen that the connection type does not have any associated hook or the hook doesn't have the
 <code class="docutils literal notranslate"><span class="pre">test_connection</span></code> method implementation, in either case the error message will throw the proper error message.</p>
 <p>One important point to note is that the connections will be tested from the webserver only, so this feature is
 subject to network egress rules setup for your webserver. Also, if webserver &amp; worker machines have different libs or
 provider packages installed then the test results might differ.</p>
-<p>Last caveat is that this feature won’t be available for the connections coming out of the secrets backends.</p>
+<p>Last caveat is that this feature won't be available for the connections coming out of the secrets backends.</p>
 </div>
 <div class="section" id="custom-connection-types">
 <h3>Custom connection types<a class="headerlink" href="#custom-connection-types" title="Permalink to this headline">¶</a></h3>
-<p>Airflow allows the definition of custom connection types – including modifications of the add/edit form
+<p>Airflow allows the definition of custom connection types -- including modifications of the add/edit form
 for the connections. Custom connection types are defined in community maintained providers, but you can
 can also add a custom provider that adds custom connection types. See <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span>Provider packages</span></a>
 for description on how to add custom providers.</p>
@@ -896,7 +896,7 @@ deprecated <code class="docutils literal notranslate"><span class="pre">hook-cla
 <ul class="simple">
 <li><p>Adding custom connection types</p></li>
 <li><p>Adding automated Hook creation from the connection type</p></li>
-<li><p>Adding custom form widget to display and edit custom “extra” parameters in your connection URL</p></li>
+<li><p>Adding custom form widget to display and edit custom &quot;extra&quot; parameters in your connection URL</p></li>
 <li><p>Hiding fields that are not used for your connection</p></li>
 <li><p>Adding placeholders showing examples of how fields should be formatted</p></li>
 </ul>
@@ -910,7 +910,7 @@ Custom fields are stored in the <code class="docutils literal notranslate"><span
 method <code class="xref py py-meth docutils literal notranslate"><span class="pre">get_connection_form_widgets()</span></code>.  This method should return a dictionary. The keys
 should be the string name of the field as it should be stored in the <code class="docutils literal notranslate"><span class="pre">extra</span></code> dict.  The values should
 be inheritors of <code class="xref py py-class docutils literal notranslate"><span class="pre">wtforms.fields.core.Field</span></code>.</p>
-<p>Here’s an example:</p>
+<p>Here's an example:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="nd">@staticmethod</span>
 <span class="k">def</span> <span class="nf">get_connection_form_widgets</span><span class="p">()</span> <span class="o">-&gt;</span> <span class="n">Dict</span><span class="p">[</span><span class="nb">str</span><span class="p">,</span> <span class="n">Any</span><span class="p">]:</span>
     <span class="sd">&quot;&quot;&quot;Returns connection widgets to add to connection form&quot;&quot;&quot;</span>
@@ -933,7 +933,7 @@ be inheritors of <code class="xref py py-class docutils literal notranslate"><sp
 and this is how its value would be stored in the <code class="docutils literal notranslate"><span class="pre">extra</span></code> dict.  From 2.3 onward, you no longer need to do this.</p>
 </div>
 <p>Method <code class="xref py py-meth docutils literal notranslate"><span class="pre">get_ui_field_behaviour()</span></code> lets you customize behavior of both .  For example you can
-hide or relabel a field (e.g. if it’s unused or re-purposed) and you can add placeholder text.</p>
+hide or relabel a field (e.g. if it's unused or re-purposed) and you can add placeholder text.</p>
 <p>An example:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="nd">@staticmethod</span>
 <span class="k">def</span> <span class="nf">get_ui_field_behaviour</span><span class="p">()</span> <span class="o">-&gt;</span> <span class="n">Dict</span><span class="p">[</span><span class="nb">str</span><span class="p">,</span> <span class="n">Any</span><span class="p">]:</span>
@@ -949,14 +949,14 @@ hide or relabel a field (e.g. if it’s unused or re-purposed) and you can add p
     <span class="p">}</span>
 </pre></div>
 </div>
-<p>Note here that <em>here</em> (in contrast with <code class="docutils literal notranslate"><span class="pre">get_connection_form_widgets</span></code>) we must add the prefix <code class="docutils literal notranslate"><span class="pre">extra__&lt;conn</span> <span class="pre">type&gt;__</span></code> when referencing a custom field.  This is this is because it’s possible to create a custom field whose name overlaps with a built-in field and we need to be able to reference it unambiguou [...]
+<p>Note here that <em>here</em> (in contrast with <code class="docutils literal notranslate"><span class="pre">get_connection_form_widgets</span></code>) we must add the prefix <code class="docutils literal notranslate"><span class="pre">extra__&lt;conn</span> <span class="pre">type&gt;__</span></code> when referencing a custom field.  This is this is because it's possible to create a custom field whose name overlaps with a built-in field and we need to be able to reference it unambiguou [...]
 <p>Take a look at providers for examples of what you can do, for example <a class="reference external" href="/docs/apache-airflow-providers-jdbc/stable/_api/airflow/providers/jdbc/hooks/jdbc/index.html#airflow.providers.jdbc.hooks.jdbc.JdbcHook" title="(in apache-airflow-providers-jdbc v2.1.3)"><code class="xref py py-class docutils literal notranslate"><span class="pre">JdbcHook</span></code></a>
 and <code class="xref py py-class docutils literal notranslate"><span class="pre">AsanaHook</span></code> both make use of this feature.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Deprecated <code class="docutils literal notranslate"><span class="pre">hook-class-names</span></code></p>
 <p>Prior to Airflow 2.2.0, the connections in providers have been exposed via <code class="docutils literal notranslate"><span class="pre">hook-class-names</span></code> array
-in provider’s meta-data, this however has proven to be not well optimized for using individual hooks
+in provider's meta-data, this however has proven to be not well optimized for using individual hooks
 in workers and the <code class="docutils literal notranslate"><span class="pre">hook-class-names</span></code> array is now replaced by <code class="docutils literal notranslate"><span class="pre">connection-types</span></code> array. Until
 provider supports Airflow below 2.2.0, both <code class="docutils literal notranslate"><span class="pre">connection-types</span></code> and <code class="docutils literal notranslate"><span class="pre">hook-class-names</span></code> should be
 present. Automated checks during CI build will verify consistency of those two arrays.</p>
@@ -969,7 +969,7 @@ present. Automated checks during CI build will verify consistency of those two a
 <p>From version 2.3.0 you can serialize connections with JSON instead.  See <a class="reference internal" href="#connection-serialization-json-example"><span class="std std-ref">example</span></a>.</p>
 </div>
 <p>For historical reasons, Airflow has a special URI format that can be used for serializing a Connection object to a string value.</p>
-<p>In general, Airflow’s URI format looks like the following:</p>
+<p>In general, Airflow's URI format looks like the following:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span>my-conn-type://my-login:my-password@my-host:5432/my-schema?param1=val1&amp;param2=val2
 </pre></div>
 </div>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/create-custom-decorator.html b/docs-archive/apache-airflow/2.3.0/howto/create-custom-decorator.html
index 56b46799b..4b59c3294 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/create-custom-decorator.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/create-custom-decorator.html
@@ -686,7 +686,7 @@
 <h1>Creating Custom <code class="docutils literal notranslate"><span class="pre">&#64;task</span></code> Decorators<a class="headerlink" href="#creating-custom-task-decorators" title="Permalink to this headline">¶</a></h1>
 <p>As of Airflow 2.2 it is possible add custom decorators to the TaskFlow interface from within a provider
 package and have those decorators appear natively as part of the <code class="docutils literal notranslate"><span class="pre">&#64;task.____</span></code> design.</p>
-<p>For an example. Let’s say you were trying to create an easier mechanism to run python functions as “foo”
+<p>For an example. Let's say you were trying to create an easier mechanism to run python functions as &quot;foo&quot;
 tasks. The steps to create and register <code class="docutils literal notranslate"><span class="pre">&#64;task.foo</span></code> are:</p>
 <ol class="arabic">
 <li><p>Create a <code class="docutils literal notranslate"><span class="pre">FooDecoratedOperator</span></code></p>
@@ -755,7 +755,7 @@ a list with each item containing <code class="docutils literal notranslate"><spa
 <p>This section mostly applies to the apache-airflow managed providers. We have not decided if we will allow third-party providers to register auto-completion in this way.</p>
 </div>
 <p>For better or worse, Python IDEs can not auto-complete dynamically
-generated methods (see <a class="reference external" href="https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000665110-auto-completion-for-dynamic-module-attributes-in-python">JetBrain’s write up on the subject</a>).</p>
+generated methods (see <a class="reference external" href="https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000665110-auto-completion-for-dynamic-module-attributes-in-python">JetBrain's write up on the subject</a>).</p>
 <p>To hack around this problem, a type stub <code class="docutils literal notranslate"><span class="pre">airflow/decorators/__init__.pyi</span></code> is provided to statically declare
 the type signature of each task decorator. A newly added task decorator should declare its signature stub
 like this:</p>
@@ -866,13 +866,13 @@ like this:</p>
 </pre></div>
 </div>
 </div>
-<p>The signature should allow only keyword-only arguments, including one named <code class="docutils literal notranslate"><span class="pre">multiple_outputs</span></code> that’s
+<p>The signature should allow only keyword-only arguments, including one named <code class="docutils literal notranslate"><span class="pre">multiple_outputs</span></code> that's
 automatically provided by default. All other arguments should be copied directly from the real FooOperator,
 and we recommend adding a comment to explain what arguments are filled automatically by FooDecoratedOperator
 and thus not included.</p>
 <p>If the new decorator can be used without arguments (e.g. <code class="docutils literal notranslate"><span class="pre">&#64;task.python</span></code> instead of <code class="docutils literal notranslate"><span class="pre">&#64;task.python()</span></code>),
-You should also add an overload that takes a single callable immediately after the “real” definition so mypy
-can recognize the function as a “bare decorator”:</p>
+You should also add an overload that takes a single callable immediately after the &quot;real&quot; definition so mypy
+can recognize the function as a &quot;bare decorator&quot;:</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header"><span class="example-title">airflow/decorators/__init__.pyi</span></p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span>    <span class="nd">@overload</span>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/custom-operator.html b/docs-archive/apache-airflow/2.3.0/howto/custom-operator.html
index 4320c5f5c..637fca594 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/custom-operator.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/custom-operator.html
@@ -714,7 +714,7 @@ Airflow context as a parameter that can be used to read config values.</p></li>
 will be instantiated once per scheduler cycle per task using them, and making database calls can significantly slow
 down scheduling and waste resources.</p>
 </div>
-<p>Let’s implement an example <code class="docutils literal notranslate"><span class="pre">HelloOperator</span></code> in a new file <code class="docutils literal notranslate"><span class="pre">hello_operator.py</span></code>:</p>
+<p>Let's implement an example <code class="docutils literal notranslate"><span class="pre">HelloOperator</span></code> in a new file <code class="docutils literal notranslate"><span class="pre">hello_operator.py</span></code>:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">airflow.models.baseoperator</span> <span class="kn">import</span> <span class="n">BaseOperator</span>
 
 
@@ -749,7 +749,7 @@ See <a class="reference internal" href="../modules_management.html"><span class=
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">hello_operator</span> <span class="kn">import</span> <span class="n">HelloOperator</span>
 </pre></div>
 </div>
-<p>If an operator communicates with an external service (API, database, etc) it’s a good idea
+<p>If an operator communicates with an external service (API, database, etc) it's a good idea
 to implement the communication layer using a <a class="reference internal" href="#custom-operator-hook"><span class="std std-ref">Hooks</span></a>. In this way the implemented logic
 can be reused by other users in different operators. Such approach provides better decoupling and
 utilization of added integration than using <code class="docutils literal notranslate"><span class="pre">CustomServiceBaseOperator</span></code> for each external service.</p>
@@ -765,7 +765,7 @@ creating a connection per task, you can retrieve a connection from the hook and
 Hook also helps to avoid storing connection auth parameters in a DAG.
 See <a class="reference internal" href="connection.html"><span class="doc">Managing Connections</span></a> for how to create and manage connections and <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span>Provider packages</span></a> for
 details of how to add your custom connection types via providers.</p>
-<p>Let’s extend our previous example to fetch name from MySQL:</p>
+<p>Let's extend our previous example to fetch name from MySQL:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">HelloDBOperator</span><span class="p">(</span><span class="n">BaseOperator</span><span class="p">):</span>
     <span class="k">def</span> <span class="fm">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">name</span><span class="p">:</span> <span class="nb">str</span><span class="p">,</span> <span class="n">mysql_conn_id</span><span class="p">:</span> <span class="nb">str</span><span class="p">,</span> <span class="n">database</span><span class="p">:</span> <span class="nb">str</span><span class="p">,</span> <span class="o">**</span><s [...]
         <span class="nb">super</span><span class="p">()</span><span class="o">.</span><span class="fm">__init__</span><span class="p">(</span><span class="o">**</span><span class="n">kwargs</span><span class="p">)</span>
@@ -782,7 +782,7 @@ details of how to add your custom connection types via providers.</p>
         <span class="k">return</span> <span class="n">message</span>
 </pre></div>
 </div>
-<p>When the operator invokes the query on the hook object, a new connection gets created if it doesn’t exist.
+<p>When the operator invokes the query on the hook object, a new connection gets created if it doesn't exist.
 The hook retrieves the auth parameters such as username and password from Airflow
 backend and passes the params to the <a class="reference internal" href="../_api/airflow/hooks/base/index.html#airflow.hooks.base.BaseHook.get_connection" title="airflow.hooks.base.BaseHook.get_connection"><code class="xref py py-func docutils literal notranslate"><span class="pre">airflow.hooks.base.BaseHook.get_connection()</span></code></a>.
 You should create hook only in the <code class="docutils literal notranslate"><span class="pre">execute</span></code> method or any method which is called from <code class="docutils literal notranslate"><span class="pre">execute</span></code>.
@@ -915,7 +915,7 @@ configuration at <code class="docutils literal notranslate"><span class="pre">qu
 <h2>Define an operator extra link<a class="headerlink" href="#define-an-operator-extra-link" title="Permalink to this headline">¶</a></h2>
 <p>For your operator, you can <a class="reference internal" href="define_extra_link.html"><span class="doc">Define an extra link</span></a> that can
 redirect users to external systems. For example, you can add a link that redirects
-the user to the operator’s manual.</p>
+the user to the operator's manual.</p>
 </div>
 <div class="section" id="sensors">
 <h2>Sensors<a class="headerlink" href="#sensors" title="Permalink to this headline">¶</a></h2>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/define_extra_link.html b/docs-archive/apache-airflow/2.3.0/howto/define_extra_link.html
index 2c2c12ece..3df505e56 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/define_extra_link.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/define_extra_link.html
@@ -806,7 +806,7 @@ Console, but if we wanted to change that link we could:</p>
 <p><strong>Adding Operator Links via Providers</strong></p>
 <p>As explained in <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span>Provider packages</span></a>, when you create your own Airflow Provider, you can
 specify the list of operators that provide extra link capability. This happens by including the operator
-class name in the <code class="docutils literal notranslate"><span class="pre">provider-info</span></code> information stored in your Provider’s package meta-data:</p>
+class name in the <code class="docutils literal notranslate"><span class="pre">provider-info</span></code> information stored in your Provider's package meta-data:</p>
 <p>Example meta-data required in your provider-info dictionary (this is part of the meta-data returned
 by <code class="docutils literal notranslate"><span class="pre">apache-airflow-providers-google</span></code> provider currently:</p>
 <div class="highlight-yaml notranslate"><div class="highlight"><pre><span></span><span class="nt">extra-links</span><span class="p">:</span><span class="w"></span>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/dynamic-dag-generation.html b/docs-archive/apache-airflow/2.3.0/howto/dynamic-dag-generation.html
index 239ae2025..de939bed2 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/dynamic-dag-generation.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/dynamic-dag-generation.html
@@ -723,7 +723,7 @@ development environment, depending on the value of the environment variable.</p>
 Such constant can then be imported directly by your DAG and used to construct the object and build
 the dependencies. This makes it easy to import such code from multiple DAGs without the need to find,
 load and parse the meta-data stored in the constant - this is done automatically by Python interpreter
-when it processes the “import” statement. This sounds strange at first, but it is surprisingly easy
+when it processes the &quot;import&quot; statement. This sounds strange at first, but it is surprisingly easy
 to generate such code and make sure this is a valid Python code that you can import from your DAGs.</p>
 <p>For example assume you dynamically generate (in your DAG folder), the <code class="docutils literal notranslate"><span class="pre">my_company_utils/common.py</span></code> file:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="c1"># This file is generated automatically !</span>
@@ -744,7 +744,7 @@ to generate such code and make sure this is a valid Python code that you can imp
         <span class="k">pass</span>
 </pre></div>
 </div>
-<p>Don’t forget that in this case you need to add empty <code class="docutils literal notranslate"><span class="pre">__init__.py</span></code> file in the <code class="docutils literal notranslate"><span class="pre">my_company_utils</span></code> folder
+<p>Don't forget that in this case you need to add empty <code class="docutils literal notranslate"><span class="pre">__init__.py</span></code> file in the <code class="docutils literal notranslate"><span class="pre">my_company_utils</span></code> folder
 and you should add the <code class="docutils literal notranslate"><span class="pre">my_company_utils/.*</span></code> line to <code class="docutils literal notranslate"><span class="pre">.airflowignore</span></code> file (if using the regexp ignore
 syntax), so that the whole folder is ignored by the scheduler when it looks for DAGs.</p>
 </div>
@@ -752,7 +752,7 @@ syntax), so that the whole folder is ignored by the scheduler when it looks for
 <h2>Dynamic DAGs with external configuration from a structured data file<a class="headerlink" href="#dynamic-dags-with-external-configuration-from-a-structured-data-file" title="Permalink to this headline">¶</a></h2>
 <p>If you need to use a more complex meta-data to prepare your DAG structure and you would prefer to keep the
 data in a structured non-python format, you should export the data to the DAG folder in a file and push
-it to the DAG folder, rather than try to pull the data by the DAG’s top-level code - for the reasons
+it to the DAG folder, rather than try to pull the data by the DAG's top-level code - for the reasons
 explained in the parent <a class="reference internal" href="../best-practices.html#best-practices-top-level-code"><span class="std std-ref">Top level Python Code</span></a>.</p>
 <p>The meta-data should be exported and stored together with the DAGs in a convenient file format (JSON, YAML
 formats are good candidates) in DAG folder. Ideally, the meta-data should be published in the same
@@ -797,7 +797,7 @@ As long as a <code class="docutils literal notranslate"><span class="pre">DAG</s
 Each of them can run separately with related configuration</p>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
-<p>Using this practice, pay attention to “late binding” behaviour in Python loops. See <a class="reference external" href="https://github.com/apache/airflow/discussions/21278#discussioncomment-2103559">that GitHub discussion</a> for more details</p>
+<p>Using this practice, pay attention to &quot;late binding&quot; behaviour in Python loops. See <a class="reference external" href="https://github.com/apache/airflow/discussions/21278#discussioncomment-2103559">that GitHub discussion</a> for more details</p>
 </div>
 </div>
 </div>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/email-config.html b/docs-archive/apache-airflow/2.3.0/howto/email-config.html
index 7ade38f03..11a18fe01 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/email-config.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/email-config.html
@@ -709,19 +709,19 @@ in the <code class="docutils literal notranslate"><span class="pre">[email]</spa
 <span class="na">html_content_template</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">/path/to/my_html_content_template_file</span><span class="w"></span>
 </pre></div>
 </div>
-<p>You can configure sender’s email address by setting <code class="docutils literal notranslate"><span class="pre">from_email</span></code> in the <code class="docutils literal notranslate"><span class="pre">[email]</span></code> section.</p>
+<p>You can configure sender's email address by setting <code class="docutils literal notranslate"><span class="pre">from_email</span></code> in the <code class="docutils literal notranslate"><span class="pre">[email]</span></code> section.</p>
 <p>To configure SMTP settings, checkout the <a class="reference internal" href="../configurations-ref.html#config-smtp"><span class="std std-ref">SMTP</span></a> section in the standard configuration.
 If you do not want to store the SMTP credentials in the config or in the environment variables, you can create a
-connection called <code class="docutils literal notranslate"><span class="pre">smtp_default</span></code> of <code class="docutils literal notranslate"><span class="pre">Email</span></code> type, or choose a custom connection name and set the <code class="docutils literal notranslate"><span class="pre">email_conn_id</span></code> with it’s name in
+connection called <code class="docutils literal notranslate"><span class="pre">smtp_default</span></code> of <code class="docutils literal notranslate"><span class="pre">Email</span></code> type, or choose a custom connection name and set the <code class="docutils literal notranslate"><span class="pre">email_conn_id</span></code> with it's name in
 the configuration &amp; store SMTP username-password in it. Other SMTP settings like host, port etc always gets picked up
-from the configuration only. The connection can be of any type (for example ‘HTTP connection’).</p>
+from the configuration only. The connection can be of any type (for example 'HTTP connection').</p>
 <p>If you want to check which email backend is currently set, you can use <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">config</span> <span class="pre">get-value</span> <span class="pre">email</span> <span class="pre">email_backend</span></code> command as in
 the example below.</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$ airflow config get-value email email_backend
 airflow.utils.email.send_email_smtp
 </pre></div>
 </div>
-<p>To access the task’s information you use <a class="reference external" href="http://jinja.pocoo.org/docs/dev/">Jinja Templating</a>  in your template files.</p>
+<p>To access the task's information you use <a class="reference external" href="http://jinja.pocoo.org/docs/dev/">Jinja Templating</a>  in your template files.</p>
 <p>For example a <code class="docutils literal notranslate"><span class="pre">html_content_template</span></code> file could look like this:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">Try</span> <span class="p">{{</span><span class="n">try_number</span><span class="p">}}</span> <span class="n">out</span> <span class="n">of</span> <span class="p">{{</span><span class="n">max_tries</span> <span class="o">+</span> <span class="mi">1</span><span class="p">}}</span><span class="o">&lt;</span><span class="n">br</span><span class="o">&gt;</span>
 <span class="ne">Exception</span><span class="p">:</span><span class="o">&lt;</span><span class="n">br</span><span class="o">&gt;</span><span class="p">{{</span><span class="n">exception_html</span><span class="p">}}</span><span class="o">&lt;</span><span class="n">br</span><span class="o">&gt;</span>
@@ -799,7 +799,7 @@ airflow.utils.email.send_email_smtp
 </div>
 </li>
 <li><p>Create a connection called <code class="docutils literal notranslate"><span class="pre">sendgrid_default</span></code>, or choose a custom connection
-name and set it in <code class="docutils literal notranslate"><span class="pre">email_conn_id</span></code> of  ‘Email’ type. Only login and password
+name and set it in <code class="docutils literal notranslate"><span class="pre">email_conn_id</span></code> of  'Email' type. Only login and password
 are used from the connection.</p></li>
 </ol>
 <img alt="create email connection" class="align-center" src="../_images/email_connection.png" />
diff --git a/docs-archive/apache-airflow/2.3.0/howto/index.html b/docs-archive/apache-airflow/2.3.0/howto/index.html
index eb80297ba..95e81e470 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/index.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/index.html
@@ -699,7 +699,7 @@ configuring an Airflow environment.</p>
 <li class="toctree-l2"><a class="reference internal" href="set-up-database.html#setting-up-a-mssql-database">Setting up a MsSQL Database</a></li>
 <li class="toctree-l2"><a class="reference internal" href="set-up-database.html#other-configuration-options">Other configuration options</a></li>
 <li class="toctree-l2"><a class="reference internal" href="set-up-database.html#initialize-the-database">Initialize the database</a></li>
-<li class="toctree-l2"><a class="reference internal" href="set-up-database.html#what-s-next">What’s next?</a></li>
+<li class="toctree-l2"><a class="reference internal" href="set-up-database.html#what-s-next">What's next?</a></li>
 </ul>
 </li>
 <li class="toctree-l1"><a class="reference internal" href="operator/index.html">Using Operators</a><ul>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/operator/bash.html b/docs-archive/apache-airflow/2.3.0/howto/operator/bash.html
index 0ceaba05d..b6b077a5e 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/operator/bash.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/operator/bash.html
@@ -746,10 +746,10 @@ commands in a <a class="reference external" href="https://www.gnu.org/software/b
 </div>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
-<p>Care should be taken with “user” input or when using Jinja templates in the
+<p>Care should be taken with &quot;user&quot; input or when using Jinja templates in the
 <code class="docutils literal notranslate"><span class="pre">bash_command</span></code>, as this bash operator does not perform any escaping or
 sanitization of the command.</p>
-<p>This applies mostly to using “dag_run” conf, as that can be submitted via
+<p>This applies mostly to using &quot;dag_run&quot; conf, as that can be submitted via
 users in the Web UI. Most of the default template variables are not at
 risk.</p>
 </div>
@@ -818,7 +818,7 @@ as shown below:</p>
 </pre></div>
 </div>
 <p>Creating separate folder for bash scripts may be desirable for many reasons, like
-separating your script’s logic and pipeline code, allowing for proper code highlighting
+separating your script's logic and pipeline code, allowing for proper code highlighting
 in files composed in different languages, and general flexibility in structuring
 pipelines.</p>
 <p>It is also possible to define your <code class="docutils literal notranslate"><span class="pre">template_searchpath</span></code> as pointing to any folder
diff --git a/docs-archive/apache-airflow/2.3.0/howto/operator/external_task_sensor.html b/docs-archive/apache-airflow/2.3.0/howto/operator/external_task_sensor.html
index 8cc1fb7b3..9bf38d1e1 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/operator/external_task_sensor.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/operator/external_task_sensor.html
@@ -754,7 +754,7 @@ via <code class="docutils literal notranslate"><span class="pre">allowed_states<
 <h2>ExternalTaskMarker<a class="headerlink" href="#externaltaskmarker" title="Permalink to this headline">¶</a></h2>
 <p>If it is desirable that whenever <code class="docutils literal notranslate"><span class="pre">parent_task</span></code> on <code class="docutils literal notranslate"><span class="pre">parent_dag</span></code> is cleared, <code class="docutils literal notranslate"><span class="pre">child_task1</span></code>
 on <code class="docutils literal notranslate"><span class="pre">child_dag</span></code> for a specific <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> should also be cleared, <code class="docutils literal notranslate"><span class="pre">ExternalTaskMarker</span></code>
-should be used. Note that <code class="docutils literal notranslate"><span class="pre">child_task1</span></code> will only be cleared if “Recursive” is selected when the
+should be used. Note that <code class="docutils literal notranslate"><span class="pre">child_task1</span></code> will only be cleared if &quot;Recursive&quot; is selected when the
 user clears <code class="docutils literal notranslate"><span class="pre">parent_task</span></code>.</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/example_external_task_marker_dag.py</span><a class="example-header-button viewcode-button reference internal" href="../../_modules/airflow/example_dags/example_external_task_marker_dag.html"><span class="viewcode-link">[source]</span></a></p>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/operator/python.html b/docs-archive/apache-airflow/2.3.0/howto/operator/python.html
index 916afb5c4..af9988ea3 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/operator/python.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/operator/python.html
@@ -810,7 +810,7 @@ Python callables inside a new Python virtual environment.</p>
 Unfortunately we currently do not support to serialize <code class="docutils literal notranslate"><span class="pre">var</span></code> and <code class="docutils literal notranslate"><span class="pre">ti</span></code> / <code class="docutils literal notranslate"><span class="pre">task_instance</span></code> due to incompatibilities
 with the underlying library. For Airflow context variables make sure that you either have access to Airflow through
 setting <code class="docutils literal notranslate"><span class="pre">system_site_packages</span></code> to <code class="docutils literal notranslate"><span class="pre">True</span></code> or add <code class="docutils literal notranslate"><span class="pre">apache-airflow</span></code> to the <code class="docutils literal notranslate"><span class="pre">requirements</span></code> argument.
-Otherwise you won’t have access to the most context variables of Airflow in <code class="docutils literal notranslate"><span class="pre">op_kwargs</span></code>.
+Otherwise you won't have access to the most context variables of Airflow in <code class="docutils literal notranslate"><span class="pre">op_kwargs</span></code>.
 If you want the context related to datetime objects like <code class="docutils literal notranslate"><span class="pre">data_interval_start</span></code> you can add <code class="docutils literal notranslate"><span class="pre">pendulum</span></code> and
 <code class="docutils literal notranslate"><span class="pre">lazy_object_proxy</span></code>.</p>
 <p>If additional parameters for package installation are needed pass them in <code class="docutils literal notranslate"><span class="pre">requirements.txt</span></code> as in the example below:</p>
@@ -828,8 +828,8 @@ if a condition is satisfied or a truthy value is obtained. The evaluation of thi
 is done via the output of a <code class="docutils literal notranslate"><span class="pre">python_callable</span></code>. If the <code class="docutils literal notranslate"><span class="pre">python_callable</span></code> returns True or a truthy value,
 the pipeline is allowed to continue and an <a class="reference internal" href="../../concepts/xcoms.html#concepts-xcom"><span class="std std-ref">XCom</span></a> of the output will be pushed. If the
 output is False or a falsy value, the pipeline will be short-circuited based on the configured
-short-circuiting (more on this later). In the example below, the tasks that follow the “condition_is_True”
-ShortCircuitOperator will execute while the tasks downstream of the “condition_is_False” ShortCircuitOperator
+short-circuiting (more on this later). In the example below, the tasks that follow the &quot;condition_is_True&quot;
+ShortCircuitOperator will execute while the tasks downstream of the &quot;condition_is_False&quot; ShortCircuitOperator
 will be skipped.</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/example_short_circuit_operator.py</span><a class="example-header-button viewcode-button reference internal" href="../../_modules/airflow/example_dags/example_short_circuit_operator.html"><span class="viewcode-link">[source]</span></a></p>
@@ -851,7 +851,7 @@ will be skipped.</p>
 </pre></div>
 </div>
 </div>
-<p>The “short-circuiting” can be configured to either respect or ignore the <a class="reference internal" href="../../concepts/dags.html#concepts-trigger-rules"><span class="std std-ref">trigger rule</span></a>
+<p>The &quot;short-circuiting&quot; can be configured to either respect or ignore the <a class="reference internal" href="../../concepts/dags.html#concepts-trigger-rules"><span class="std std-ref">trigger rule</span></a>
 defined for downstream tasks. If <code class="docutils literal notranslate"><span class="pre">ignore_downstream_trigger_rules</span></code> is set to True, the default configuration, all
 downstream tasks are skipped without considering the <code class="docutils literal notranslate"><span class="pre">trigger_rule</span></code> defined for tasks.  If this parameter is
 set to False, the direct downstream tasks are skipped but the specified <code class="docutils literal notranslate"><span class="pre">trigger_rule</span></code> for other subsequent
@@ -860,8 +860,8 @@ downstream task(s) were purposely meant to be skipped but perhaps not other subs
 configuration is especially useful if only <em>part</em> of a pipeline should be short-circuited rather than all
 tasks which follow the ShortCircuitOperator task.</p>
 <p>In the example below, notice that the ShortCircuitOperator task is configured to respect downstream trigger
-rules. This means while the tasks that follow the “short_circuit” ShortCircuitOperator task will be skipped
-since the <code class="docutils literal notranslate"><span class="pre">python_callable</span></code> returns False, “task_7” will still execute as its set to execute when upstream
+rules. This means while the tasks that follow the &quot;short_circuit&quot; ShortCircuitOperator task will be skipped
+since the <code class="docutils literal notranslate"><span class="pre">python_callable</span></code> returns False, &quot;task_7&quot; will still execute as its set to execute when upstream
 tasks have completed running regardless of status (i.e. the <code class="docutils literal notranslate"><span class="pre">TriggerRule.ALL_DONE</span></code> trigger rule).</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/example_short_circuit_operator.py</span><a class="example-header-button viewcode-button reference internal" href="../../_modules/airflow/example_dags/example_short_circuit_operator.html"><span class="viewcode-link">[source]</span></a></p>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/set-config.html b/docs-archive/apache-airflow/2.3.0/howto/set-config.html
index 513e79b13..60cb49f8f 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/set-config.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/set-config.html
@@ -685,7 +685,7 @@
 <div class="section" id="setting-configuration-options">
 <h1>Setting Configuration Options<a class="headerlink" href="#setting-configuration-options" title="Permalink to this headline">¶</a></h1>
 <p>The first time you run Airflow, it will create a file called <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> in
-your <code class="docutils literal notranslate"><span class="pre">$AIRFLOW_HOME</span></code> directory (<code class="docutils literal notranslate"><span class="pre">~/airflow</span></code> by default). This file contains Airflow’s configuration and you
+your <code class="docutils literal notranslate"><span class="pre">$AIRFLOW_HOME</span></code> directory (<code class="docutils literal notranslate"><span class="pre">~/airflow</span></code> by default). This file contains Airflow's configuration and you
 can edit it to change any of the settings. You can also set options with environment variables by using this format:
 <span class="target" id="index-0"></span><a class="reference internal" href="../cli-and-env-variables-ref.html#envvar-AIRFLOW__-SECTION-__-KEY"><code class="xref std std-envvar docutils literal notranslate"><span class="pre">AIRFLOW__{SECTION}__{KEY}</span></code></a> (note the double underscores).</p>
 <p>For example, the metadata database connection string can either be set in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> like this:</p>
@@ -748,11 +748,11 @@ For example:</p>
 <li><p>set in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code></p></li>
 <li><p>command in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code></p></li>
 <li><p>secret key in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code></p></li>
-<li><p>Airflow’s built in defaults</p></li>
+<li><p>Airflow's built in defaults</p></li>
 </ol>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>For Airflow versions &gt;= 2.2.1, &lt; 2.3.0 Airflow’s built in defaults took precedence
+<p>For Airflow versions &gt;= 2.2.1, &lt; 2.3.0 Airflow's built in defaults took precedence
 over command and secret key in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> in some circumstances.</p>
 </div>
 <p>You can check the current configuration with the <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">config</span> <span class="pre">list</span></code> command.</p>
@@ -779,7 +779,7 @@ should be same on the Webserver and Worker to allow Webserver to fetch logs from
 <p>The webserver key is also used to authorize requests to Celery workers when logs are retrieved. The token
 generated using the secret key has a short expiry time though - make sure that time on ALL the machines
 that you run airflow components on is synchronized (for example using ntpd) otherwise you might get
-“forbidden” errors when the logs are accessed.</p>
+&quot;forbidden&quot; errors when the logs are accessed.</p>
 </div>
 </div>
 
diff --git a/docs-archive/apache-airflow/2.3.0/howto/set-up-database.html b/docs-archive/apache-airflow/2.3.0/howto/set-up-database.html
index 36783bada..d929cd514 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/set-up-database.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/set-up-database.html
@@ -347,7 +347,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#setting-up-a-mssql-database">Setting up a MsSQL Database</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#other-configuration-options">Other configuration options</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#initialize-the-database">Initialize the database</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#what-s-next">What’s next?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#what-s-next">What's next?</a></li>
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="operator/index.html">Using Operators</a></li>
@@ -546,7 +546,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#setting-up-a-mssql-database">Setting up a MsSQL Database</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#other-configuration-options">Other configuration options</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#initialize-the-database">Initialize the database</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#what-s-next">What’s next?</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#what-s-next">What's next?</a></li>
 </ul>
 </li>
 <li class="toctree-l2"><a class="reference internal" href="operator/index.html">Using Operators</a></li>
@@ -746,7 +746,7 @@ sqlite:////tmp/airflow/airflow.db
 it only works with Sequential Executor) and it should NEVER be used for production.</p>
 <p>There is a minimum version of sqlite3 required to run Airflow 2.0+ - minimum version is 3.15.0. Some of the
 older systems have an earlier version of sqlite installed by default and for those system you need to manually
-upgrade SQLite to use version newer than 3.15.0. Note, that this is not a <code class="docutils literal notranslate"><span class="pre">python</span> <span class="pre">library</span></code> version, it’s the
+upgrade SQLite to use version newer than 3.15.0. Note, that this is not a <code class="docutils literal notranslate"><span class="pre">python</span> <span class="pre">library</span></code> version, it's the
 SQLite system-level application that needs to be upgraded. There are different ways how SQLIte might be
 installed, you can find some information about that at the <a class="reference external" href="https://www.sqlite.org/index.html">official website of SQLite</a> and in the documentation specific to distribution of your Operating
 System.</p>
@@ -766,7 +766,7 @@ Type <span class="s2">&quot;help&quot;</span>, <span class="s2">&quot;copyright&
 </pre></div>
 </div>
 <p>But be aware that setting environment variables for your Airflow deployment might change which SQLite
-library is found first, so you might want to make sure that the “high-enough” version of SQLite is the only
+library is found first, so you might want to make sure that the &quot;high-enough&quot; version of SQLite is the only
 version installed in your system.</p>
 <p>An example URI for the sqlite database:</p>
 <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>sqlite:////home/airflow/airflow.db
@@ -845,7 +845,7 @@ SQLAlchemy 1.4.0+ results in:</p>
 <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>postgresql+psycopg2://&lt;user&gt;:&lt;password&gt;@&lt;host&gt;/&lt;db&gt;
 </pre></div>
 </div>
-<p>Also note that since SqlAlchemy does not expose a way to target a specific schema in the database URI, you need to ensure schema <code class="docutils literal notranslate"><span class="pre">public</span></code> is in your Postgres user’s search_path.</p>
+<p>Also note that since SqlAlchemy does not expose a way to target a specific schema in the database URI, you need to ensure schema <code class="docutils literal notranslate"><span class="pre">public</span></code> is in your Postgres user's search_path.</p>
 <p>If you created a new Postgres account for Airflow:</p>
 <ul class="simple">
 <li><p>The default search_path for new Postgres user is: <code class="docutils literal notranslate"><span class="pre">&quot;$user&quot;,</span> <span class="pre">public</span></code>, no change is needed.</p></li>
@@ -924,7 +924,7 @@ without any cert options provided.</p>
 </div>
 <p>However if you want to use other drivers visit the <a class="reference external" href="https://docs.sqlalchemy.org/en/13/dialects/mysql.html">MySQL Dialect</a>  in SQLAlchemy documentation for more information regarding download
 and setup of the SqlAlchemy connection.</p>
-<p>In addition, you also should pay particular attention to MySQL’s encoding. Although the <code class="docutils literal notranslate"><span class="pre">utf8mb4</span></code> character set is more and more popular for MySQL (actually, <code class="docutils literal notranslate"><span class="pre">utf8mb4</span></code> becomes default character set in MySQL8.0), using the <code class="docutils literal notranslate"><span class="pre">utf8mb4</span></code> encoding requires additional setting i [...]
+<p>In addition, you also should pay particular attention to MySQL's encoding. Although the <code class="docutils literal notranslate"><span class="pre">utf8mb4</span></code> character set is more and more popular for MySQL (actually, <code class="docutils literal notranslate"><span class="pre">utf8mb4</span></code> becomes default character set in MySQL8.0), using the <code class="docutils literal notranslate"><span class="pre">utf8mb4</span></code> encoding requires additional setting i [...]
 </div>
 <div class="section" id="setting-up-a-mssql-database">
 <h2>Setting up a MsSQL Database<a class="headerlink" href="#setting-up-a-mssql-database" title="Permalink to this headline">¶</a></h2>
@@ -971,7 +971,7 @@ Official Docker image we have ODBC driver installed, so you need to specify the
 </div>
 </div>
 <div class="section" id="what-s-next">
-<h2>What’s next?<a class="headerlink" href="#what-s-next" title="Permalink to this headline">¶</a></h2>
+<h2>What's next?<a class="headerlink" href="#what-s-next" title="Permalink to this headline">¶</a></h2>
 <p>By default, Airflow uses <code class="docutils literal notranslate"><span class="pre">SequentialExecutor</span></code>, which does not provide parallelism. You should consider
 configuring a different <a class="reference internal" href="../executor/index.html"><span class="doc">executor</span></a> for better performance.</p>
 </div>
@@ -1061,7 +1061,7 @@ configuring a different <a class="reference internal" href="../executor/index.ht
 <li><a class="reference internal" href="#setting-up-a-mssql-database">Setting up a MsSQL Database</a></li>
 <li><a class="reference internal" href="#other-configuration-options">Other configuration options</a></li>
 <li><a class="reference internal" href="#initialize-the-database">Initialize the database</a></li>
-<li><a class="reference internal" href="#what-s-next">What’s next?</a></li>
+<li><a class="reference internal" href="#what-s-next">What's next?</a></li>
 </ul>
 </li>
 </ul>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/timetable.html b/docs-archive/apache-airflow/2.3.0/howto/timetable.html
index 56a16d31a..82220ba3d 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/timetable.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/timetable.html
@@ -698,15 +698,15 @@
 <div></div></blockquote>
 <div class="section" id="customizing-dag-scheduling-with-timetables">
 <h1>Customizing DAG Scheduling with Timetables<a class="headerlink" href="#customizing-dag-scheduling-with-timetables" title="Permalink to this headline">¶</a></h1>
-<p>For our example, let’s say a company wants to run a job after each weekday to
+<p>For our example, let's say a company wants to run a job after each weekday to
 process data collected during the work day. The first intuitive answer to this
 would be <code class="docutils literal notranslate"><span class="pre">schedule_interval=&quot;0</span> <span class="pre">0</span> <span class="pre">*</span> <span class="pre">*</span> <span class="pre">1-5&quot;</span></code> (midnight on Monday to Friday), but
 this means data collected on Friday will <em>not</em> be processed right after Friday
-ends, but on the next Monday, and that run’s interval would be from midnight
+ends, but on the next Monday, and that run's interval would be from midnight
 Friday to midnight <em>Monday</em>. What we want is:</p>
 <ul class="simple">
 <li><p>Schedule a run for each Monday, Tuesday, Wednesday, Thursday, and Friday. The
-run’s data interval would cover from midnight of each day, to midnight of the
+run's data interval would cover from midnight of each day, to midnight of the
 next day (e.g. 2021-01-01 00:00:00 to 2021-01-02 00:00:00).</p></li>
 <li><p>Each run would be created right after the data interval ends. The run covering
 Monday happens on midnight Tuesday and so on. The run covering Friday happens
@@ -715,8 +715,8 @@ on midnight Saturday. No runs happen on midnights Sunday and Monday.</p></li>
 <p>For simplicity, we will only deal with UTC datetimes in this example.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>All datetime values returned by a custom timetable <strong>MUST</strong> be “aware”, i.e.
-contains timezone information. Furthermore, they must use <code class="docutils literal notranslate"><span class="pre">pendulum</span></code>’s
+<p>All datetime values returned by a custom timetable <strong>MUST</strong> be &quot;aware&quot;, i.e.
+contains timezone information. Furthermore, they must use <code class="docutils literal notranslate"><span class="pre">pendulum</span></code>'s
 datetime and timezone types.</p>
 </div>
 <div class="section" id="timetable-registration">
@@ -737,7 +737,7 @@ skeleton for us to implement a new timetable:</p>
     <span class="n">timetables</span> <span class="o">=</span> <span class="p">[</span><span class="n">AfterWorkdayTimetable</span><span class="p">]</span>
 </pre></div>
 </div>
-<p>Next, we’ll start putting code into <code class="docutils literal notranslate"><span class="pre">AfterWorkdayTimetable</span></code>. After the
+<p>Next, we'll start putting code into <code class="docutils literal notranslate"><span class="pre">AfterWorkdayTimetable</span></code>. After the
 implementation is finished, we should be able to use the timetable in our DAG
 file:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">import</span> <span class="nn">pendulum</span>
@@ -758,17 +758,17 @@ file:</p>
 </div>
 <div class="section" id="define-scheduling-logic">
 <h2>Define Scheduling Logic<a class="headerlink" href="#define-scheduling-logic" title="Permalink to this headline">¶</a></h2>
-<p>When Airflow’s scheduler encounters a DAG, it calls one of the two methods to
-know when to schedule the DAG’s next run.</p>
+<p>When Airflow's scheduler encounters a DAG, it calls one of the two methods to
+know when to schedule the DAG's next run.</p>
 <ul class="simple">
-<li><p><code class="docutils literal notranslate"><span class="pre">next_dagrun_info</span></code>: The scheduler uses this to learn the timetable’s regular
-schedule, i.e. the “one for every workday, run at the end of it” part in our
+<li><p><code class="docutils literal notranslate"><span class="pre">next_dagrun_info</span></code>: The scheduler uses this to learn the timetable's regular
+schedule, i.e. the &quot;one for every workday, run at the end of it&quot; part in our
 example.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">infer_manual_data_interval</span></code>: When a DAG run is manually triggered (from the web
 UI, for example), the scheduler uses this method to learn about how to
-reverse-infer the out-of-schedule run’s data interval.</p></li>
+reverse-infer the out-of-schedule run's data interval.</p></li>
 </ul>
-<p>We’ll start with <code class="docutils literal notranslate"><span class="pre">infer_manual_data_interval</span></code> since it’s the easier of the two:</p>
+<p>We'll start with <code class="docutils literal notranslate"><span class="pre">infer_manual_data_interval</span></code> since it's the easier of the two:</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/plugins/workday.py</span><a class="example-header-button viewcode-button reference internal" href="../_modules/airflow/example_dags/plugins/workday.html"><span class="viewcode-link">[source]</span></a></p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">infer_manual_data_interval</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">run_after</span><span class="p">:</span> <span class="n">DateTime</span><span class="p">)</span> <span class="o">-&gt;</span> <span class="n">DataInterval</span><span class="p">:</span>
@@ -834,7 +834,7 @@ interval.</p>
 </div>
 <p>This method accepts two arguments. <code class="docutils literal notranslate"><span class="pre">last_automated_dagrun</span></code> is a
 <a class="reference internal" href="../_api/airflow/timetables/base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><code class="xref py py-class docutils literal notranslate"><span class="pre">DataInterval</span></code></a> instance indicating the data
-interval of this DAG’s previous non-manually-triggered run, or <code class="docutils literal notranslate"><span class="pre">None</span></code> if this
+interval of this DAG's previous non-manually-triggered run, or <code class="docutils literal notranslate"><span class="pre">None</span></code> if this
 is the first time ever the DAG is being scheduled. <code class="docutils literal notranslate"><span class="pre">restriction</span></code> encapsulates
 how the DAG and its tasks specify the schedule, and contains three attributes:</p>
 <ul class="simple">
@@ -844,21 +844,21 @@ the DAG and its tasks, or <code class="docutils literal notranslate"><span class
 found at all.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">latest</span></code>: Similar to <code class="docutils literal notranslate"><span class="pre">earliest</span></code>, this is the latest time the DAG may be
 scheduled, calculated from <code class="docutils literal notranslate"><span class="pre">end_date</span></code> arguments.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">catchup</span></code>: A boolean reflecting the DAG’s <code class="docutils literal notranslate"><span class="pre">catchup</span></code> argument.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">catchup</span></code>: A boolean reflecting the DAG's <code class="docutils literal notranslate"><span class="pre">catchup</span></code> argument.</p></li>
 </ul>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>Both <code class="docutils literal notranslate"><span class="pre">earliest</span></code> and <code class="docutils literal notranslate"><span class="pre">latest</span></code> apply to the DAG run’s logical date
+<p>Both <code class="docutils literal notranslate"><span class="pre">earliest</span></code> and <code class="docutils literal notranslate"><span class="pre">latest</span></code> apply to the DAG run's logical date
 (the <em>start</em> of the data interval), not when the run will be scheduled
 (usually after the end of the data interval).</p>
 </div>
 <p>If there was a run scheduled previously, we should now schedule for the next
 weekday, i.e. plus one day if the previous run was on Monday through Thursday,
 or three days if it was on Friday. If there was not a previous scheduled run,
-however, we pick the next workday’s midnight after <code class="docutils literal notranslate"><span class="pre">restriction.earliest</span></code>
-(unless it <em>is</em> a workday’s midnight; in which case it’s used directly).
-<code class="docutils literal notranslate"><span class="pre">restriction.catchup</span></code> also needs to be considered—if it’s <code class="docutils literal notranslate"><span class="pre">False</span></code>, we
-can’t schedule before the current time, even if <code class="docutils literal notranslate"><span class="pre">start_date</span></code> values are in the
+however, we pick the next workday's midnight after <code class="docutils literal notranslate"><span class="pre">restriction.earliest</span></code>
+(unless it <em>is</em> a workday's midnight; in which case it's used directly).
+<code class="docutils literal notranslate"><span class="pre">restriction.catchup</span></code> also needs to be considered---if it's <code class="docutils literal notranslate"><span class="pre">False</span></code>, we
+can't schedule before the current time, even if <code class="docutils literal notranslate"><span class="pre">start_date</span></code> values are in the
 past. Finally, if our calculated data interval is later than
 <code class="docutils literal notranslate"><span class="pre">restriction.latest</span></code>, we must respect it and not schedule a run by returning
 <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p>
@@ -867,7 +867,7 @@ past. Finally, if our calculated data interval is later than
 attributes:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">data_interval</span></code>: A <a class="reference internal" href="../_api/airflow/timetables/base/index.html#airflow.timetables.base.DataInterval" title="airflow.timetables.base.DataInterval"><code class="xref py py-class docutils literal notranslate"><span class="pre">DataInterval</span></code></a> instance
-describing the next run’s data interval.</p></li>
+describing the next run's data interval.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">run_after</span></code>: A <code class="docutils literal notranslate"><span class="pre">pendulum.DateTime</span></code> instance that tells the scheduler when
 the DAG run can be scheduled.</p></li>
 </ul>
@@ -885,7 +885,7 @@ provides a shortcut for this:</p>
 <span class="k">assert</span> <span class="n">info</span><span class="o">.</span><span class="n">data_interval</span><span class="o">.</span><span class="n">end</span> <span class="o">==</span> <span class="n">info</span><span class="o">.</span><span class="n">run_after</span>  <span class="c1"># Always True.</span>
 </pre></div>
 </div>
-<p>For reference, here’s our plugin and DAG files in their entirety:</p>
+<p>For reference, here's our plugin and DAG files in their entirety:</p>
 <div class="example-block-wrapper docutils container">
 <p class="example-header example-header--with-button"><span class="example-title">airflow/example_dags/plugins/workday.py</span><a class="example-header-button viewcode-button reference internal" href="../_modules/airflow/example_dags/plugins/workday.html"><span class="viewcode-link">[source]</span></a></p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">datetime</span> <span class="kn">import</span> <span class="n">timedelta</span>
@@ -972,7 +972,7 @@ provides a shortcut for this:</p>
 with our <code class="docutils literal notranslate"><span class="pre">AfterWorkdayTimetable</span></code> example, maybe we have DAGs running on
 different timezones, and we want to schedule some DAGs at 8am the next day,
 instead of on midnight. Instead of creating a separate timetable for each
-purpose, we’d want to do something like:</p>
+purpose, we'd want to do something like:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">SometimeAfterWorkdayTimetable</span><span class="p">(</span><span class="n">Timetable</span><span class="p">):</span>
     <span class="k">def</span> <span class="fm">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">schedule_at</span><span class="p">:</span> <span class="n">Time</span><span class="p">)</span> <span class="o">-&gt;</span> <span class="kc">None</span><span class="p">:</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">_schedule_at</span> <span class="o">=</span> <span class="n">schedule_at</span>
@@ -1007,7 +1007,7 @@ serialized DAG is accessed by the scheduler to reconstruct the timetable.</p>
 <div class="section" id="timetable-display-in-ui">
 <h2>Timetable Display in UI<a class="headerlink" href="#timetable-display-in-ui" title="Permalink to this headline">¶</a></h2>
 <p>By default, a custom timetable is displayed by their class name in the UI (e.g.
-the <em>Schedule</em> column in the “DAGs” table). It is possible to customize this
+the <em>Schedule</em> column in the &quot;DAGs&quot; table). It is possible to customize this
 by overriding the <code class="docutils literal notranslate"><span class="pre">summary</span></code> property. This is especially useful for
 parameterized timetables to include arguments provided in <code class="docutils literal notranslate"><span class="pre">__init__</span></code>. For
 our <code class="docutils literal notranslate"><span class="pre">SometimeAfterWorkdayTimetable</span></code> class, for example, we could have:</p>
diff --git a/docs-archive/apache-airflow/2.3.0/howto/use-test-config.html b/docs-archive/apache-airflow/2.3.0/howto/use-test-config.html
index 5fde8ef07..5b54c4a66 100644
--- a/docs-archive/apache-airflow/2.3.0/howto/use-test-config.html
+++ b/docs-archive/apache-airflow/2.3.0/howto/use-test-config.html
@@ -684,7 +684,7 @@
 <div></div></blockquote>
 <div class="section" id="using-the-test-mode-configuration">
 <h1>Using the Test Mode Configuration<a class="headerlink" href="#using-the-test-mode-configuration" title="Permalink to this headline">¶</a></h1>
-<p>Airflow has a fixed set of “test mode” configuration options. You can load these
+<p>Airflow has a fixed set of &quot;test mode&quot; configuration options. You can load these
 at any time by calling <code class="docutils literal notranslate"><span class="pre">airflow.configuration.load_test_config()</span></code>. Please <strong>note</strong> that this
 operation is <strong>not reversible</strong>.</p>
 <p>Some options for example, <code class="docutils literal notranslate"><span class="pre">DAG_FOLDER</span></code>, are loaded before you have a chance to call <code class="docutils literal notranslate"><span class="pre">load_test_config()</span></code>.
@@ -693,7 +693,7 @@ In order to eagerly load the test configuration, set <code class="docutils liter
 <span class="na">unit_test_mode</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">True</span><span class="w"></span>
 </pre></div>
 </div>
-<p>Due to Airflow’s automatic environment variable expansion (see <a class="reference internal" href="set-config.html"><span class="doc">Setting Configuration Options</span></a>), you can also set the
+<p>Due to Airflow's automatic environment variable expansion (see <a class="reference internal" href="set-config.html"><span class="doc">Setting Configuration Options</span></a>), you can also set the
 environment variable <code class="docutils literal notranslate"><span class="pre">AIRFLOW__CORE__UNIT_TEST_MODE</span></code> to temporarily overwrite <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code>.</p>
 </div>
 
diff --git a/docs-archive/apache-airflow/2.3.0/installation/dependencies.html b/docs-archive/apache-airflow/2.3.0/installation/dependencies.html
index 73ea09461..2a3306d72 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/dependencies.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/dependencies.html
@@ -688,12 +688,12 @@
 <h1>Dependencies<a class="headerlink" href="#dependencies" title="Permalink to this headline">¶</a></h1>
 <div class="section" id="airflow-extra-dependencies">
 <h2>Airflow extra dependencies<a class="headerlink" href="#airflow-extra-dependencies" title="Permalink to this headline">¶</a></h2>
-<p>The <code class="docutils literal notranslate"><span class="pre">apache-airflow</span></code> PyPI basic package only installs what’s needed to get started.
+<p>The <code class="docutils literal notranslate"><span class="pre">apache-airflow</span></code> PyPI basic package only installs what's needed to get started.
 Additional packages can be installed depending on what will be useful in your
-environment. For instance, if you don’t need connectivity with Postgres,
-you won’t have to go through the trouble of installing the <code class="docutils literal notranslate"><span class="pre">postgres-devel</span></code>
+environment. For instance, if you don't need connectivity with Postgres,
+you won't have to go through the trouble of installing the <code class="docutils literal notranslate"><span class="pre">postgres-devel</span></code>
 yum package, or whatever equivalent applies on the distribution you are using.</p>
-<p>Most of the extra dependencies are linked to a corresponding provider package. For example “amazon” extra
+<p>Most of the extra dependencies are linked to a corresponding provider package. For example &quot;amazon&quot; extra
 has a corresponding <code class="docutils literal notranslate"><span class="pre">apache-airflow-providers-amazon</span></code> provider package to be installed. When you install
 Airflow with such extras, the necessary provider packages are installed automatically (latest versions from
 PyPI for those packages). However you can freely upgrade and install provider packages independently from
@@ -705,7 +705,7 @@ the main Airflow installation.</p>
 <p>Unlike Apache Airflow 1.10, the Airflow 2.0 is delivered in multiple, separate, but connected packages.
 The core of Airflow scheduling system is delivered as <code class="docutils literal notranslate"><span class="pre">apache-airflow</span></code> package and there are around
 60 provider packages which can be installed separately as so called <code class="docutils literal notranslate"><span class="pre">Airflow</span> <span class="pre">Provider</span> <span class="pre">packages</span></code>.
-The default Airflow installation doesn’t have many integrations and you have to install them yourself.</p>
+The default Airflow installation doesn't have many integrations and you have to install them yourself.</p>
 <p>You can even develop and install your own providers for Airflow. For more information,
 see: <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span>Provider packages</span></a></p>
 <p>For the list of the provider packages and what they enable, see: <a class="reference external" href="/docs/apache-airflow-providers/packages-ref.html" title="(in apache-airflow-providers vdevel)"><span>Providers packages reference</span></a>.</p>
@@ -715,7 +715,7 @@ see: <a class="reference external" href="/docs/apache-airflow-providers/index.ht
 <p>Just to prevent confusion of extras versus provider packages: Extras and providers are different things,
 though many extras are leading to installing providers.</p>
 <p>Extras are standard Python setuptools feature that allows to add additional set of dependencies as
-optional features to “core” Apache Airflow. One of the type of such optional features are providers
+optional features to &quot;core&quot; Apache Airflow. One of the type of such optional features are providers
 packages, but not all optional features of Apache Airflow have corresponding providers.</p>
 <p>We are using the <code class="docutils literal notranslate"><span class="pre">extras</span></code> setuptools features to also install provider packages.
 Most of the extras are also linked (same name) with provider packages - for example adding <code class="docutils literal notranslate"><span class="pre">[google]</span></code>
@@ -724,7 +724,7 @@ not install providers (examples <code class="docutils literal notranslate"><span
 dependencies which are needed for those <code class="docutils literal notranslate"><span class="pre">extra</span></code> features of Airflow mentioned. The three examples
 above add respectively GitHub Enterprise OAuth authentication, Kerberos integration or
 asynchronous workers for Gunicorn. None of those have providers, they are just extending Apache Airflow
-“core” package with new functionalities.</p>
+&quot;core&quot; package with new functionalities.</p>
 </div>
 <div class="section" id="system-dependencies">
 <h2>System dependencies<a class="headerlink" href="#system-dependencies" title="Permalink to this headline">¶</a></h2>
diff --git a/docs-archive/apache-airflow/2.3.0/installation/installing-from-pypi.html b/docs-archive/apache-airflow/2.3.0/installation/installing-from-pypi.html
index d1fc81497..8b3cbc1a7 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/installing-from-pypi.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/installing-from-pypi.html
@@ -731,10 +731,10 @@ and both at the same time. We decided to keep our dependencies as open as possib
 (in <code class="docutils literal notranslate"><span class="pre">setup.cfg</span></code> and <code class="docutils literal notranslate"><span class="pre">setup.py</span></code>) so users can install different
 version of libraries if needed. This means that from time to time plain <code class="docutils literal notranslate"><span class="pre">pip</span> <span class="pre">install</span> <span class="pre">apache-airflow</span></code> will
 not work or will produce an unusable Airflow installation.</p>
-<p>In order to have a repeatable installation, we also keep a set of “known-to-be-working” constraint files in the
+<p>In order to have a repeatable installation, we also keep a set of &quot;known-to-be-working&quot; constraint files in the
 <code class="docutils literal notranslate"><span class="pre">constraints-main</span></code>, <code class="docutils literal notranslate"><span class="pre">constraints-2-0</span></code>, <code class="docutils literal notranslate"><span class="pre">constraints-2-1</span></code> etc. orphan branches and then we create a tag
 for each released version e.g. <code class="code docutils literal notranslate"><span class="pre">constraints-2.3.0</span></code>. This way, we keep a tested and working set of dependencies.</p>
-<p>Those “known-to-be-working” constraints are per major/minor Python version. You can use them as constraint
+<p>Those &quot;known-to-be-working&quot; constraints are per major/minor Python version. You can use them as constraint
 files when installing Airflow from PyPI. Note that you have to specify the correct Airflow
 and Python versions in the URL.</p>
 <p>You can create the URL to the file substituting the variables in the template below.</p>
@@ -752,8 +752,8 @@ to install and upgrade airflow separately and independently from providers.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span>https://raw.githubusercontent.com/apache/airflow/constraints-${AIRFLOW_VERSION}/constraints-no-providers-${PYTHON_VERSION}.txt
 </pre></div>
 </div>
-<p>You can also use “latest” as version when you install “latest” stable version of Airflow. The “latest”
-constraints always points to the “latest” released Airflow version constraints:</p>
+<p>You can also use &quot;latest&quot; as version when you install &quot;latest&quot; stable version of Airflow. The &quot;latest&quot;
+constraints always points to the &quot;latest&quot; released Airflow version constraints:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">raw</span><span class="o">.</span><span class="n">githubusercontent</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">apache</span><span class="o">/</span><span class="n">airflow</span><span class="o">/</span><span class="n">constraints</span><span class="o">-</span><s [...]
 </pre></div>
 </div>
@@ -788,12 +788,12 @@ pip install <span class="s2">&quot;apache-airflow[postgres,google]==</span><span
 </div>
 <div class="section" id="installation-and-upgrading-of-airflow-providers-separately">
 <h3>Installation and upgrading of Airflow providers separately<a class="headerlink" href="#installation-and-upgrading-of-airflow-providers-separately" title="Permalink to this headline">¶</a></h3>
-<p>You can manually install all the providers you need. You can continue using the “providers” constraint files
-but the ‘versioned’ airflow constraints installs only the versions of providers that were available in PyPI at
-the time of preparing of the airflow version. However, usually you can use “main” version of the providers
+<p>You can manually install all the providers you need. You can continue using the &quot;providers&quot; constraint files
+but the 'versioned' airflow constraints installs only the versions of providers that were available in PyPI at
+the time of preparing of the airflow version. However, usually you can use &quot;main&quot; version of the providers
 to install latest version of providers. Usually the providers work with most versions of Airflow, if there
 will be any incompatibilities, it will be captured as package dependencies.</p>
-<p>Note that “main” is just an example - you might need to choose a specific airflow version to install providers
+<p>Note that &quot;main&quot; is just an example - you might need to choose a specific airflow version to install providers
 in specific version.</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="nv">PYTHON_VERSION</span><span class="o">=</span><span class="s2">&quot;</span><span class="k">$(</span>python --version <span class="p">|</span> cut -d <span class="s2">&quot; &quot;</span> -f <span class="m">2</span> <span class="p">|</span> cut -d <span class="s2">&quot;.&quot;</span> -f <span class="m">1</span>-2<span class="k">)</span><span class="s2">&quot;</span>
 <span class="c1"># For example: 3.6</span>
@@ -811,7 +811,7 @@ pip install <span class="s2">&quot;apache-airflow-providers-google&quot;</span>
 </div>
 <div class="section" id="installation-and-upgrade-of-airflow-core">
 <h3>Installation and upgrade of Airflow core<a class="headerlink" href="#installation-and-upgrade-of-airflow-core" title="Permalink to this headline">¶</a></h3>
-<p>If you don’t want to install any extra providers, initially you can use the command set below.</p>
+<p>If you don't want to install any extra providers, initially you can use the command set below.</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="nv">AIRFLOW_VERSION</span><span class="o">=</span><span class="m">2</span>.3.0
 <span class="nv">PYTHON_VERSION</span><span class="o">=</span><span class="s2">&quot;</span><span class="k">$(</span>python --version <span class="p">|</span> cut -d <span class="s2">&quot; &quot;</span> -f <span class="m">2</span> <span class="p">|</span> cut -d <span class="s2">&quot;.&quot;</span> -f <span class="m">1</span>-2<span class="k">)</span><span class="s2">&quot;</span>
 <span class="c1"># For example: 3.6</span>
diff --git a/docs-archive/apache-airflow/2.3.0/installation/installing-from-sources.html b/docs-archive/apache-airflow/2.3.0/installation/installing-from-sources.html
index 9c753aad5..e145c912d 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/installing-from-sources.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/installing-from-sources.html
@@ -691,7 +691,7 @@
 You can also install <code class="docutils literal notranslate"><span class="pre">Apache</span> <span class="pre">Airflow</span></code> - as most Python packages - via <a class="reference internal" href="installing-from-pypi.html"><span class="doc">PyPI</span></a>.
 You can choose different version of Airflow by selecting different version from the drop-down at
 the top-left of the page.</p>
-<p>The <code class="docutils literal notranslate"><span class="pre">source</span></code>, <code class="docutils literal notranslate"><span class="pre">sdist</span></code> and <code class="docutils literal notranslate"><span class="pre">whl</span></code> packages released are the “official” sources of installation that you
+<p>The <code class="docutils literal notranslate"><span class="pre">source</span></code>, <code class="docutils literal notranslate"><span class="pre">sdist</span></code> and <code class="docutils literal notranslate"><span class="pre">whl</span></code> packages released are the &quot;official&quot; sources of installation that you
 can use if you want to verify the origin of the packages and want to verify checksums and signatures of
 the packages. The packages are available via the
 <a class="reference external" href="http://ws.apache.org/mirrors.cgi">Official Apache Software Foundations Downloads</a></p>
@@ -747,9 +747,9 @@ distribution directory and follow the below guide.</p>
 <span class="go">  Primary key fingerprint: CDE1 5C6E 4D3A 8EC4 ECF4  BA4B 6674 E08A D7DE 406F</span>
 </pre></div>
 </div>
-<p>The “Good signature from …” is indication that the signatures are correct.
-Do not worry about the “not certified with a trusted signature” warning. Most of the certificates used
-by release managers are self signed, that’s why you get this warning. By importing the server in the
+<p>The &quot;Good signature from ...&quot; is indication that the signatures are correct.
+Do not worry about the &quot;not certified with a trusted signature&quot; warning. Most of the certificates used
+by release managers are self signed, that's why you get this warning. By importing the server in the
 previous step and importing it via ID from <code class="docutils literal notranslate"><span class="pre">KEYS</span></code> page, you know that this is a valid Key already.</p>
 <p>For SHA512 sum check, download the relevant <code class="docutils literal notranslate"><span class="pre">sha512</span></code> and run the following:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>shasum -a <span class="m">512</span> apache-airflow--********  <span class="p">|</span> diff - apache-airflow--********.sha512
diff --git a/docs-archive/apache-airflow/2.3.0/installation/prerequisites.html b/docs-archive/apache-airflow/2.3.0/installation/prerequisites.html
index bd5c87cfe..b72d0da76 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/prerequisites.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/prerequisites.html
@@ -688,7 +688,7 @@
 <li><p>Kubernetes: 1.20.2 1.21.1 1.22.0, 1.23.0</p></li>
 </ul>
 <p><strong>Note:</strong> MySQL 5.x versions are unable to or have limitations with
-running multiple schedulers – please see: <a class="reference internal" href="../concepts/scheduler.html"><span class="doc">Scheduler</span></a>. MariaDB is not tested/recommended.</p>
+running multiple schedulers -- please see: <a class="reference internal" href="../concepts/scheduler.html"><span class="doc">Scheduler</span></a>. MariaDB is not tested/recommended.</p>
 <p><strong>Note:</strong> SQLite is used in Airflow tests. Do not use it in production. We recommend
 using the latest stable version of SQLite for local development.</p>
 <p><strong>Note</strong>: Python v3.10 is not supported yet. For details, see <a class="reference external" href="https://github.com/apache/airflow/issues/19059">#19059</a>.</p>
@@ -699,7 +699,7 @@ wildly on the deployment options you have</p>
 tested on fairly modern Linux Distros and recent versions of MacOS.
 On Windows you can run it via WSL2 (Windows Subsystem for Linux 2) or via Linux Containers.
 The work to add Windows support is tracked via <a class="reference external" href="https://github.com/apache/airflow/issues/10388">#10388</a> but
-it is not a high priority. You should only use Linux-based distros as “Production” execution environment
+it is not a high priority. You should only use Linux-based distros as &quot;Production&quot; execution environment
 as this is the only environment that is supported. The only distro that is used in our CI tests and that
 is used in the <a class="reference external" href="https://hub.docker.com/p/apache/airflow">Community managed DockerHub image</a> is
 <code class="docutils literal notranslate"><span class="pre">Debian</span> <span class="pre">Bullseye</span></code>.</p>
diff --git a/docs-archive/apache-airflow/2.3.0/installation/setting-up-the-database.html b/docs-archive/apache-airflow/2.3.0/installation/setting-up-the-database.html
index bb8770a7f..0d9ce68f8 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/setting-up-the-database.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/setting-up-the-database.html
@@ -674,8 +674,8 @@
 <div></div></blockquote>
 <div class="section" id="setting-up-the-database">
 <h1>Setting up the database<a class="headerlink" href="#setting-up-the-database" title="Permalink to this headline">¶</a></h1>
-<p>Airflow requires a database. If you’re just experimenting and learning Airflow, you can stick with the
-default SQLite option. If you don’t want to use SQLite, then take a look at
+<p>Airflow requires a database. If you're just experimenting and learning Airflow, you can stick with the
+default SQLite option. If you don't want to use SQLite, then take a look at
 <a class="reference internal" href="../howto/set-up-database.html"><span class="doc">Set up a Database Backend</span></a> to setup a different database.</p>
 <p>Usually, you need to run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">db</span> <span class="pre">upgrade</span></code> in order to create the database schema that Airflow can use.</p>
 <p>Similarly, upgrading Airflow usually requires an extra step of upgrading the database. This is done
diff --git a/docs-archive/apache-airflow/2.3.0/installation/supported-versions.html b/docs-archive/apache-airflow/2.3.0/installation/supported-versions.html
index 6798af933..5402f12fb 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/supported-versions.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/supported-versions.html
@@ -753,7 +753,7 @@ We <strong>highly</strong> recommend installing the latest Airflow release which
 <h2>Support for Python and Kubernetes versions<a class="headerlink" href="#support-for-python-and-kubernetes-versions" title="Permalink to this headline">¶</a></h2>
 <p>As of Airflow 2.0 we agreed to certain rules we follow for Python and Kubernetes support.
 They are based on the official release schedule of Python and Kubernetes, nicely summarized in the
-<a class="reference external" href="https://devguide.python.org/#status-of-python-branches">Python Developer’s Guide</a> and
+<a class="reference external" href="https://devguide.python.org/#status-of-python-branches">Python Developer's Guide</a> and
 <a class="reference external" href="https://kubernetes.io/docs/setup/release/version-skew-policy">Kubernetes version skew policy</a>.</p>
 <ol class="arabic simple">
 <li><p>We drop support for Python and Kubernetes versions when they reach EOL. We drop support for those
@@ -761,8 +761,8 @@ EOL versions in main right after EOL date, and it is effectively removed when we
 first new MINOR (Or MAJOR if there is no new MINOR version) of Airflow
 For example for Python 3.6 it means that we drop support in main right after 23.12.2021, and the first
 MAJOR or MINOR version of Airflow released after will not have it.</p></li>
-<li><p>The “oldest” supported version of Python/Kubernetes is the default one. “Default” is only meaningful
-in terms of “smoke tests” in CI PRs which are run using this default version and default reference
+<li><p>The &quot;oldest&quot; supported version of Python/Kubernetes is the default one. &quot;Default&quot; is only meaningful
+in terms of &quot;smoke tests&quot; in CI PRs which are run using this default version and default reference
 image available in DockerHub. Currently <code class="docutils literal notranslate"><span class="pre">apache/airflow:latest</span></code> and <code class="docutils literal notranslate"><span class="pre">apache/airflow:2.0.2</span></code> images
 are both Python 3.6 images, however the first MINOR/MAJOR release of Airflow release after 23.12.2021 will
 become Python 3.7 images.</p></li>
diff --git a/docs-archive/apache-airflow/2.3.0/installation/upgrading.html b/docs-archive/apache-airflow/2.3.0/installation/upgrading.html
index 0c96b293d..67ff06c05 100644
--- a/docs-archive/apache-airflow/2.3.0/installation/upgrading.html
+++ b/docs-archive/apache-airflow/2.3.0/installation/upgrading.html
@@ -694,7 +694,7 @@
 <h2>Why you need to upgrade<a class="headerlink" href="#why-you-need-to-upgrade" title="Permalink to this headline">¶</a></h2>
 <p>Newer Airflow versions can contain database migrations so you must run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">db</span> <span class="pre">upgrade</span></code>
 to upgrade your database with the schema changes in the Airflow version you are upgrading to.
-Don’t worry, it’s safe to run even if there are no migrations to perform.</p>
+Don't worry, it's safe to run even if there are no migrations to perform.</p>
 </div>
 <div class="section" id="when-you-need-to-upgrade">
 <h2>When you need to upgrade<a class="headerlink" href="#when-you-need-to-upgrade" title="Permalink to this headline">¶</a></h2>
@@ -727,7 +727,7 @@ from Airflow 2.0.0 onward and in MSSQL from Airflow 2.2.0 onward.</p>
 <h2>Migration best practices<a class="headerlink" href="#migration-best-practices" title="Permalink to this headline">¶</a></h2>
 <p>Depending on the size of your database and the actual migration it might take quite some time to migrate it,
 so if you have long history and big database, it is recommended to make a copy of the database first and
-perform a test migration to assess how long the migration will take. Typically “Major” upgrades might take
+perform a test migration to assess how long the migration will take. Typically &quot;Major&quot; upgrades might take
 longer as adding new features require sometimes restructuring of the database.</p>
 </div>
 <div class="section" id="post-upgrade-warnings">
@@ -750,7 +750,7 @@ choose to store it somewhere. Unless you have specific reasons to keep the data
 is your best option.</p>
 <p>There are various ways you can inspect and delete the data - if you have direct access to the
 database using your own tools (often graphical tools showing the database objects), you can drop such
-table or rename it or move it to another database using those tools. If you don’t have such tools you
+table or rename it or move it to another database using those tools. If you don't have such tools you
 can use the <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">db</span> <span class="pre">shell</span></code> command - this will drop you in the db shell tool for your database and you
 will be able to both inspect and delete the table.</p>
 <p>How to drop the table using Kubernetes:</p>
diff --git a/docs-archive/apache-airflow/2.3.0/lineage.html b/docs-archive/apache-airflow/2.3.0/lineage.html
index e42dee2f9..ef965950d 100644
--- a/docs-archive/apache-airflow/2.3.0/lineage.html
+++ b/docs-archive/apache-airflow/2.3.0/lineage.html
@@ -656,7 +656,7 @@
 </div>
 <p>Airflow can help track origins of data, what happens to it and where it moves over time. This can aid having
 audit trails and data governance, but also debugging of data flows.</p>
-<p>Airflow tracks data by means of inlets and outlets of the tasks. Let’s work from an example and see how it
+<p>Airflow tracks data by means of inlets and outlets of the tasks. Let's work from an example and see how it
 works.</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">import</span> <span class="nn">datetime</span>
 <span class="kn">import</span> <span class="nn">pendulum</span>
@@ -722,7 +722,7 @@ has outlets defined (e.g. by using <code class="docutils literal notranslate"><s
 </div>
 <div class="section" id="lineage-backend">
 <h2>Lineage Backend<a class="headerlink" href="#lineage-backend" title="Permalink to this headline">¶</a></h2>
-<p>It’s possible to push the lineage metrics to a custom backend by providing an instance of a LineageBackend in the config:</p>
+<p>It's possible to push the lineage metrics to a custom backend by providing an instance of a LineageBackend in the config:</p>
 <div class="highlight-ini notranslate"><div class="highlight"><pre><span></span><span class="k">[lineage]</span><span class="w"></span>
 <span class="na">backend</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">my.lineage.CustomBackend</span><span class="w"></span>
 </pre></div>
diff --git a/docs-archive/apache-airflow/2.3.0/logging-monitoring/check-health.html b/docs-archive/apache-airflow/2.3.0/logging-monitoring/check-health.html
index bd4f62cd5..a12834813 100644
--- a/docs-archive/apache-airflow/2.3.0/logging-monitoring/check-health.html
+++ b/docs-archive/apache-airflow/2.3.0/logging-monitoring/check-health.html
@@ -699,7 +699,7 @@ For the webserver, you can configure the readiness probe (<code class="docutils
 </pre></div>
 </div>
 <ul class="simple">
-<li><p>The <code class="docutils literal notranslate"><span class="pre">status</span></code> of each component can be either “healthy” or “unhealthy”</p>
+<li><p>The <code class="docutils literal notranslate"><span class="pre">status</span></code> of each component can be either &quot;healthy&quot; or &quot;unhealthy&quot;</p>
 <ul>
 <li><p>The status of <code class="docutils literal notranslate"><span class="pre">metadatabase</span></code> depends on whether a valid connection can be initiated with the database</p></li>
 <li><p>The status of <code class="docutils literal notranslate"><span class="pre">scheduler</span></code> depends on when the latest scheduler heartbeat was received</p>
diff --git a/docs-archive/apache-airflow/2.3.0/logging-monitoring/metrics.html b/docs-archive/apache-airflow/2.3.0/logging-monitoring/metrics.html
index 08f92b79b..6adeb846a 100644
--- a/docs-archive/apache-airflow/2.3.0/logging-monitoring/metrics.html
+++ b/docs-archive/apache-airflow/2.3.0/logging-monitoring/metrics.html
@@ -842,7 +842,7 @@ fully asynchronous)</p></td>
 </thead>
 <tbody>
 <tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">dagbag_size</span></code></p></td>
-<td><p>Number of DAGs found when the scheduler ran a scan based on it’s
+<td><p>Number of DAGs found when the scheduler ran a scan based on it's
 configuration</p></td>
 </tr>
 <tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">dag_processing.import_errors</span></code></p></td>
@@ -943,7 +943,7 @@ and priority.</p></td>
 start date and the actual DagRun start date</p></td>
 </tr>
 <tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">scheduler.critical_section_duration</span></code></p></td>
-<td><p>Milliseconds spent in the critical section of scheduler loop –
+<td><p>Milliseconds spent in the critical section of scheduler loop --
 only a single scheduler can enter this loop at a time</p></td>
 </tr>
 <tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">dagrun.&lt;dag_id&gt;.first_task_scheduling_delay</span></code></p></td>
diff --git a/docs-archive/apache-airflow/2.3.0/logging-monitoring/tracking-user-activity.html b/docs-archive/apache-airflow/2.3.0/logging-monitoring/tracking-user-activity.html
index 66cb0492b..c8d65cbc0 100644
--- a/docs-archive/apache-airflow/2.3.0/logging-monitoring/tracking-user-activity.html
+++ b/docs-archive/apache-airflow/2.3.0/logging-monitoring/tracking-user-activity.html
@@ -674,7 +674,7 @@
 </div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>You can see view injected tracker html within Airflow’s source code at
+<p>You can see view injected tracker html within Airflow's source code at
 <code class="docutils literal notranslate"><span class="pre">airflow/www/templates/airflow/main.html</span></code>. The related global
 variables are set in <code class="docutils literal notranslate"><span class="pre">airflow/www/templates/app.py</span></code>.</p>
 </div>
diff --git a/docs-archive/apache-airflow/2.3.0/migrations-ref.html b/docs-archive/apache-airflow/2.3.0/migrations-ref.html
index 8754228f9..588acd2a8 100644
--- a/docs-archive/apache-airflow/2.3.0/migrations-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/migrations-ref.html
@@ -641,7 +641,7 @@
 <div></div></blockquote>
 <div class="section" id="reference-for-database-migrations">
 <h1>Reference for Database Migrations<a class="headerlink" href="#reference-for-database-migrations" title="Permalink to this headline">¶</a></h1>
-<p>Here’s the list of all the Database Migrations that are executed via when you run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">db</span> <span class="pre">upgrade</span></code>:</p>
+<p>Here's the list of all the Database Migrations that are executed via when you run <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">db</span> <span class="pre">upgrade</span></code>:</p>
 <blockquote>
 <div></div></blockquote>
 <table class="docutils align-default">
@@ -1085,7 +1085,7 @@ table</p></td>
 <tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">d2ae31099d61</span></code> (branch_point)</p></td>
 <td><p><code class="docutils literal notranslate"><span class="pre">947454bf1dff</span></code></p></td>
 <td><p><code class="docutils literal notranslate"><span class="pre">1.8.2</span></code></p></td>
-<td><p>Increase text size for MySQL (not relevant for other DBs’
+<td><p>Increase text size for MySQL (not relevant for other DBs'
 text types)</p></td>
 </tr>
 <tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">947454bf1dff</span></code></p></td>
@@ -1151,7 +1151,7 @@ text types)</p></td>
 <tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">bba5a7cfc896</span></code></p></td>
 <td><p><code class="docutils literal notranslate"><span class="pre">bbc73705a13e</span></code></p></td>
 <td><p><code class="docutils literal notranslate"><span class="pre">1.7.0</span></code></p></td>
-<td><p>Add a column to track the encryption state of the ‘Extra’
+<td><p>Add a column to track the encryption state of the 'Extra'
 field in connection</p></td>
 </tr>
 <tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">bbc73705a13e</span></code></p></td>
diff --git a/docs-archive/apache-airflow/2.3.0/modules_management.html b/docs-archive/apache-airflow/2.3.0/modules_management.html
index 21fd17204..0076d5383 100644
--- a/docs-archive/apache-airflow/2.3.0/modules_management.html
+++ b/docs-archive/apache-airflow/2.3.0/modules_management.html
@@ -19,7 +19,7 @@
             <link rel="shortcut icon" href="_static/pin_32.png"/>
             <link rel="index" title="Index" href="genindex.html" />
             <link rel="search" title="Search" href="search.html" />
-            <link rel="next" title="Airflow’s release process and version policy" href="release-process.html" />
+            <link rel="next" title="Airflow&#39;s release process and version policy" href="release-process.html" />
             <link rel="prev" title="DAG Serialization" href="dag-serialization.html" />
     <!-- Matomo -->
     <script>
@@ -356,7 +356,7 @@
 <li class="toctree-l2"><a class="reference internal" href="#built-in-pythonpath-entries-in-airflow">Built-in <code class="docutils literal notranslate"><span class="pre">PYTHONPATH</span></code> entries in Airflow</a></li>
 <li class="toctree-l2"><a class="reference internal" href="#best-practices-for-module-loading">Best practices for module loading</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#use-unique-top-package-name">Use unique top package name</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#don-t-use-relative-imports">Don’t use relative imports</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#don-t-use-relative-imports">Don't use relative imports</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#add-init-py-in-package-folders">Add <code class="docutils literal notranslate"><span class="pre">__init__.py</span></code> in package folders</a></li>
 </ul>
 </li>
@@ -538,7 +538,7 @@
 <li class="toctree-l2"><a class="reference internal" href="#built-in-pythonpath-entries-in-airflow">Built-in <code class="docutils literal notranslate"><span class="pre">PYTHONPATH</span></code> entries in Airflow</a></li>
 <li class="toctree-l2"><a class="reference internal" href="#best-practices-for-module-loading">Best practices for module loading</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#use-unique-top-package-name">Use unique top package name</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#don-t-use-relative-imports">Don’t use relative imports</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#don-t-use-relative-imports">Don't use relative imports</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#add-init-py-in-package-folders">Add <code class="docutils literal notranslate"><span class="pre">__init__.py</span></code> in package folders</a></li>
 </ul>
 </li>
@@ -712,7 +712,7 @@ followed by installation-dependent default paths which is managed by
 <a class="reference external" href="https://docs.python.org/3/library/site.html#module-site">site</a> module.</p>
 <p><code class="docutils literal notranslate"><span class="pre">sys.path</span></code> can also be modified during a Python session by simply using append
 (for example, <code class="docutils literal notranslate"><span class="pre">sys.path.append(&quot;/path/to/custom/package&quot;)</span></code>). Python will start
-searching for packages in the newer paths once they’re added. Airflow makes use
+searching for packages in the newer paths once they're added. Airflow makes use
 of this feature as described in the section
 <a class="reference internal" href="#adding-directories-to-pythonpath"><span class="std std-ref">Adding directories to the PYTHONPATH</span></a>.</p>
 <p>In the variable <code class="docutils literal notranslate"><span class="pre">sys.path</span></code> there is a directory <code class="docutils literal notranslate"><span class="pre">site-packages</span></code> which
@@ -780,7 +780,7 @@ my_company/my_custom_dags/base_dag.py
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>The DAGS folder in Airflow 2 should not be shared with the webserver. While you can do it, unlike in Airflow 1.10,
-Airflow has no expectations that the DAGS folder is present in the webserver. In fact it’s a bit of
+Airflow has no expectations that the DAGS folder is present in the webserver. In fact it's a bit of
 security risk to share the <code class="docutils literal notranslate"><span class="pre">dags</span></code> folder with the webserver, because it means that people who write DAGS
 can write code that the webserver will be able to execute (ideally the webserver should
 never run code which can be modified by users who write DAGs). Therefore if you need to share some code
@@ -803,7 +803,7 @@ create <code class="docutils literal notranslate"><span class="pre">airflow/oper
 named <code class="docutils literal notranslate"><span class="pre">airflow.operators</span></code> and it will look there when importing <code class="docutils literal notranslate"><span class="pre">from</span> <span class="pre">airflow.operators</span></code>.</p>
 </div>
 <div class="section" id="don-t-use-relative-imports">
-<h3>Don’t use relative imports<a class="headerlink" href="#don-t-use-relative-imports" title="Permalink to this headline">¶</a></h3>
+<h3>Don't use relative imports<a class="headerlink" href="#don-t-use-relative-imports" title="Permalink to this headline">¶</a></h3>
 <p>Never use relative imports (starting with <code class="docutils literal notranslate"><span class="pre">.</span></code>) that were added in Python 3.</p>
 <p>This is tempting to do something like that it in <code class="docutils literal notranslate"><span class="pre">my_dag1.py</span></code>:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">.base_dag</span> <span class="kn">import</span> <span class="n">BaseDag</span>  <span class="c1"># NEVER DO THAT!!!!</span>
@@ -907,7 +907,7 @@ the path to root of your project using the following command:</p>
 <span class="go"> &#39;/home/arch/venvs/airflow/lib/python3.7/site-packages&#39;]</span>
 </pre></div>
 </div>
-<p>As we can see that our provided directory is now added to the path, let’s
+<p>As we can see that our provided directory is now added to the path, let's
 try to import the package now:</p>
 <div class="highlight-pycon notranslate"><div class="highlight"><pre><span></span><span class="gp">&gt;&gt;&gt; </span><span class="kn">import</span> <span class="nn">airflow_operators</span>
 <span class="go">Hello from airflow_operators</span>
@@ -919,7 +919,7 @@ For example, if we run the following airflow command:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="nv">PYTHONPATH</span><span class="o">=</span>/home/arch/projects/airflow_operators airflow info
 </pre></div>
 </div>
-<p>We’ll see the <code class="docutils literal notranslate"><span class="pre">Python</span> <span class="pre">PATH</span></code> updated with our mentioned <span class="target" id="index-4"></span><a class="reference external" href="https://docs.python.org/3/using/cmdline.html#envvar-PYTHONPATH" title="(in Python v3.10)"><code class="xref std std-envvar docutils literal notranslate"><span class="pre">PYTHONPATH</span></code></a>
+<p>We'll see the <code class="docutils literal notranslate"><span class="pre">Python</span> <span class="pre">PATH</span></code> updated with our mentioned <span class="target" id="index-4"></span><a class="reference external" href="https://docs.python.org/3/using/cmdline.html#envvar-PYTHONPATH" title="(in Python v3.10)"><code class="xref std std-envvar docutils literal notranslate"><span class="pre">PYTHONPATH</span></code></a>
 value as shown below:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>Python PATH: [/home/arch/venv/bin:/home/arch/projects/airflow_operators:/usr/lib/python38.zip:/usr/lib/python3.8:/usr/lib/python3.8/lib-dynload:/home/arch/venv/lib/python3.8/site-packages:/home/arch/airflow/dags:/home/arch/airflow/config:/home/arch/airflow/plugins]
 </pre></div>
@@ -1021,7 +1021,7 @@ see <a class="reference external" href="https://packaging.python.org/tutorials/p
             <a rel="prev" title="DAG Serialization" href="dag-serialization.html" >
                 <button class="btn-hollow btn-blue bodytext__medium--cerulean-blue" accesskey="p">Previous</button>
             </a>
-            <a rel="next" title="Airflow’s release process and version policy" href="release-process.html" >
+            <a rel="next" title="Airflow&#39;s release process and version policy" href="release-process.html" >
                 <button class="btn-hollow btn-blue bodytext__medium--cerulean-blue" accesskey="n">Next</button>
             </a>
     </div>
@@ -1097,7 +1097,7 @@ see <a class="reference external" href="https://packaging.python.org/tutorials/p
 <li><a class="reference internal" href="#built-in-pythonpath-entries-in-airflow">Built-in <code class="docutils literal notranslate"><span class="pre">PYTHONPATH</span></code> entries in Airflow</a></li>
 <li><a class="reference internal" href="#best-practices-for-module-loading">Best practices for module loading</a><ul>
 <li><a class="reference internal" href="#use-unique-top-package-name">Use unique top package name</a></li>
-<li><a class="reference internal" href="#don-t-use-relative-imports">Don’t use relative imports</a></li>
+<li><a class="reference internal" href="#don-t-use-relative-imports">Don't use relative imports</a></li>
 <li><a class="reference internal" href="#add-init-py-in-package-folders">Add <code class="docutils literal notranslate"><span class="pre">__init__.py</span></code> in package folders</a></li>
 </ul>
 </li>
diff --git a/docs-archive/apache-airflow/2.3.0/objects.inv b/docs-archive/apache-airflow/2.3.0/objects.inv
index 49749172a..76e2c5214 100644
Binary files a/docs-archive/apache-airflow/2.3.0/objects.inv and b/docs-archive/apache-airflow/2.3.0/objects.inv differ
diff --git a/docs-archive/apache-airflow/2.3.0/operators-and-hooks-ref.html b/docs-archive/apache-airflow/2.3.0/operators-and-hooks-ref.html
index e5a44c832..a4ef134d2 100644
--- a/docs-archive/apache-airflow/2.3.0/operators-and-hooks-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/operators-and-hooks-ref.html
@@ -642,7 +642,7 @@
 <div></div></blockquote>
 <div class="section" id="operators-and-hooks-reference">
 <h1>Operators and Hooks Reference<a class="headerlink" href="#operators-and-hooks-reference" title="Permalink to this headline">¶</a></h1>
-<p>Here’s the list of the operators and hooks which are available in this release in the <code class="docutils literal notranslate"><span class="pre">apache-airflow</span></code> package.</p>
+<p>Here's the list of the operators and hooks which are available in this release in the <code class="docutils literal notranslate"><span class="pre">apache-airflow</span></code> package.</p>
 <p>Airflow has many more integrations available for separate installation as
 <a class="reference external" href="/docs/apache-airflow-providers/index.html" title="(in apache-airflow-providers vdevel)"><span>Provider packages</span></a>.</p>
 <p>For details see: <a class="reference external" href="/docs/apache-airflow-providers/operators-and-hooks-ref/index.html" title="(in apache-airflow-providers vdevel)"><span>Operators and Hooks Reference</span></a>.</p>
diff --git a/docs-archive/apache-airflow/2.3.0/plugins.html b/docs-archive/apache-airflow/2.3.0/plugins.html
index 01d6fab30..2c27ff983 100644
--- a/docs-archive/apache-airflow/2.3.0/plugins.html
+++ b/docs-archive/apache-airflow/2.3.0/plugins.html
@@ -668,7 +668,7 @@
 features to its core by simply dropping files in your
 <code class="docutils literal notranslate"><span class="pre">$AIRFLOW_HOME/plugins</span></code> folder.</p>
 <p>The python modules in the <code class="docutils literal notranslate"><span class="pre">plugins</span></code> folder get imported, and <strong>macros</strong> and web <strong>views</strong>
-get integrated to Airflow’s main collections and become available for use.</p>
+get integrated to Airflow's main collections and become available for use.</p>
 <p>To troubleshoot issues with plugins, you can use the <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">plugins</span></code> command.
 This command dumps information about loaded plugins.</p>
 <div class="versionchanged">
@@ -685,16 +685,16 @@ plugins can be a way for companies to customize their Airflow installation
 to reflect their ecosystem.</p>
 <p>Plugins can be used as an easy way to write, share and activate new sets of
 features.</p>
-<p>There’s also a need for a set of more complex applications to interact with
+<p>There's also a need for a set of more complex applications to interact with
 different flavors of data and metadata.</p>
 <p>Examples:</p>
 <ul class="simple">
-<li><p>A set of tools to parse Hive logs and expose Hive metadata (CPU /IO / phases/ skew /…)</p></li>
+<li><p>A set of tools to parse Hive logs and expose Hive metadata (CPU /IO / phases/ skew /...)</p></li>
 <li><p>An anomaly detection framework, allowing people to collect metrics, set thresholds and alerts</p></li>
 <li><p>An auditing tool, helping understand who accesses what</p></li>
 <li><p>A config-driven SLA monitoring tool, allowing you to set monitored tables and at what time
 they should land, alert people, and expose visualizations of outages</p></li>
-<li><p>…</p></li>
+<li><p>...</p></li>
 </ul>
 </div>
 <div class="section" id="why-build-on-top-of-airflow">
@@ -717,7 +717,7 @@ start of each Airflow process, set <code class="docutils literal notranslate"><s
 <p>This means that if you make any changes to plugins and you want the webserver or scheduler to use that new
 code you will need to restart those processes.</p>
 <p>By default, task execution will use forking to avoid the slow down of having to create a whole new python
-interpreter and re-parse all of the Airflow code and start up routines – this is a big benefit for shorter
+interpreter and re-parse all of the Airflow code and start up routines -- this is a big benefit for shorter
 running tasks. This does mean that if you use plugins in your tasks, and want them to update you will either
 need to restart the worker (if using CeleryExecutor) or scheduler (Local or Sequential executors). The other
 option is you can accept the speed hit at start up set the <code class="docutils literal notranslate"><span class="pre">core.execute_tasks_new_python_interpreter</span></code>
@@ -729,7 +729,7 @@ loaded/parsed in any long-running Airflow process.)</p>
 <span id="plugins-interface"></span><h2>Interface<a class="headerlink" href="#interface" title="Permalink to this headline">¶</a></h2>
 <p>To create a plugin you will need to derive the
 <code class="docutils literal notranslate"><span class="pre">airflow.plugins_manager.AirflowPlugin</span></code> class and reference the objects
-you want to plug into Airflow. Here’s what the class you need to derive
+you want to plug into Airflow. Here's what the class you need to derive
 looks like:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="k">class</span> <span class="nc">AirflowPlugin</span><span class="p">:</span>
     <span class="c1"># The name of your plugin (str)</span>
diff --git a/docs-archive/apache-airflow/2.3.0/privacy_notice.html b/docs-archive/apache-airflow/2.3.0/privacy_notice.html
index f81363a84..08f6e8c89 100644
--- a/docs-archive/apache-airflow/2.3.0/privacy_notice.html
+++ b/docs-archive/apache-airflow/2.3.0/privacy_notice.html
@@ -666,7 +666,7 @@
 <div class="section" id="privacy-faq">
 <h2>Privacy FAQ<a class="headerlink" href="#privacy-faq" title="Permalink to this headline">¶</a></h2>
 <p><strong>What is Google Analytics?</strong></p>
-<p>Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with website content. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen, for example the URL of the page. The Google Analytics JavaScript libraries use HTTP Cookies to “remember” what a user has done on previous pages / interactions with the website. It makes it easy for websit [...]
+<p>Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with website content. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen, for example the URL of the page. The Google Analytics JavaScript libraries use HTTP Cookies to &quot;remember&quot; what a user has done on previous pages / interactions with the website. It makes it easy  [...]
 <p><strong>Why do we use GA?</strong></p>
 <p>We use GA solely to gather the information that helps to make the site more useful to visitors and contributors, as well as to better understand how and when our site is used. We DO NOT track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.</p>
 <p><strong>What information is being collected?</strong></p>
diff --git a/docs-archive/apache-airflow/2.3.0/production-deployment.html b/docs-archive/apache-airflow/2.3.0/production-deployment.html
index d5228ac9a..0303cc98a 100644
--- a/docs-archive/apache-airflow/2.3.0/production-deployment.html
+++ b/docs-archive/apache-airflow/2.3.0/production-deployment.html
@@ -677,7 +677,7 @@
 <div class="section" id="production-deployment">
 <h1>Production Deployment<a class="headerlink" href="#production-deployment" title="Permalink to this headline">¶</a></h1>
 <p>It is time to deploy your DAG in production. To do this, first, you need to make sure that the Airflow
-is itself production-ready. Let’s see what precautions you need to take.</p>
+is itself production-ready. Let's see what precautions you need to take.</p>
 <div class="section" id="database-backend">
 <h2>Database backend<a class="headerlink" href="#database-backend" title="Permalink to this headline">¶</a></h2>
 <p>Airflow comes with an <code class="docutils literal notranslate"><span class="pre">SQLite</span></code> backend by default. This allows the user to run Airflow without any external
@@ -691,12 +691,12 @@ such as PostgreSQL or MySQL.</p>
 </pre></div>
 </div>
 <p>Once you have changed the backend, airflow needs to create all the tables required for operation.
-Create an empty DB and give airflow’s user the permission to <code class="docutils literal notranslate"><span class="pre">CREATE/ALTER</span></code> it.
+Create an empty DB and give airflow's user the permission to <code class="docutils literal notranslate"><span class="pre">CREATE/ALTER</span></code> it.
 Once that is done, you can run -</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>airflow db upgrade
 </pre></div>
 </div>
-<p><code class="docutils literal notranslate"><span class="pre">upgrade</span></code> keeps track of migrations already applied, so it’s safe to run as often as you need.</p>
+<p><code class="docutils literal notranslate"><span class="pre">upgrade</span></code> keeps track of migrations already applied, so it's safe to run as often as you need.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Do not use <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">db</span> <span class="pre">init</span></code> as it can create a lot of default connections, charts, etc. which are not
@@ -712,7 +712,7 @@ the scheduler when it runs a task, hence it is not recommended in a production s
 For a multi-node setup, you should use the <a class="reference internal" href="executor/kubernetes.html"><span class="doc">Kubernetes executor</span></a> or
 the <a class="reference internal" href="executor/celery.html"><span class="doc">Celery executor</span></a>.</p>
 <p>Once you have configured the executor, it is necessary to make sure that every node in the cluster contains
-the same configuration and dags. Airflow sends simple instructions such as “execute task X of dag Y”, but
+the same configuration and dags. Airflow sends simple instructions such as &quot;execute task X of dag Y&quot;, but
 does not send any dag files or configuration. You can use a simple cronjob or any other mechanism to sync
 DAGs and configs across your nodes, e.g., checkout DAGs from git repo every 5 minutes on all nodes.</p>
 </div>
@@ -788,7 +788,7 @@ to the Google API.</p>
 <div class="section" id="iam-and-service-accounts">
 <h3>IAM and Service Accounts<a class="headerlink" href="#iam-and-service-accounts" title="Permalink to this headline">¶</a></h3>
 <p>You should not rely on internal network segmentation or firewalling as our primary security mechanisms.
-To protect your organization’s data, every request you make should contain sender identity. In the case of
+To protect your organization's data, every request you make should contain sender identity. In the case of
 Google Cloud, the identity is provided by
 <a class="reference external" href="https://cloud.google.com/iam/docs/service-accounts">the IAM and Service account</a>. Each Compute Engine
 instance has an associated service account identity. It provides cryptographic credentials that your workload
diff --git a/docs-archive/apache-airflow/2.3.0/project.html b/docs-archive/apache-airflow/2.3.0/project.html
index 4ab87a9a4..014d48c6e 100644
--- a/docs-archive/apache-airflow/2.3.0/project.html
+++ b/docs-archive/apache-airflow/2.3.0/project.html
@@ -657,7 +657,7 @@
 <p>Airflow was started in October 2014 by Maxime Beauchemin at Airbnb.
 It was open source from the very first commit and officially brought under
 the Airbnb GitHub and announced in June 2015.</p>
-<p>The project joined the Apache Software Foundation’s Incubator program in March 2016 and the
+<p>The project joined the Apache Software Foundation's Incubator program in March 2016 and the
 Foundation <a class="reference external" href="https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces44">announced Apache Airflow as a Top-Level Project</a>
 in January 2019.</p>
 </div>
@@ -695,12 +695,12 @@ in January 2019.</p>
 <li><p>Kengo Seki (&#64;sekikn)</p></li>
 <li><p>Kevin Yang (&#64;KevinYang21)</p></li>
 <li><p>Leah Cole (&#64;leahecole)</p></li>
-<li><p>Maxime “Max” Beauchemin (&#64;mistercrunch)</p></li>
+<li><p>Maxime &quot;Max&quot; Beauchemin (&#64;mistercrunch)</p></li>
 <li><p>Qian Yu (&#64;yuqian90)</p></li>
 <li><p>Qingping Hou (&#64;houqp)</p></li>
 <li><p>Ry Walker (&#64;ryw)</p></li>
 <li><p>Ryan Hamilton (&#64;ryanahamilton)</p></li>
-<li><p>Siddharth “Sid” Anand (&#64;r39132)</p></li>
+<li><p>Siddharth &quot;Sid&quot; Anand (&#64;r39132)</p></li>
 <li><p>Sumit Maheshwari (&#64;msumit)</p></li>
 <li><p>Tao Feng (&#64;feng-tao)</p></li>
 <li><p>Tomasz Urbaszek (&#64;turbaszek)</p></li>
@@ -709,16 +709,16 @@ in January 2019.</p>
 <li><p>Xiaodong Deng (&#64;XD-DENG)</p></li>
 <li><p>Xinbin Huang (&#64;xinbinhuang)</p></li>
 </ul>
-<p>For the full list of contributors, take a look at <a class="reference external" href="https://github.com/apache/airflow/graphs/contributors">Airflow’s GitHub
+<p>For the full list of contributors, take a look at <a class="reference external" href="https://github.com/apache/airflow/graphs/contributors">Airflow's GitHub
 Contributor page:</a></p>
 </div>
 <div class="section" id="resources-links">
 <h2>Resources &amp; links<a class="headerlink" href="#resources-links" title="Permalink to this headline">¶</a></h2>
 <ul class="simple">
-<li><p><a class="reference external" href="https://airflow.apache.org/docs/">Airflow’s official documentation</a></p></li>
+<li><p><a class="reference external" href="https://airflow.apache.org/docs/">Airflow's official documentation</a></p></li>
 <li><p>Mailing lists:</p>
 <ul>
-<li><p>Developer’s mailing list: <a class="reference external" href="mailto:dev-subscribe&#37;&#52;&#48;airflow&#46;apache&#46;org">dev-subscribe<span>&#64;</span>airflow<span>&#46;</span>apache<span>&#46;</span>org</a></p></li>
+<li><p>Developer's mailing list: <a class="reference external" href="mailto:dev-subscribe&#37;&#52;&#48;airflow&#46;apache&#46;org">dev-subscribe<span>&#64;</span>airflow<span>&#46;</span>apache<span>&#46;</span>org</a></p></li>
 <li><p>All commits mailing list: <a class="reference external" href="mailto:commits-subscribe&#37;&#52;&#48;airflow&#46;apache&#46;org">commits-subscribe<span>&#64;</span>airflow<span>&#46;</span>apache<span>&#46;</span>org</a></p></li>
 <li><p>Airflow users mailing list: <a class="reference external" href="mailto:users-subscribe&#37;&#52;&#48;airflow&#46;apache&#46;org">users-subscribe<span>&#64;</span>airflow<span>&#46;</span>apache<span>&#46;</span>org</a></p></li>
 </ul>
diff --git a/docs-archive/apache-airflow/2.3.0/python-api-ref.html b/docs-archive/apache-airflow/2.3.0/python-api-ref.html
index a94dd5781..d79ead94e 100644
--- a/docs-archive/apache-airflow/2.3.0/python-api-ref.html
+++ b/docs-archive/apache-airflow/2.3.0/python-api-ref.html
@@ -730,7 +730,7 @@
 <h1>Python API Reference<a class="headerlink" href="#python-api-reference" title="Permalink to this headline">¶</a></h1>
 <div class="section" id="dags">
 <span id="pythonapi-dags"></span><h2>DAGs<a class="headerlink" href="#dags" title="Permalink to this headline">¶</a></h2>
-<p>The DAG is Airflow’s core model that represents a recurring workflow. Check out <a class="reference internal" href="_api/airflow/models/dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><code class="xref py py-class docutils literal notranslate"><span class="pre">DAG</span></code></a> for details.</p>
+<p>The DAG is Airflow's core model that represents a recurring workflow. Check out <a class="reference internal" href="_api/airflow/models/dag/index.html#airflow.models.dag.DAG" title="airflow.models.dag.DAG"><code class="xref py py-class docutils literal notranslate"><span class="pre">DAG</span></code></a> for details.</p>
 </div>
 <div class="section" id="operators">
 <span id="pythonapi-operators"></span><h2>Operators<a class="headerlink" href="#operators" title="Permalink to this headline">¶</a></h2>
@@ -752,7 +752,7 @@ method at a specified <code class="xref py py-attr docutils literal notranslate"
 <h3>BaseOperator<a class="headerlink" href="#baseoperator" title="Permalink to this headline">¶</a></h3>
 <p>All operators are derived from <code class="xref py py-class docutils literal notranslate"><span class="pre">BaseOperator</span></code> and acquire much
 functionality through inheritance. Since this is the core of the engine,
-it’s worth taking the time to understand the parameters of <code class="xref py py-class docutils literal notranslate"><span class="pre">BaseOperator</span></code>
+it's worth taking the time to understand the parameters of <code class="xref py py-class docutils literal notranslate"><span class="pre">BaseOperator</span></code>
 to understand the primitive features that can be leveraged in your
 DAGs.</p>
 </div>
@@ -832,7 +832,7 @@ All secrets backends derive from <code class="xref py py-class docutils literal
 </div>
 <div class="section" id="timetables">
 <h2>Timetables<a class="headerlink" href="#timetables" title="Permalink to this headline">¶</a></h2>
-<p>Custom timetable implementations provide Airflow’s scheduler additional logic to
+<p>Custom timetable implementations provide Airflow's scheduler additional logic to
 schedule DAG runs in ways not possible with built-in schedule expressions.</p>
 <div class="toctree-wrapper compound">
 <ul>
diff --git a/docs-archive/apache-airflow/2.3.0/release-process.html b/docs-archive/apache-airflow/2.3.0/release-process.html
index 31aca81dc..e95ff0abe 100644
--- a/docs-archive/apache-airflow/2.3.0/release-process.html
+++ b/docs-archive/apache-airflow/2.3.0/release-process.html
@@ -9,7 +9,7 @@
 <head>
         <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1">
-        <title>Airflow’s release process and version policy &mdash; Airflow Documentation</title>
+        <title>Airflow&#39;s release process and version policy &mdash; Airflow Documentation</title>
     <link rel="stylesheet" href="_static/_gen/css/main.min.css" type="text/css" />
             <link rel="stylesheet" type="text/css" href="_static/pygments.css" />
             <link rel="stylesheet" type="text/css" href="_static/_gen/css/main.min.css" />
@@ -635,7 +635,7 @@
         
             <li class="breadcrumb-item"><a href="index.html" class="icon icon-home"> Home</a></li>
             
-            <li class="breadcrumb-item"><a href="release-process.html"> Airflow’s release process and version policy</a></li>
+            <li class="breadcrumb-item"><a href="release-process.html"> Airflow's release process and version policy</a></li>
         
     </ul>
 </div>
@@ -649,7 +649,7 @@
   <blockquote>
 <div></div></blockquote>
 <div class="section" id="airflow-s-release-process-and-version-policy">
-<h1>Airflow’s release process and version policy<a class="headerlink" href="#airflow-s-release-process-and-version-policy" title="Permalink to this headline">¶</a></h1>
+<h1>Airflow's release process and version policy<a class="headerlink" href="#airflow-s-release-process-and-version-policy" title="Permalink to this headline">¶</a></h1>
 <p>Since Airflow 2.0.0 and provider packages 1.0.0 we aim to follow SemVer, meaning the release numbering works as follows:</p>
 <ul class="simple">
 <li><p>Versions are numbered in the form X.Y.Z.</p></li>
@@ -661,14 +661,14 @@ These are of the form X.Y.Z alpha/beta/rc N, which means the Nth alpha/beta/rele
 </ul>
 <p>In git, each minor version will have its own branch, called <code class="docutils literal notranslate"><span class="pre">vX-Y-stable</span></code> where bugfix/security releases will be issued from.
 Commits and PRs should not normally go direct to these branches, but instead should target the main branch and then be cherry-picked by the release managers to these release branches.</p>
-<p>Each Airflow release will also have a tag in git indicating its version number, signed with the release manager’s key.
+<p>Each Airflow release will also have a tag in git indicating its version number, signed with the release manager's key.
 Tags for the main Airflow release have the form <code class="docutils literal notranslate"><span class="pre">X.Y.Z</span></code> (no leading <code class="docutils literal notranslate"><span class="pre">v</span></code>) and provider packages are tagged with the form <code class="docutils literal notranslate"><span class="pre">providers-&lt;name&gt;/X.Y.Z</span></code>.</p>
 <p>Although Airflow follows SemVer this is not a promise of 100% compatibility between minor or patch releases, simply because this is not possible: what is a bug to one person might be a feature another person is depending on.</p>
 <blockquote>
-<div><p>Knowing the <em>intentions</em> of a maintainer can be valuable – especially <em>when</em> things break. Because that’s all SemVer is: <strong>a TL;DR of the changelog</strong>.</p>
+<div><p>Knowing the <em>intentions</em> of a maintainer can be valuable – especially <em>when</em> things break. Because that's all SemVer is: <strong>a TL;DR of the changelog</strong>.</p>
 <p class="attribution">—Hynek Schlawack <a class="reference external" href="https://hynek.me/articles/semver-will-not-save-you/">https://hynek.me/articles/semver-will-not-save-you/</a></p>
 </div></blockquote>
-<p>That is all SemVer is – it’s a statement of our intent as package authors, and a clear statement of our goals.</p>
+<p>That is all SemVer is -- it's a statement of our intent as package authors, and a clear statement of our goals.</p>
 <dl class="glossary">
 <dt id="term-Major-release">Major release<a class="headerlink" href="#term-Major-release" title="Permalink to this term">¶</a></dt><dd><p>Major releases (X.0.0, X+1.0.0 etc.) indicate a backwards-incompatible change.</p>
 <p>These releases do not happen with any regular interval or on any predictable schedule.</p>
@@ -679,7 +679,7 @@ These releases will contain new features, improvements to existing features, and
 </dd>
 <dt id="term-Patch-releases">Patch releases<a class="headerlink" href="#term-Patch-releases" title="Permalink to this term">¶</a></dt><dd><p>Patch releases (X.Y.Z, X.Y.Z+1, etc.) will happen, on an as-needed basis, as issues are reported and fixed.</p>
 <p>These releases will be 100% compatible with the associated feature release.
-So the answer to “should I upgrade to the latest patch release?” will always be “yes.”</p>
+So the answer to &quot;should I upgrade to the latest patch release?&quot; will always be &quot;yes.&quot;</p>
 <p>The only exception to the above with respect to 100% backwards compatibility is when a security or data loss issue can’t be fixed without breaking backwards-compatibility.
 If this happens, the release notes will provide detailed upgrade instructions.
 <strong>No new features will be added in patch releases</strong></p>
@@ -689,20 +689,20 @@ If this happens, the release notes will provide detailed upgrade instructions.
 <h2>Deprecation policy<a class="headerlink" href="#deprecation-policy" title="Permalink to this headline">¶</a></h2>
 <p>From time-to-time existing features will be deprecated, or modules will be renamed.</p>
 <p>When this happens, the existing code will continue to work but will issue a DeprecationWarning (or a subclass) when the code is executed.
-This code will continue to work for the rest of the current major version – if it works on 2.0.0, it will work for every 2.Y.Z release.</p>
+This code will continue to work for the rest of the current major version -- if it works on 2.0.0, it will work for every 2.Y.Z release.</p>
 <p>So, for example, if we decided to start the deprecation of a function in Airflow 2.2.4:</p>
 <ul class="simple">
 <li><p>Airflow 2.2 will contain a backwards-compatible replica of the function which will raise a DeprecationWarning</p></li>
 <li><p>Airflow 2.3 will continue to work and issue a warning</p></li>
 <li><p>Airflow 3.0 (the major version that follows 2.2) will remove the feature outright</p></li>
 </ul>
-<p>The exception to this deprecation policy is any feature which is marked as “experimental”, which <em>may</em> suffer breaking changes or complete removal in a Feature release.</p>
+<p>The exception to this deprecation policy is any feature which is marked as &quot;experimental&quot;, which <em>may</em> suffer breaking changes or complete removal in a Feature release.</p>
 </div>
 <div class="section" id="experimental-features">
 <span id="experimental"></span><h2>Experimental features<a class="headerlink" href="#experimental-features" title="Permalink to this headline">¶</a></h2>
 <p>From time-to-time a new feature will be added to Airflow that will be marked as experimental.</p>
 <p>Experimental features do not have any guarantees about deprecation, and <em>can</em> be changed in a breaking way between feature releases, or even removed entirely.</p>
-<p>We always aim to maintain compatibility even for experimental features, but make no promises. By having this “get out” it lets us build new features more quickly and get them in the hand of users without having to worry about making a feature perfect.</p>
+<p>We always aim to maintain compatibility even for experimental features, but make no promises. By having this &quot;get out&quot; it lets us build new features more quickly and get them in the hand of users without having to worry about making a feature perfect.</p>
 </div>
 </div>
 
@@ -781,7 +781,7 @@ This code will continue to work for the rest of the current major version – if
     <nav class="wy-nav-side-toc">
         <div class="wy-menu-vertical">
             <ul>
-<li><a class="reference internal" href="#">Airflow’s release process and version policy</a><ul>
+<li><a class="reference internal" href="#">Airflow's release process and version policy</a><ul>
 <li><a class="reference internal" href="#deprecation-policy">Deprecation policy</a></li>
 <li><a class="reference internal" href="#experimental-features">Experimental features</a></li>
 </ul>
diff --git a/docs-archive/apache-airflow/2.3.0/release_notes.html b/docs-archive/apache-airflow/2.3.0/release_notes.html
index 8b93b5a78..d8b1bf25a 100644
--- a/docs-archive/apache-airflow/2.3.0/release_notes.html
+++ b/docs-archive/apache-airflow/2.3.0/release_notes.html
@@ -20,7 +20,7 @@
             <link rel="index" title="Index" href="genindex.html" />
             <link rel="search" title="Search" href="search.html" />
             <link rel="next" title="Best Practices" href="best-practices.html" />
-            <link rel="prev" title="Airflow’s release process and version policy" href="release-process.html" />
+            <link rel="prev" title="Airflow&#39;s release process and version policy" href="release-process.html" />
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
@@ -357,7 +357,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#significant-changes">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#passing-execution-date-to-xcom-set-xcom-clear-xcom-get-one-and-xcom-get-many-is-deprecated-19825">Passing <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> to <code class="docutils literal notranslate"><span class="pre">XCom.set()</span></code>, <code class="docutils literal notranslate"><span class="pre">XCom.clear()</span></code> , <code class="docutils literal notranslate"><span class=" [...]
 <li class="toctree-l4"><a class="reference internal" href="#task-log-templates-are-now-read-from-the-metadata-database-instead-of-airflow-cfg-20165">Task log templates are now read from the metadata database instead of <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> (#20165)</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#minimum-kubernetes-version-bumped-from-3-0-0-to-21-7-0-20759">Minimum kubernetes version bumped from <code class="docutils literal notranslate"><span class="pre">3.0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">21.7.0</span></code> (#20759)</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#minimum-kubernetes-library-version-bumped-from-3-0-0-to-21-7-0-20759">Minimum kubernetes library version bumped from <code class="docutils literal notranslate"><span class="pre">3.0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">21.7.0</span></code> (#20759)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#xcom-now-defined-by-run-id-instead-of-execution-date-20975">XCom now defined by <code class="docutils literal notranslate"><span class="pre">run_id</span></code> instead of <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> (#20975)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#non-json-serializable-params-deprecated-21135">Non-JSON-serializable params deprecated (#21135).</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#you-must-use-postgresql-instead-of-postgres-in-sql-alchemy-conn-for-sqlalchemy-1-4-0-21205">You must use <code class="docutils literal notranslate"><span class="pre">postgresql://</span></code> instead of <code class="docutils literal notranslate"><span class="pre">postgres://</span></code> in <code class="docutils literal notranslate"><span class="pre">sql_alchemy_conn</span></code> for SQLAlchemy 1.4.0+ (#21205)</a></li>
@@ -366,7 +366,7 @@
 <li class="toctree-l4"><a class="reference internal" href="#zip-files-in-the-dags-folder-can-no-longer-have-a-py-extension-21538">Zip files in the DAGs folder can no longer have a <code class="docutils literal notranslate"><span class="pre">.py</span></code> extension (#21538)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#auth-backends-includes-session-21640"><code class="docutils literal notranslate"><span class="pre">auth_backends</span></code> includes session (#21640)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#default-templates-for-log-filenames-and-elasticsearch-log-id-changed-21734">Default templates for log filenames and elasticsearch log_id changed (#21734)</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798">BaseOperatorLink’s <code class="docutils literal notranslate"><span class="pre">get_link</span></code> method changed to take a <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (#21798)</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798">BaseOperatorLink's <code class="docutils literal notranslate"><span class="pre">get_link</span></code> method changed to take a <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (#21798)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#readytorescheduledep-now-only-runs-when-reschedule-is-true-21815"><code class="docutils literal notranslate"><span class="pre">ReadyToRescheduleDep</span></code> now only runs when <code class="docutils literal notranslate"><span class="pre">reschedule</span></code> is <em>True</em> (#21815)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#the-deps-attribute-on-an-operator-class-should-be-a-class-level-attribute-21815">The <code class="docutils literal notranslate"><span class="pre">deps</span></code> attribute on an operator class should be a class level attribute (#21815)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#deprecation-connection-extra-must-be-json-encoded-dict-21816">Deprecation: <code class="docutils literal notranslate"><span class="pre">Connection.extra</span></code> must be JSON-encoded dict (#21816)</a><ul>
@@ -421,7 +421,7 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#airflow-2-2-1-2021-10-29">Airflow 2.2.1 (2021-10-29)</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#id14">Significant Changes</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#param-s-default-value-for-default-removed"><code class="docutils literal notranslate"><span class="pre">Param</span></code>’s default value for <code class="docutils literal notranslate"><span class="pre">default</span></code> removed</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#param-s-default-value-for-default-removed"><code class="docutils literal notranslate"><span class="pre">Param</span></code>'s default value for <code class="docutils literal notranslate"><span class="pre">default</span></code> removed</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#max-queued-runs-per-dag-configuration-has-been-removed"><code class="docutils literal notranslate"><span class="pre">max_queued_runs_per_dag</span></code> configuration has been removed</a></li>
 </ul>
 </li>
@@ -488,9 +488,9 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#airflow-2-1-0-2021-05-21">Airflow 2.1.0 (2021-05-21)</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#id39">Significant Changes</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#new-deprecated-api-extra">New “deprecated_api” extra</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#new-deprecated-api-extra">New &quot;deprecated_api&quot; extra</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#the-http-provider-is-not-installed-by-default">The <code class="docutils literal notranslate"><span class="pre">http</span></code> provider is not installed by default</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#apply-default-decorator-isn-t-longer-necessary"><code class="docutils literal notranslate"><span class="pre">&#64;apply_default</span></code> decorator isn’t longer necessary</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#apply-default-decorator-isn-t-longer-necessary"><code class="docutils literal notranslate"><span class="pre">&#64;apply_default</span></code> decorator isn't longer necessary</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#change-the-configuration-options-for-field-masking">Change the configuration options for field masking</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#deprecated-poddefaults-and-add-xcom-sidecar-in-airflow-kubernetes-pod-generator">Deprecated PodDefaults and add_xcom_sidecar in airflow.kubernetes.pod_generator</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#removed-pod-launcher-from-core-airflow">Removed pod_launcher from core airflow</a></li>
@@ -695,7 +695,7 @@
 </ul>
 </li>
 <li class="toctree-l4"><a class="reference internal" href="#other-changes">Other changes</a><ul>
-<li class="toctree-l5"><a class="reference internal" href="#standardized-extra-requirements">Standardized “extra” requirements</a></li>
+<li class="toctree-l5"><a class="reference internal" href="#standardized-extra-requirements">Standardized &quot;extra&quot; requirements</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#simplify-the-response-payload-of-endpoints-dag-stats-and-task-stats">Simplify the response payload of endpoints /dag_stats and /task_stats</a></li>
 </ul>
 </li>
@@ -800,7 +800,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#id101">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#changes-in-experimental-api-execution-date-microseconds-replacement">Changes in experimental API execution_date microseconds replacement</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#infinite-pool-size-and-pool-size-query-optimization">Infinite pool size and pool size query optimization</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#viewer-won-t-have-edit-permissions-on-dag-view">Viewer won’t have edit permissions on DAG view.</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#viewer-won-t-have-edit-permissions-on-dag-view">Viewer won't have edit permissions on DAG view.</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#google-cloud-storage-hook">Google Cloud Storage Hook</a></li>
 </ul>
 </li>
@@ -814,7 +814,7 @@
 <li class="toctree-l2"><a class="reference internal" href="#airflow-1-10-6-2019-10-28">Airflow 1.10.6 (2019-10-28)</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#id107">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#baseoperator-render-template-function-signature-changed">BaseOperator::render_template function signature changed</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#changes-to-aws-default-connection-s-default-region">Changes to <code class="docutils literal notranslate"><span class="pre">aws_default</span></code> Connection’s default region</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#changes-to-aws-default-connection-s-default-region">Changes to <code class="docutils literal notranslate"><span class="pre">aws_default</span></code> Connection's default region</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#some-dag-processing-metrics-have-been-renamed">Some DAG Processing metrics have been renamed</a></li>
 </ul>
 </li>
@@ -870,7 +870,7 @@
 <li class="toctree-l4"><a class="reference internal" href="#removal-of-airflow-home-config-setting">Removal of <code class="docutils literal notranslate"><span class="pre">airflow_home</span></code> config setting</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#change-of-two-methods-signatures-in-gcptransferservicehook">Change of two methods signatures in <code class="docutils literal notranslate"><span class="pre">GCPTransferServiceHook</span></code></a></li>
 <li class="toctree-l4"><a class="reference internal" href="#moved-two-classes-to-different-modules">Moved two classes to different modules</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#fixed-typo-in-driver-class-path-in-sparksubmithook">Fixed typo in –driver-class-path in SparkSubmitHook</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#fixed-typo-in-driver-class-path-in-sparksubmithook">Fixed typo in --driver-class-path in SparkSubmitHook</a></li>
 </ul>
 </li>
 <li class="toctree-l3"><a class="reference internal" href="#new-feature">New Feature</a></li>
@@ -901,7 +901,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#id135">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#min-file-parsing-loop-time-config-option-temporarily-disabled">min_file_parsing_loop_time config option temporarily disabled</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#statsd-metrics">StatsD Metrics</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#emrhook-now-passes-all-of-connection-s-extra-to-createjobflow-api">EMRHook now passes all of connection’s extra to CreateJobFlow API</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#emrhook-now-passes-all-of-connection-s-extra-to-createjobflow-api">EMRHook now passes all of connection's extra to CreateJobFlow API</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#ldap-auth-backend-now-requires-tls">LDAP Auth Backend now requires TLS</a></li>
 </ul>
 </li>
@@ -948,7 +948,7 @@
 <li class="toctree-l5"><a class="reference internal" href="#a-quick-recap-about-logging">A quick recap about logging</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#changes-in-airflow-logging">Changes in Airflow Logging</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#template-path-of-the-file-task-handler">Template path of the file_task_handler</a></li>
-<li class="toctree-l5"><a class="reference internal" href="#i-m-using-s3log-or-gcslogs-what-do-i-do">I’m using S3Log or GCSLogs, what do I do!?</a></li>
+<li class="toctree-l5"><a class="reference internal" href="#i-m-using-s3log-or-gcslogs-what-do-i-do">I'm using S3Log or GCSLogs, what do I do!?</a></li>
 </ul>
 </li>
 <li class="toctree-l4"><a class="reference internal" href="#id142">New Features</a><ul>
@@ -1185,7 +1185,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#significant-changes">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#passing-execution-date-to-xcom-set-xcom-clear-xcom-get-one-and-xcom-get-many-is-deprecated-19825">Passing <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> to <code class="docutils literal notranslate"><span class="pre">XCom.set()</span></code>, <code class="docutils literal notranslate"><span class="pre">XCom.clear()</span></code> , <code class="docutils literal notranslate"><span class=" [...]
 <li class="toctree-l4"><a class="reference internal" href="#task-log-templates-are-now-read-from-the-metadata-database-instead-of-airflow-cfg-20165">Task log templates are now read from the metadata database instead of <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> (#20165)</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#minimum-kubernetes-version-bumped-from-3-0-0-to-21-7-0-20759">Minimum kubernetes version bumped from <code class="docutils literal notranslate"><span class="pre">3.0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">21.7.0</span></code> (#20759)</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#minimum-kubernetes-library-version-bumped-from-3-0-0-to-21-7-0-20759">Minimum kubernetes library version bumped from <code class="docutils literal notranslate"><span class="pre">3.0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">21.7.0</span></code> (#20759)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#xcom-now-defined-by-run-id-instead-of-execution-date-20975">XCom now defined by <code class="docutils literal notranslate"><span class="pre">run_id</span></code> instead of <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> (#20975)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#non-json-serializable-params-deprecated-21135">Non-JSON-serializable params deprecated (#21135).</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#you-must-use-postgresql-instead-of-postgres-in-sql-alchemy-conn-for-sqlalchemy-1-4-0-21205">You must use <code class="docutils literal notranslate"><span class="pre">postgresql://</span></code> instead of <code class="docutils literal notranslate"><span class="pre">postgres://</span></code> in <code class="docutils literal notranslate"><span class="pre">sql_alchemy_conn</span></code> for SQLAlchemy 1.4.0+ (#21205)</a></li>
@@ -1194,7 +1194,7 @@
 <li class="toctree-l4"><a class="reference internal" href="#zip-files-in-the-dags-folder-can-no-longer-have-a-py-extension-21538">Zip files in the DAGs folder can no longer have a <code class="docutils literal notranslate"><span class="pre">.py</span></code> extension (#21538)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#auth-backends-includes-session-21640"><code class="docutils literal notranslate"><span class="pre">auth_backends</span></code> includes session (#21640)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#default-templates-for-log-filenames-and-elasticsearch-log-id-changed-21734">Default templates for log filenames and elasticsearch log_id changed (#21734)</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798">BaseOperatorLink’s <code class="docutils literal notranslate"><span class="pre">get_link</span></code> method changed to take a <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (#21798)</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798">BaseOperatorLink's <code class="docutils literal notranslate"><span class="pre">get_link</span></code> method changed to take a <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (#21798)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#readytorescheduledep-now-only-runs-when-reschedule-is-true-21815"><code class="docutils literal notranslate"><span class="pre">ReadyToRescheduleDep</span></code> now only runs when <code class="docutils literal notranslate"><span class="pre">reschedule</span></code> is <em>True</em> (#21815)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#the-deps-attribute-on-an-operator-class-should-be-a-class-level-attribute-21815">The <code class="docutils literal notranslate"><span class="pre">deps</span></code> attribute on an operator class should be a class level attribute (#21815)</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#deprecation-connection-extra-must-be-json-encoded-dict-21816">Deprecation: <code class="docutils literal notranslate"><span class="pre">Connection.extra</span></code> must be JSON-encoded dict (#21816)</a><ul>
@@ -1249,7 +1249,7 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#airflow-2-2-1-2021-10-29">Airflow 2.2.1 (2021-10-29)</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#id14">Significant Changes</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#param-s-default-value-for-default-removed"><code class="docutils literal notranslate"><span class="pre">Param</span></code>’s default value for <code class="docutils literal notranslate"><span class="pre">default</span></code> removed</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#param-s-default-value-for-default-removed"><code class="docutils literal notranslate"><span class="pre">Param</span></code>'s default value for <code class="docutils literal notranslate"><span class="pre">default</span></code> removed</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#max-queued-runs-per-dag-configuration-has-been-removed"><code class="docutils literal notranslate"><span class="pre">max_queued_runs_per_dag</span></code> configuration has been removed</a></li>
 </ul>
 </li>
@@ -1316,9 +1316,9 @@
 </li>
 <li class="toctree-l2"><a class="reference internal" href="#airflow-2-1-0-2021-05-21">Airflow 2.1.0 (2021-05-21)</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#id39">Significant Changes</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#new-deprecated-api-extra">New “deprecated_api” extra</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#new-deprecated-api-extra">New &quot;deprecated_api&quot; extra</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#the-http-provider-is-not-installed-by-default">The <code class="docutils literal notranslate"><span class="pre">http</span></code> provider is not installed by default</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#apply-default-decorator-isn-t-longer-necessary"><code class="docutils literal notranslate"><span class="pre">&#64;apply_default</span></code> decorator isn’t longer necessary</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#apply-default-decorator-isn-t-longer-necessary"><code class="docutils literal notranslate"><span class="pre">&#64;apply_default</span></code> decorator isn't longer necessary</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#change-the-configuration-options-for-field-masking">Change the configuration options for field masking</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#deprecated-poddefaults-and-add-xcom-sidecar-in-airflow-kubernetes-pod-generator">Deprecated PodDefaults and add_xcom_sidecar in airflow.kubernetes.pod_generator</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#removed-pod-launcher-from-core-airflow">Removed pod_launcher from core airflow</a></li>
@@ -1523,7 +1523,7 @@
 </ul>
 </li>
 <li class="toctree-l4"><a class="reference internal" href="#other-changes">Other changes</a><ul>
-<li class="toctree-l5"><a class="reference internal" href="#standardized-extra-requirements">Standardized “extra” requirements</a></li>
+<li class="toctree-l5"><a class="reference internal" href="#standardized-extra-requirements">Standardized &quot;extra&quot; requirements</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#simplify-the-response-payload-of-endpoints-dag-stats-and-task-stats">Simplify the response payload of endpoints /dag_stats and /task_stats</a></li>
 </ul>
 </li>
@@ -1628,7 +1628,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#id101">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#changes-in-experimental-api-execution-date-microseconds-replacement">Changes in experimental API execution_date microseconds replacement</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#infinite-pool-size-and-pool-size-query-optimization">Infinite pool size and pool size query optimization</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#viewer-won-t-have-edit-permissions-on-dag-view">Viewer won’t have edit permissions on DAG view.</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#viewer-won-t-have-edit-permissions-on-dag-view">Viewer won't have edit permissions on DAG view.</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#google-cloud-storage-hook">Google Cloud Storage Hook</a></li>
 </ul>
 </li>
@@ -1642,7 +1642,7 @@
 <li class="toctree-l2"><a class="reference internal" href="#airflow-1-10-6-2019-10-28">Airflow 1.10.6 (2019-10-28)</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#id107">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#baseoperator-render-template-function-signature-changed">BaseOperator::render_template function signature changed</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#changes-to-aws-default-connection-s-default-region">Changes to <code class="docutils literal notranslate"><span class="pre">aws_default</span></code> Connection’s default region</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#changes-to-aws-default-connection-s-default-region">Changes to <code class="docutils literal notranslate"><span class="pre">aws_default</span></code> Connection's default region</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#some-dag-processing-metrics-have-been-renamed">Some DAG Processing metrics have been renamed</a></li>
 </ul>
 </li>
@@ -1698,7 +1698,7 @@
 <li class="toctree-l4"><a class="reference internal" href="#removal-of-airflow-home-config-setting">Removal of <code class="docutils literal notranslate"><span class="pre">airflow_home</span></code> config setting</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#change-of-two-methods-signatures-in-gcptransferservicehook">Change of two methods signatures in <code class="docutils literal notranslate"><span class="pre">GCPTransferServiceHook</span></code></a></li>
 <li class="toctree-l4"><a class="reference internal" href="#moved-two-classes-to-different-modules">Moved two classes to different modules</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#fixed-typo-in-driver-class-path-in-sparksubmithook">Fixed typo in –driver-class-path in SparkSubmitHook</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#fixed-typo-in-driver-class-path-in-sparksubmithook">Fixed typo in --driver-class-path in SparkSubmitHook</a></li>
 </ul>
 </li>
 <li class="toctree-l3"><a class="reference internal" href="#new-feature">New Feature</a></li>
@@ -1729,7 +1729,7 @@
 <li class="toctree-l3"><a class="reference internal" href="#id135">Significant Changes</a><ul>
 <li class="toctree-l4"><a class="reference internal" href="#min-file-parsing-loop-time-config-option-temporarily-disabled">min_file_parsing_loop_time config option temporarily disabled</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#statsd-metrics">StatsD Metrics</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#emrhook-now-passes-all-of-connection-s-extra-to-createjobflow-api">EMRHook now passes all of connection’s extra to CreateJobFlow API</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#emrhook-now-passes-all-of-connection-s-extra-to-createjobflow-api">EMRHook now passes all of connection's extra to CreateJobFlow API</a></li>
 <li class="toctree-l4"><a class="reference internal" href="#ldap-auth-backend-now-requires-tls">LDAP Auth Backend now requires TLS</a></li>
 </ul>
 </li>
@@ -1776,7 +1776,7 @@
 <li class="toctree-l5"><a class="reference internal" href="#a-quick-recap-about-logging">A quick recap about logging</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#changes-in-airflow-logging">Changes in Airflow Logging</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#template-path-of-the-file-task-handler">Template path of the file_task_handler</a></li>
-<li class="toctree-l5"><a class="reference internal" href="#i-m-using-s3log-or-gcslogs-what-do-i-do">I’m using S3Log or GCSLogs, what do I do!?</a></li>
+<li class="toctree-l5"><a class="reference internal" href="#i-m-using-s3log-or-gcslogs-what-do-i-do">I'm using S3Log or GCSLogs, what do I do!?</a></li>
 </ul>
 </li>
 <li class="toctree-l4"><a class="reference internal" href="#id142">New Features</a><ul>
@@ -2020,8 +2020,13 @@
 <p>Previously, a task’s log is dynamically rendered from the <code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">log_filename_template</span></code> and <code class="docutils literal notranslate"><span class="pre">[elasticsearch]</span> <span class="pre">log_id_template</span></code> config values at runtime. This resulted in unfortunate characteristics, e.g. it is impractical to modify the config value after an Airflow instance is running for a w [...]
 <p>A new <code class="docutils literal notranslate"><span class="pre">log_template</span></code> table is introduced to solve this problem. This table is synchronized with the aforementioned config values every time Airflow starts, and a new field <code class="docutils literal notranslate"><span class="pre">log_template_id</span></code> is added to every DAG run to point to the format used by tasks (<code class="docutils literal notranslate"><span class="pre">NULL</span></code> indicates [...]
 </div>
-<div class="section" id="minimum-kubernetes-version-bumped-from-3-0-0-to-21-7-0-20759">
-<h4>Minimum kubernetes version bumped from <code class="docutils literal notranslate"><span class="pre">3.0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">21.7.0</span></code> (#20759)<a class="headerlink" href="#minimum-kubernetes-version-bumped-from-3-0-0-to-21-7-0-20759" title="Permalink to this headline">¶</a></h4>
+<div class="section" id="minimum-kubernetes-library-version-bumped-from-3-0-0-to-21-7-0-20759">
+<h4>Minimum kubernetes library version bumped from <code class="docutils literal notranslate"><span class="pre">3.0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">21.7.0</span></code> (#20759)<a class="headerlink" href="#minimum-kubernetes-library-version-bumped-from-3-0-0-to-21-7-0-20759" title="Permalink to this headline">¶</a></h4>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>This is only about changing the <code class="docutils literal notranslate"><span class="pre">kubernetes</span></code> library, not the Kubernetes cluster. Airflow support for
+Kubernetes version is described in <a class="reference external" href="https://airflow.apache.org/docs/apache-airflow/stable/installation/prerequisites.html">Installation prerequisites</a>.</p>
+</div>
 <p>No change in behavior is expected.  This was necessary in order to take advantage of a <a class="reference external" href="https://github.com/kubernetes-client/python-base/commit/70b78cd8488068c014b6d762a0c8d358273865b4">bugfix</a> concerning refreshing of Kubernetes API tokens with EKS, which enabled the removal of some <a class="reference external" href="https://github.com/apache/airflow/pull/20759">workaround code</a>.</p>
 </div>
 <div class="section" id="xcom-now-defined-by-run-id-instead-of-execution-date-20975">
@@ -2083,13 +2088,13 @@ Details in the <a class="reference external" href="https://docs.sqlalchemy.org/e
 <li><p><code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">log_filename_template</span></code>: <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">ti.dag_id</span> <span class="pre">}}/{{</span> <span class="pre">ti.task_id</span> <span class="pre">}}/{{</span> <span class="pre">ts</span> <span class="pre">}}/{{</span> <span class="pre">try_number</span> <span class="pre">}}.log</span></code></p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">[elasticsearch]</span> <span class="pre">log_id_template</span></code>: <code class="docutils literal notranslate"><span class="pre">{dag_id}-{task_id}-{execution_date}-{try_number}</span></code></p></li>
 </ul>
-<p><code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">log_filename_template</span></code> now uses “hive partition style” of <code class="docutils literal notranslate"><span class="pre">dag_id=&lt;id&gt;/run_id=&lt;id&gt;</span></code> by default, which may cause problems on some older FAT filesystems. If this affects you then you will have to change the log template.</p>
+<p><code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">log_filename_template</span></code> now uses &quot;hive partition style&quot; of <code class="docutils literal notranslate"><span class="pre">dag_id=&lt;id&gt;/run_id=&lt;id&gt;</span></code> by default, which may cause problems on some older FAT filesystems. If this affects you then you will have to change the log template.</p>
 <p>If you have customized the templates you should ensure that they contain <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">ti.map_index</span> <span class="pre">}}</span></code> if you want to use dynamically mapped tasks.</p>
 </div>
 <div class="section" id="baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798">
-<h4>BaseOperatorLink’s <code class="docutils literal notranslate"><span class="pre">get_link</span></code> method changed to take a <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (#21798)<a class="headerlink" href="#baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798" title="Permalink to this headline">¶</a></h4>
-<p>In v2.2 we “deprecated” passing an execution date to XCom.get methods, but there was no other option for operator links as they were only passed an execution_date.</p>
-<p>Now in 2.3 as part of Dynamic Task Mapping (AIP-42) we will need to add map_index to the XCom row to support the “reduce” part of the API.</p>
+<h4>BaseOperatorLink's <code class="docutils literal notranslate"><span class="pre">get_link</span></code> method changed to take a <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (#21798)<a class="headerlink" href="#baseoperatorlink-s-get-link-method-changed-to-take-a-ti-key-keyword-argument-21798" title="Permalink to this headline">¶</a></h4>
+<p>In v2.2 we &quot;deprecated&quot; passing an execution date to XCom.get methods, but there was no other option for operator links as they were only passed an execution_date.</p>
+<p>Now in 2.3 as part of Dynamic Task Mapping (AIP-42) we will need to add map_index to the XCom row to support the &quot;reduce&quot; part of the API.</p>
 <p>In order to support that cleanly we have changed the interface for BaseOperatorLink to take an TaskInstanceKey as the <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> keyword argument (as execution_date + task is no longer unique for mapped operators).</p>
 <p>The existing signature will be detected (by the absence of the <code class="docutils literal notranslate"><span class="pre">ti_key</span></code> argument) and continue to work.</p>
 </div>
@@ -2099,7 +2104,7 @@ Details in the <a class="reference external" href="https://docs.sqlalchemy.org/e
 </div>
 <div class="section" id="the-deps-attribute-on-an-operator-class-should-be-a-class-level-attribute-21815">
 <h4>The <code class="docutils literal notranslate"><span class="pre">deps</span></code> attribute on an operator class should be a class level attribute (#21815)<a class="headerlink" href="#the-deps-attribute-on-an-operator-class-should-be-a-class-level-attribute-21815" title="Permalink to this headline">¶</a></h4>
-<p>To support operator-mapping (AIP 42), the <code class="docutils literal notranslate"><span class="pre">deps</span></code> attribute on operator class must be a set at the class level. This means that if a custom operator implements this as an instance-level variable, it will not be able to be used for operator-mapping. This does not affect existing code, but we highly recommend you to restructure the operator’s dep logic in order to support the new feature.</p>
+<p>To support operator-mapping (AIP 42), the <code class="docutils literal notranslate"><span class="pre">deps</span></code> attribute on operator class must be a set at the class level. This means that if a custom operator implements this as an instance-level variable, it will not be able to be used for operator-mapping. This does not affect existing code, but we highly recommend you to restructure the operator's dep logic in order to support the new feature.</p>
 </div>
 <div class="section" id="deprecation-connection-extra-must-be-json-encoded-dict-21816">
 <h4>Deprecation: <code class="docutils literal notranslate"><span class="pre">Connection.extra</span></code> must be JSON-encoded dict (#21816)<a class="headerlink" href="#deprecation-connection-extra-must-be-json-encoded-dict-21816" title="Permalink to this headline">¶</a></h4>
@@ -2109,13 +2114,13 @@ Details in the <a class="reference external" href="https://docs.sqlalchemy.org/e
 </div>
 <div class="section" id="what-why-and-when">
 <h5>What, why, and when?<a class="headerlink" href="#what-why-and-when" title="Permalink to this headline">¶</a></h5>
-<p>Airflow’s Connection is used for storing credentials.  For storage of information that does not
+<p>Airflow's Connection is used for storing credentials.  For storage of information that does not
 fit into user / password / host / schema / port, we have the <code class="docutils literal notranslate"><span class="pre">extra</span></code> string field.  Its intention
 was always to provide for storage of arbitrary key-value pairs, like <code class="docutils literal notranslate"><span class="pre">no_host_key_check</span></code> in the SSH
 hook, or <code class="docutils literal notranslate"><span class="pre">keyfile_dict</span></code> in GCP.</p>
-<p>But since the field is string, it’s technically been permissible to store any string value.  For example
+<p>But since the field is string, it's technically been permissible to store any string value.  For example
 one could have stored the string value <code class="docutils literal notranslate"><span class="pre">'my-website.com'</span></code> and used this in the hook.  But this is a very
-bad practice. One reason is intelligibility: when you look at the value for <code class="docutils literal notranslate"><span class="pre">extra</span></code> , you don’t have any idea
+bad practice. One reason is intelligibility: when you look at the value for <code class="docutils literal notranslate"><span class="pre">extra</span></code> , you don't have any idea
 what its purpose is.  Better would be to store <code class="docutils literal notranslate"><span class="pre">{&quot;api_host&quot;:</span> <span class="pre">&quot;my-website.com&quot;}</span></code> which at least tells you
 <em>something</em> about the value.  Another reason is extensibility: if you store the API host as a simple string
 value, what happens if you need to add more information, such as the API endpoint, or credentials?  Then
@@ -2161,19 +2166,19 @@ task logs).</p>
 </div>
 <div class="section" id="remove-requirement-that-custom-connection-ui-fields-be-prefixed-22607">
 <h4>Remove requirement that custom connection UI fields be prefixed (#22607)<a class="headerlink" href="#remove-requirement-that-custom-connection-ui-fields-be-prefixed-22607" title="Permalink to this headline">¶</a></h4>
-<p>Hooks can define custom connection fields for their connection type by implementing method <code class="docutils literal notranslate"><span class="pre">get_connection_form_widgets</span></code>.  These custom fields appear in the web UI as additional connection attributes, but internally they are stored in the connection <code class="docutils literal notranslate"><span class="pre">extra</span></code> dict field.  For technical reasons, previously, when stored in the <code class="docut [...]
+<p>Hooks can define custom connection fields for their connection type by implementing method <code class="docutils literal notranslate"><span class="pre">get_connection_form_widgets</span></code>.  These custom fields appear in the web UI as additional connection attributes, but internally they are stored in the connection <code class="docutils literal notranslate"><span class="pre">extra</span></code> dict field.  For technical reasons, previously, when stored in the <code class="docut [...]
 <p>To enable this, update the dict returned by the <code class="docutils literal notranslate"><span class="pre">get_connection_form_widgets</span></code> method to remove the prefix from the keys.  Internally, the providers manager will still use a prefix to ensure each custom field is globally unique, but the absence of a prefix in the returned widget dict will signal to the Web UI to read and store custom fields without the prefix.  Note that this is only a change to the Web UI behavio [...]
 </div>
 <div class="section" id="the-webserver-x-frame-enabled-configuration-works-according-to-description-now-23222">
 <h4>The webserver.X_FRAME_ENABLED configuration works according to description now (#23222).<a class="headerlink" href="#the-webserver-x-frame-enabled-configuration-works-according-to-description-now-23222" title="Permalink to this headline">¶</a></h4>
 <p>In Airflow 2.0.0 - 2.2.4 the webserver.X_FRAME_ENABLED parameter worked the opposite of its description,
-setting the value to “true” caused “X-Frame-Options” header to “DENY” (not allowing Airflow to be used
-in an iframe). When you set it to “false”, the header was not added, so Airflow could be embedded in an
+setting the value to &quot;true&quot; caused &quot;X-Frame-Options&quot; header to &quot;DENY&quot; (not allowing Airflow to be used
+in an iframe). When you set it to &quot;false&quot;, the header was not added, so Airflow could be embedded in an
 iframe. By default Airflow could not be embedded in an iframe.</p>
 <p>In Airflow 2.2.5 there was a bug introduced that made it impossible to disable Airflow to
 work in iframe. No matter what the configuration was set, it was possible to embed Airflow in an iframe.</p>
-<p>Airflow 2.3.0 restores the original meaning to the parameter. If you set it to “true” (default) Airflow
-can be embedded in an iframe (no header is added), but when you set it to “false” the header is added
+<p>Airflow 2.3.0 restores the original meaning to the parameter. If you set it to &quot;true&quot; (default) Airflow
+can be embedded in an iframe (no header is added), but when you set it to &quot;false&quot; the header is added
 and Airflow cannot be embedded in an iframe.</p>
 </div>
 </div>
@@ -2186,7 +2191,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Allow reuse of decorated tasks (#22941)</p></li>
 <li><p>Move the database configuration to a new section (#22284)</p></li>
 <li><p>Add <code class="docutils literal notranslate"><span class="pre">SmoothOperator</span></code> (#22813)</p></li>
-<li><p>Make operator’s <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code> configurable (#22389)</p></li>
+<li><p>Make operator's <code class="docutils literal notranslate"><span class="pre">execution_timeout</span></code> configurable (#22389)</p></li>
 <li><p>Events Timetable (#22332)</p></li>
 <li><p>Support dag serialization with custom <code class="docutils literal notranslate"><span class="pre">ti_deps</span></code> rules (#22698)</p></li>
 <li><p>Support log download in task log view (#22804)</p></li>
@@ -2225,7 +2230,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Showing approximate time until next dag_run in Airflow  (#20273)</p></li>
 <li><p>Extend config window on UI (#20052)</p></li>
 <li><p>Add show dag dependencies feature to CLI (#19985)</p></li>
-<li><p>Add cli command for ‘airflow dags reserialize` (#19471)</p></li>
+<li><p>Add cli command for 'airflow dags reserialize` (#19471)</p></li>
 <li><p>Add missing description field to Pool schema(REST API) (#19841)</p></li>
 <li><p>Introduce DagRun action to change state to queued. (#19353)</p></li>
 <li><p>Add DAG run details page (#19705)</p></li>
@@ -2244,17 +2249,17 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Meaningful error message in resolve_template_files (#23027)</p></li>
 <li><p>Update ImportError items instead of deleting and recreating them (#22928)</p></li>
 <li><p>Add option <code class="docutils literal notranslate"><span class="pre">--skip-init</span></code> to db reset command (#22989)</p></li>
-<li><p>Support importing connections from files with “.yml” extension (#22872)</p></li>
+<li><p>Support importing connections from files with &quot;.yml&quot; extension (#22872)</p></li>
 <li><p>Support glob syntax in <code class="docutils literal notranslate"><span class="pre">.airflowignore</span></code> files (#21392) (#22051)</p></li>
 <li><p>Hide pagination when data is a single page (#22963)</p></li>
 <li><p>Support for sorting DAGs in the web UI (#22671)</p></li>
 <li><p>Speed up <code class="docutils literal notranslate"><span class="pre">has_access</span></code> decorator by ~200ms (#22858)</p></li>
 <li><p>Add XComArg to lazy-imported list of Airflow module (#22862)</p></li>
 <li><p>Add more fields to REST API dags/dag_id/details endpoint (#22756)</p></li>
-<li><p>Don’t show irrelevant/duplicated/”internal” Task attrs in UI (#22812)</p></li>
+<li><p>Don't show irrelevant/duplicated/&quot;internal&quot; Task attrs in UI (#22812)</p></li>
 <li><p>No need to load whole ti in current_state (#22764)</p></li>
 <li><p>Pickle dag exception string fix (#22760)</p></li>
-<li><p>Better verification of Localexecutor’s parallelism option (#22711)</p></li>
+<li><p>Better verification of Localexecutor's parallelism option (#22711)</p></li>
 <li><p>log backfill exceptions to sentry (#22704)</p></li>
 <li><p>retry commit on MySQL deadlocks during backfill (#22696)</p></li>
 <li><p>Add more fields to REST API get DAG(dags/dag_id) endpoint (#22637)</p></li>
@@ -2264,20 +2269,20 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Expose <code class="docutils literal notranslate"><span class="pre">try_number</span></code> in airflow vars (#22297)</p></li>
 <li><p>Add generic connection type (#22310)</p></li>
 <li><p>Add a few more fields to the taskinstance finished log message (#22262)</p></li>
-<li><p>Pause auto-refresh if scheduler isn’t running (#22151)</p></li>
+<li><p>Pause auto-refresh if scheduler isn't running (#22151)</p></li>
 <li><p>Show DagModel details. (#21868)</p></li>
 <li><p>Add pip_install_options to PythonVirtualenvOperator (#22158)</p></li>
 <li><p>Show import error for <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">list</span></code> CLI command (#21991)</p></li>
 <li><p>Pause auto-refresh when page is hidden (#21904)</p></li>
 <li><p>Default args type check (#21809)</p></li>
 <li><p>Enhance magic methods on XComArg for UX (#21882)</p></li>
-<li><p>py files don’t have to be checked <code class="docutils literal notranslate"><span class="pre">is_zipfiles</span></code> in refresh_dag (#21926)</p></li>
+<li><p>py files don't have to be checked <code class="docutils literal notranslate"><span class="pre">is_zipfiles</span></code> in refresh_dag (#21926)</p></li>
 <li><p>Fix TaskDecorator type hints (#21881)</p></li>
-<li><p>Add ‘Show record’ option for variables (#21342)</p></li>
+<li><p>Add 'Show record' option for variables (#21342)</p></li>
 <li><p>Use DB where possible for quicker <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dag</span></code> subcommands (#21793)</p></li>
 <li><p>REST API: add rendered fields in task instance. (#21741)</p></li>
 <li><p>Change the default auth backend to session (#21640)</p></li>
-<li><p>Don’t check if <code class="docutils literal notranslate"><span class="pre">py</span></code> DAG files are zipped during parsing (#21538)</p></li>
+<li><p>Don't check if <code class="docutils literal notranslate"><span class="pre">py</span></code> DAG files are zipped during parsing (#21538)</p></li>
 <li><p>Switch XCom implementation to use <code class="docutils literal notranslate"><span class="pre">run_id</span></code> (#20975)</p></li>
 <li><p>Action log on Browse Views (#21569)</p></li>
 <li><p>Implement multiple API auth backends (#21472)</p></li>
@@ -2285,7 +2290,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Support mssql in airflow db shell (#21511)</p></li>
 <li><p>Support config <code class="docutils literal notranslate"><span class="pre">worker_enable_remote_control</span></code> for celery (#21507)</p></li>
 <li><p>Log memory usage in <code class="docutils literal notranslate"><span class="pre">CgroupTaskRunner</span></code> (#21481)</p></li>
-<li><p>Modernize DAG-related URL routes and rename “tree” to “grid” (#20730)</p></li>
+<li><p>Modernize DAG-related URL routes and rename &quot;tree&quot; to &quot;grid&quot; (#20730)</p></li>
 <li><p>Move Zombie detection to <code class="docutils literal notranslate"><span class="pre">SchedulerJob</span></code> (#21181)</p></li>
 <li><p>Improve speed to run <code class="docutils literal notranslate"><span class="pre">airflow</span></code> by 6x (#21438)</p></li>
 <li><p>Add more SQL template fields renderers (#21237)</p></li>
@@ -2299,7 +2304,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Correctly specify overloads for TaskFlow API for type-hinting (#20933)</p></li>
 <li><p>Introduce notification_sent to SlaMiss view (#20923)</p></li>
 <li><p>Rewrite the task decorator as a composition (#20868)</p></li>
-<li><p>Add “Greater/Smaller than or Equal” to filters in the browse views (#20602) (#20798)</p></li>
+<li><p>Add &quot;Greater/Smaller than or Equal&quot; to filters in the browse views (#20602) (#20798)</p></li>
 <li><p>Rewrite DAG run retrieval in task command (#20737)</p></li>
 <li><p>Speed up creation of DagRun for large DAGs (5k+ tasks) by 25-130% (#20722)</p></li>
 <li><p>Make native environment Airflow-flavored like sandbox (#20704)</p></li>
@@ -2321,16 +2326,16 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Check and run migration in commands if necessary (#18439)</p></li>
 <li><p>Log only when Zombies exists (#20118)</p></li>
 <li><p>Increase length of the email and username (#19932)</p></li>
-<li><p>Add more filtering options for TI’s in the UI (#19910)</p></li>
-<li><p>Dynamically enable “Test Connection” button by connection type (#19792)</p></li>
-<li><p>Avoid littering postgres server logs with “could not obtain lock” with HA schedulers (#19842)</p></li>
+<li><p>Add more filtering options for TI's in the UI (#19910)</p></li>
+<li><p>Dynamically enable &quot;Test Connection&quot; button by connection type (#19792)</p></li>
+<li><p>Avoid littering postgres server logs with &quot;could not obtain lock&quot; with HA schedulers (#19842)</p></li>
 <li><p>Renamed <code class="docutils literal notranslate"><span class="pre">Connection.get_hook</span></code> parameter to make it the same as in <code class="docutils literal notranslate"><span class="pre">SqlSensor</span></code> and <code class="docutils literal notranslate"><span class="pre">SqlOperator</span></code>. (#19849)</p></li>
 <li><p>Add hook_params in SqlSensor using the latest changes from PR #18718. (#18431)</p></li>
 <li><p>Speed up webserver boot time by delaying provider initialization (#19709)</p></li>
 <li><p>Configurable logging of <code class="docutils literal notranslate"><span class="pre">XCOM</span></code> value in PythonOperator (#19378)</p></li>
 <li><p>Minimize production js files (#19658)</p></li>
 <li><p>Add <code class="docutils literal notranslate"><span class="pre">hook_params</span></code> in <code class="docutils literal notranslate"><span class="pre">BaseSqlOperator</span></code> (#18718)</p></li>
-<li><p>Add missing “end_date” to hash components (#19281)</p></li>
+<li><p>Add missing &quot;end_date&quot; to hash components (#19281)</p></li>
 <li><p>More friendly output of the airflow plugins command + add timetables (#19298)</p></li>
 <li><p>Add sensor default timeout config (#19119)</p></li>
 <li><p>Update <code class="docutils literal notranslate"><span class="pre">taskinstance</span></code> REST API schema to include dag_run_id field (#19105)</p></li>
@@ -2341,7 +2346,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <div class="section" id="bug-fixes">
 <h3>Bug Fixes<a class="headerlink" href="#bug-fixes" title="Permalink to this headline">¶</a></h3>
 <ul class="simple">
-<li><p>Use inherited ‘trigger_tasks’ method (#23016)</p></li>
+<li><p>Use inherited 'trigger_tasks' method (#23016)</p></li>
 <li><p>In DAG dependency detector, use class type instead of class name (#21706)</p></li>
 <li><p>Fix tasks being wrongly skipped by schedule_after_task_execution (#23181)</p></li>
 <li><p>Fix X-Frame enabled behaviour (#23222)</p></li>
@@ -2350,11 +2355,11 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Fix timezone display for logs on UI (#23075)</p></li>
 <li><p>Include message in graph errors (#23021)</p></li>
 <li><p>Change trigger dropdown left position (#23013)</p></li>
-<li><p>Don’t add planned tasks for legacy DAG runs (#23007)</p></li>
+<li><p>Don't add planned tasks for legacy DAG runs (#23007)</p></li>
 <li><p>Add dangling rows check for TaskInstance references (#22924)</p></li>
 <li><p>Validate the input params in connection <code class="docutils literal notranslate"><span class="pre">CLI</span></code> command (#22688)</p></li>
 <li><p>Fix trigger event payload is not persisted in db (#22944)</p></li>
-<li><p>Drop “airflow moved” tables in command <code class="docutils literal notranslate"><span class="pre">db</span> <span class="pre">reset</span></code> (#22990)</p></li>
+<li><p>Drop &quot;airflow moved&quot; tables in command <code class="docutils literal notranslate"><span class="pre">db</span> <span class="pre">reset</span></code> (#22990)</p></li>
 <li><p>Add max width to task group tooltips (#22978)</p></li>
 <li><p>Add template support for <code class="docutils literal notranslate"><span class="pre">external_task_ids</span></code>. (#22809)</p></li>
 <li><p>Allow <code class="docutils literal notranslate"><span class="pre">DagParam</span></code> to hold falsy values (#22964)</p></li>
@@ -2389,7 +2394,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Set <code class="docutils literal notranslate"><span class="pre">queued_dttm</span></code> when submitting task to directly to executor (#22259)</p></li>
 <li><p>Addressed some issues in the tutorial mentioned in discussion #22233 (#22236)</p></li>
 <li><p>Change default python executable to python3 for docker decorator (#21973)</p></li>
-<li><p>Don’t validate that Params are JSON when NOTSET (#22000)</p></li>
+<li><p>Don't validate that Params are JSON when NOTSET (#22000)</p></li>
 <li><p>Add per-DAG delete permissions (#21938)</p></li>
 <li><p>Fix handling some None parameters in kubernetes 23 libs. (#21905)</p></li>
 <li><p>Fix handling of empty (None) tags in <code class="docutils literal notranslate"><span class="pre">bulk_write_to_db</span></code> (#21757)</p></li>
@@ -2400,7 +2405,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>[de]serialize resources on task correctly (#21445)</p></li>
 <li><p>Add params <code class="docutils literal notranslate"><span class="pre">dag_id</span></code>, <code class="docutils literal notranslate"><span class="pre">task_id</span></code> etc to <code class="docutils literal notranslate"><span class="pre">XCom.serialize_value</span></code> (#19505)</p></li>
 <li><p>Update test connection functionality to use custom form fields (#21330)</p></li>
-<li><p>fix all “high” npm vulnerabilities (#21526)</p></li>
+<li><p>fix all &quot;high&quot; npm vulnerabilities (#21526)</p></li>
 <li><p>Fix bug incorrectly removing action from role, rather than permission. (#21483)</p></li>
 <li><p>Fix relationship join bug in FAB/SecurityManager with SQLA 1.4 (#21296)</p></li>
 <li><p>Use Identity instead of Sequence in SQLAlchemy 1.4 for MSSQL (#21238)</p></li>
@@ -2412,16 +2417,16 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Fix <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">trigger</span></code> cli (#20781)</p></li>
 <li><p>Fix task instances iteration in a pool to prevent blocking (#20816)</p></li>
 <li><p>Allow depending to a <code class="docutils literal notranslate"><span class="pre">&#64;task_group</span></code> as a whole (#20671)</p></li>
-<li><p>Use original task’s <code class="docutils literal notranslate"><span class="pre">start_date</span></code> if a task continues after deferral (#20062)</p></li>
+<li><p>Use original task's <code class="docutils literal notranslate"><span class="pre">start_date</span></code> if a task continues after deferral (#20062)</p></li>
 <li><p>Disabled edit button in task instances list view page (#20659)</p></li>
 <li><p>Fix a package name import error (#20519) (#20519)</p></li>
 <li><p>Remove <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> label when get cleanup pods list (#20417)</p></li>
 <li><p>Remove unneeded FAB REST API endpoints (#20487)</p></li>
 <li><p>Fix parsing of Cloudwatch log group arn containing slashes (#14667) (#19700)</p></li>
-<li><p>Sanity check for MySQL’s TIMESTAMP column (#19821)</p></li>
+<li><p>Sanity check for MySQL's TIMESTAMP column (#19821)</p></li>
 <li><p>Allow using default celery command group with executors subclassed from Celery-based executors. (#18189)</p></li>
 <li><p>Move <code class="docutils literal notranslate"><span class="pre">class_permission_name</span></code> to mixin so it applies to all classes (#18749)</p></li>
-<li><p>Adjust trimmed_pod_id and replace ‘.’ with ‘-‘ (#19036)</p></li>
+<li><p>Adjust trimmed_pod_id and replace '.' with '-' (#19036)</p></li>
 <li><p>Pass custom_headers to send_email and send_email_smtp (#19009)</p></li>
 <li><p>Ensure <code class="docutils literal notranslate"><span class="pre">catchup=False</span></code> is used in example dags (#19396)</p></li>
 <li><p>Edit permalinks in OpenApi description file (#19244)</p></li>
@@ -2449,7 +2454,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Add docs for <code class="docutils literal notranslate"><span class="pre">db</span> <span class="pre">upgrade</span></code> / <code class="docutils literal notranslate"><span class="pre">db</span> <span class="pre">downgrade</span></code> (#21879)</p></li>
 <li><p>Update modules_management.rst (#21889)</p></li>
 <li><p>Fix UPDATING section on SqlAlchemy 1.4 scheme changes (#21887)</p></li>
-<li><p>Update TaskFlow tutorial doc to show how to pass “operator-level” args. (#21446)</p></li>
+<li><p>Update TaskFlow tutorial doc to show how to pass &quot;operator-level&quot; args. (#21446)</p></li>
 <li><p>Fix doc - replace decreasing by increasing (#21805)</p></li>
 <li><p>Add another way to dynamically generate DAGs to docs (#21297)</p></li>
 <li><p>Add extra information about time synchronization needed (#21685)</p></li>
@@ -2479,7 +2484,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Patch <code class="docutils literal notranslate"><span class="pre">sql_alchemy_conn</span></code> if old postgres scheme used (#22333)</p></li>
 <li><p>Protect against accidental misuse of XCom.get_value() (#22244)</p></li>
 <li><p>Order filenames for migrations (#22168)</p></li>
-<li><p>Don’t try to auto generate migrations for Celery tables (#22120)</p></li>
+<li><p>Don't try to auto generate migrations for Celery tables (#22120)</p></li>
 <li><p>Require SQLAlchemy 1.4 (#22114)</p></li>
 <li><p>bump sphinx-jinja (#22101)</p></li>
 <li><p>Add compat shim for SQLAlchemy to avoid warnings (#21959)</p></li>
@@ -2530,7 +2535,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Fix graph auto-refresh on page load (#21736)</p></li>
 <li><p>Fix filesystem sensor for directories (#21729)</p></li>
 <li><p>Fix stray <code class="docutils literal notranslate"><span class="pre">order_by(TaskInstance.execution_date)</span></code> (#21705)</p></li>
-<li><p>Correctly handle multiple ‘=’ in LocalFileSystem secrets. (#21694)</p></li>
+<li><p>Correctly handle multiple '=' in LocalFileSystem secrets. (#21694)</p></li>
 <li><p>Log exception in local executor (#21667)</p></li>
 <li><p>Disable <code class="docutils literal notranslate"><span class="pre">default_pool</span></code> delete on web ui (#21658)</p></li>
 <li><p>Extends <code class="docutils literal notranslate"><span class="pre">typing-extensions</span></code> to be installed with python 3.8+ #21566 (#21567)</p></li>
@@ -2581,7 +2586,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <h3>Significant Changes<a class="headerlink" href="#id4" title="Permalink to this headline">¶</a></h3>
 <div class="section" id="smart-sensors-deprecated">
 <h4>Smart sensors deprecated<a class="headerlink" href="#smart-sensors-deprecated" title="Permalink to this headline">¶</a></h4>
-<p>Smart sensors, an “early access” feature added in Airflow 2, are now deprecated and will be removed in Airflow 2.4.0. They have been superseded by Deferrable Operators, added in Airflow 2.2.0.</p>
+<p>Smart sensors, an &quot;early access&quot; feature added in Airflow 2, are now deprecated and will be removed in Airflow 2.4.0. They have been superseded by Deferrable Operators, added in Airflow 2.2.0.</p>
 <p>See <a class="reference external" href="https://airflow.apache.org/docs/apache-airflow/2.2.4/concepts/smart-sensors.html#migrating-to-deferrable-operators">Migrating to Deferrable Operators</a> for details on how to migrate.</p>
 </div>
 </div>
@@ -2605,9 +2610,9 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Fix session usage in <code class="docutils literal notranslate"><span class="pre">/rendered-k8s</span></code> view (#21006)</p></li>
 <li><p>Fix <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">backfill</span> <span class="pre">--reset-dagruns</span></code> errors when run twice (#21062)</p></li>
 <li><p>Do not set <code class="docutils literal notranslate"><span class="pre">TaskInstance.max_tries</span></code> in <code class="docutils literal notranslate"><span class="pre">refresh_from_task</span></code> (#21018)</p></li>
-<li><p>Don’t require dag_id in body in dagrun REST API endpoint (#21024)</p></li>
+<li><p>Don't require dag_id in body in dagrun REST API endpoint (#21024)</p></li>
 <li><p>Add Roles from Azure OAUTH Response in internal Security Manager (#20707)</p></li>
-<li><p>Allow Viewing DagRuns and TIs if a user has DAG “read” perms (#20663)</p></li>
+<li><p>Allow Viewing DagRuns and TIs if a user has DAG &quot;read&quot; perms (#20663)</p></li>
 <li><p>Fix running <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">dags</span> <span class="pre">test</span> <span class="pre">&lt;dag_id&gt;</span> <span class="pre">&lt;execution_dt&gt;</span></code> results in error when run twice (#21031)</p></li>
 <li><p>Switch to non-vendored latest connexion library (#20910)</p></li>
 <li><p>Bump flask-appbuilder to <code class="docutils literal notranslate"><span class="pre">&gt;=3.3.4</span></code> (#20628)</p></li>
@@ -2633,7 +2638,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Add note about Variable precedence with env vars (#21568)</p></li>
 <li><p>Update error docs to include before_send option (#21275)</p></li>
 <li><p>Augment xcom docs (#20755)</p></li>
-<li><p>Add documentation and release policy on “latest” constraints (#21093)</p></li>
+<li><p>Add documentation and release policy on &quot;latest&quot; constraints (#21093)</p></li>
 <li><p>Add a link to the DAG model in the Python API reference (#21060)</p></li>
 <li><p>Added an enum param example (#20841)</p></li>
 <li><p>Compare taskgroup and subdag (#20700)</p></li>
@@ -2691,7 +2696,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Fix log timezone in task log view (#19342) (#19401)</p></li>
 <li><p>Fix: Add taskgroup tooltip to graph view (#19083)</p></li>
 <li><p>Rename execution date in forms and tables (#19063)</p></li>
-<li><p>Simplify “invalid TI state” message (#19029)</p></li>
+<li><p>Simplify &quot;invalid TI state&quot; message (#19029)</p></li>
 <li><p>Handle case of nonexistent file when preparing file path queue (#18998)</p></li>
 <li><p>Do not create dagruns for DAGs with import errors  (#19367)</p></li>
 <li><p>Fix field relabeling when switching between conn types (#19411)</p></li>
@@ -2748,13 +2753,13 @@ and Airflow cannot be embedded in an iframe.</p>
 <li><p>Task should fail immediately when pod is unprocessable (#19359)</p></li>
 <li><p>Fix downgrade for a DB Migration (#19390)</p></li>
 <li><p>Only mark SchedulerJobs as failed, not any jobs (#19375)</p></li>
-<li><p>Fix message on “Mark as” confirmation page (#19363)</p></li>
+<li><p>Fix message on &quot;Mark as&quot; confirmation page (#19363)</p></li>
 <li><p>Bugfix: Check next run exists before reading data interval (#19307)</p></li>
 <li><p>Fix MySQL db migration with default encoding/collation (#19268)</p></li>
 <li><p>Fix hidden tooltip position (#19261)</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">sqlite_default</span></code> Connection has been hard-coded to <code class="docutils literal notranslate"><span class="pre">/tmp</span></code>, use <code class="docutils literal notranslate"><span class="pre">gettempdir</span></code> instead (#19255)</p></li>
 <li><p>Fix Toggle Wrap on DAG code page (#19211)</p></li>
-<li><p>Clarify “dag not found” error message in CLI (#19338)</p></li>
+<li><p>Clarify &quot;dag not found&quot; error message in CLI (#19338)</p></li>
 <li><p>Add Note to SLA regarding <code class="docutils literal notranslate"><span class="pre">schedule_interval</span></code> (#19173)</p></li>
 <li><p>Use <code class="docutils literal notranslate"><span class="pre">execution_date</span></code> to check for existing <code class="docutils literal notranslate"><span class="pre">DagRun</span></code> for <code class="docutils literal notranslate"><span class="pre">TriggerDagRunOperator</span></code> (#18968)</p></li>
 <li><p>Add explicit session parameter in <code class="docutils literal notranslate"><span class="pre">PoolSlotsAvailableDep</span></code> (#18875)</p></li>
@@ -2765,7 +2770,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <div class="section" id="id13">
 <h3>Doc only changes<a class="headerlink" href="#id13" title="Permalink to this headline">¶</a></h3>
 <ul class="simple">
-<li><p>Add missing parameter documentation for “timetable” (#19282)</p></li>
+<li><p>Add missing parameter documentation for &quot;timetable&quot; (#19282)</p></li>
 <li><p>Improve Kubernetes Executor docs (#19339)</p></li>
 <li><p>Update image tag used in docker docs</p></li>
 </ul>
@@ -2776,12 +2781,12 @@ and Airflow cannot be embedded in an iframe.</p>
 <div class="section" id="id14">
 <h3>Significant Changes<a class="headerlink" href="#id14" title="Permalink to this headline">¶</a></h3>
 <div class="section" id="param-s-default-value-for-default-removed">
-<h4><code class="docutils literal notranslate"><span class="pre">Param</span></code>’s default value for <code class="docutils literal notranslate"><span class="pre">default</span></code> removed<a class="headerlink" href="#param-s-default-value-for-default-removed" title="Permalink to this headline">¶</a></h4>
+<h4><code class="docutils literal notranslate"><span class="pre">Param</span></code>'s default value for <code class="docutils literal notranslate"><span class="pre">default</span></code> removed<a class="headerlink" href="#param-s-default-value-for-default-removed" title="Permalink to this headline">¶</a></h4>
 <p><code class="docutils literal notranslate"><span class="pre">Param</span></code>, introduced in Airflow 2.2.0, accidentally set the default value to <code class="docutils literal notranslate"><span class="pre">None</span></code>. This default has been removed. If you want <code class="docutils literal notranslate"><span class="pre">None</span></code> as your default, explicitly set it as such. For example:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="n">Param</span><span class="p">(</span><span class="kc">None</span><span class="p">,</span> <span class="nb">type</span><span class="o">=</span><span class="p">[</span><span class="s2">&quot;null&quot;</span><span class="p">,</span> <span class="s2">&quot;string&quot;</span><span class="p">])</span>
 </pre></div>
 </div>
-<p>Now if you resolve a <code class="docutils literal notranslate"><span class="pre">Param</span></code> without a default and don’t pass a value, you will get an <code class="docutils literal notranslate"><span class="pre">TypeError</span></code>. For Example:</p>
+<p>Now if you resolve a <code class="docutils literal notranslate"><span class="pre">Param</span></code> without a default and don't pass a value, you will get an <code class="docutils literal notranslate"><span class="pre">TypeError</span></code>. For Example:</p>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="n">Param</span><span class="p">()</span><span class="o">.</span><span class="n">resolve</span><span class="p">()</span>  <span class="c1"># raises TypeError</span>
 </pre></div>
 </div>
@@ -2789,7 +2794,7 @@ and Airflow cannot be embedded in an iframe.</p>
 <div class="section" id="max-queued-runs-per-dag-configuration-has-been-removed">
 <h4><code class="docutils literal notranslate"><span class="pre">max_queued_runs_per_dag</span></code> configuration has been removed<a class="headerlink" href="#max-queued-runs-per-dag-configuration-has-been-removed" title="Permalink to this headline">¶</a></h4>
 <p>The <code class="docutils literal notranslate"><span class="pre">max_queued_runs_per_dag</span></code> configuration option in <code class="docutils literal notranslate"><span class="pre">[core]</span></code> section has been removed. Previously, this controlled the number of queued dagrun
-the scheduler can create in a dag. Now, the maximum number is controlled internally by the DAG’s <code class="docutils literal notranslate"><span class="pre">max_active_runs</span></code></p>
+the scheduler can create in a dag. Now, the maximum number is controlled internally by the DAG's <code class="docutils literal notranslate"><span class="pre">max_active_runs</span></code></p>
 </div>
 </div>
 <div class="section" id="id15">
@@ -2808,18 +2813,18 @@ the scheduler can create in a dag. Now, the maximum number is controlled interna
 <li><p>Warn about unsupported Python 3.10 (#19060)</p></li>
 <li><p>Fix catchup by limiting queued dagrun creation using <code class="docutils literal notranslate"><span class="pre">max_active_runs</span></code> (#18897)</p></li>
 <li><p>Prevent scheduler crash when serialized dag is missing (#19113)</p></li>
-<li><p>Don’t install SQLAlchemy/Pendulum adapters for other DBs (#18745)</p></li>
+<li><p>Don't install SQLAlchemy/Pendulum adapters for other DBs (#18745)</p></li>
 <li><p>Workaround <code class="docutils literal notranslate"><span class="pre">libstdcpp</span></code> TLS error (#19010)</p></li>
 <li><p>Change <code class="docutils literal notranslate"><span class="pre">ds</span></code>, <code class="docutils literal notranslate"><span class="pre">ts</span></code>, etc. back to use logical date (#19088)</p></li>
-<li><p>Ensure task state doesn’t change when marked as failed/success/skipped (#19095)</p></li>
+<li><p>Ensure task state doesn't change when marked as failed/success/skipped (#19095)</p></li>
 <li><p>Relax packaging requirement (#19087)</p></li>
 <li><p>Rename trigger page label to Logical Date (#19061)</p></li>
 <li><p>Allow Param to support a default value of <code class="docutils literal notranslate"><span class="pre">None</span></code> (#19034)</p></li>
 <li><p>Upgrade old DAG/task param format when deserializing from the DB (#18986)</p></li>
-<li><p>Don’t bake ENV and _cmd into tmp config for non-sudo (#18772)</p></li>
+<li><p>Don't bake ENV and _cmd into tmp config for non-sudo (#18772)</p></li>
 <li><p>CLI: Fail <code class="docutils literal notranslate"><span class="pre">backfill</span></code> command before loading DAGs if missing args (#18994)</p></li>
 <li><p>BugFix: Null execution date on insert to <code class="docutils literal notranslate"><span class="pre">task_fail</span></code> violating NOT NULL (#18979)</p></li>
-<li><p>Try to move “dangling” rows in db upgrade (#18953)</p></li>
+<li><p>Try to move &quot;dangling&quot; rows in db upgrade (#18953)</p></li>
 <li><p>Row lock TI query in <code class="docutils literal notranslate"><span class="pre">SchedulerJob._process_executor_events</span></code> (#18975)</p></li>
 <li><p>Sentry before send fallback (#18980)</p></li>
 <li><p>Fix <code class="docutils literal notranslate"><span class="pre">XCom.delete</span></code> error in Airflow 2.2.0 (#18956)</p></li>
@@ -2929,7 +2934,7 @@ per task.</p>
 <h4><code class="docutils literal notranslate"><span class="pre">processor_poll_interval</span></code> config have been renamed to <code class="docutils literal notranslate"><span class="pre">scheduler_idle_sleep_time</span></code><a class="headerlink" href="#processor-poll-interval-config-have-been-renamed-to-scheduler-idle-sleep-time" title="Permalink to this headline">¶</a></h4>
 <p><code class="docutils literal notranslate"><span class="pre">[scheduler]</span> <span class="pre">processor_poll_interval</span></code> setting in <code class="docutils literal notranslate"><span class="pre">airflow.cfg</span></code> has been renamed to <code class="docutils literal notranslate"><span class="pre">[scheduler]</span> <span class="pre">scheduler_idle_sleep_time</span></code>
 for better understanding.</p>
-<p>It controls the ‘time to sleep’ at the end of the Scheduler loop if nothing was scheduled inside <code class="docutils literal notranslate"><span class="pre">SchedulerJob</span></code>.</p>
+<p>It controls the 'time to sleep' at the end of the Scheduler loop if nothing was scheduled inside <code class="docutils literal notranslate"><span class="pre">SchedulerJob</span></code>.</p>
 <p><strong>Before</strong>:</p>
 <div class="highlight-ini notranslate"><div class="highlight"><pre><span></span><span class="k">[scheduler]</span><span class="w"></span>
 <span class="na">processor_poll_interval</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">16</span><span class="w"></span>
@@ -2963,15 +2968,15 @@ this setting controlled DAG Serialization.</p>
 <div class="section" id="remove-taskinstance-log-filepath-attribute">
 <h4>Remove <code class="docutils literal notranslate"><span class="pre">TaskInstance.log_filepath</span></code> attribute<a class="headerlink" href="#remove-taskinstance-log-filepath-attribute" title="Permalink to this headline">¶</a></h4>
 <p>This method returned incorrect values for a long time, because it did not take into account the different
-logger configuration and task retries. We have also started supporting more advanced tools that don’t use
-files, so it is impossible to determine the correct file path in every case e.g. Stackdriver doesn’t use files
+logger configuration and task retries. We have also started supporting more advanced tools that don't use
+files, so it is impossible to determine the correct file path in every case e.g. Stackdriver doesn't use files
 but identifies logs based on labels.  For this reason, we decided to delete this attribute.</p>
 <p>If you need to read logs, you can use <code class="docutils literal notranslate"><span class="pre">airflow.utils.log.log_reader.TaskLogReader</span></code> class, which does not have
 the above restrictions.</p>
 </div>
 <div class="section" id="if-a-sensor-times-out-it-will-not-retry">
 <h4>If a sensor times out, it will not retry<a class="headerlink" href="#if-a-sensor-times-out-it-will-not-retry" title="Permalink to this headline">¶</a></h4>
-<p>Previously, a sensor is retried when it times out until the number of <code class="docutils literal notranslate"><span class="pre">retries</span></code> are exhausted. So the effective timeout of a sensor is <code class="docutils literal notranslate"><span class="pre">timeout</span> <span class="pre">*</span> <span class="pre">(retries</span> <span class="pre">+</span> <span class="pre">1)</span></code>. This behaviour is now changed. A sensor will immediately fail without retrying if [...]
+<p>Previously, a sensor is retried when it times out until the number of <code class="docutils literal notranslate"><span class="pre">retries</span></code> are exhausted. So the effective timeout of a sensor is <code class="docutils literal notranslate"><span class="pre">timeout</span> <span class="pre">*</span> <span class="pre">(retries</span> <span class="pre">+</span> <span class="pre">1)</span></code>. This behaviour is now changed. A sensor will immediately fail without retrying if [...]
 </div>
 <div class="section" id="default-task-pools-slots-can-be-set-using-core-default-pool-task-slot-count">
 <h4>Default Task Pools Slots can be set using <code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">default_pool_task_slot_count</span></code><a class="headerlink" href="#default-task-pools-slots-can-be-set-using-core-default-pool-task-slot-count" title="Permalink to this headline">¶</a></h4>
@@ -2990,7 +2995,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <h4>TaskInstances now <em>require</em> a DagRun<a class="headerlink" href="#taskinstances-now-require-a-dagrun" title="Permalink to this headline">¶</a></h4>
 <p>Under normal operation every TaskInstance row in the database would have DagRun row too, but it was possible to manually delete the DagRun and Airflow would still schedule the TaskInstances.</p>
 <p>In Airflow 2.2 we have changed this and now there is a database-level foreign key constraint ensuring that every TaskInstance has a DagRun row.</p>
-<p>Before updating to this 2.2 release you will have to manually resolve any inconsistencies (add back DagRun rows, or delete TaskInstances) if you have any “dangling” TaskInstance” rows.</p>
+<p>Before updating to this 2.2 release you will have to manually resolve any inconsistencies (add back DagRun rows, or delete TaskInstances) if you have any &quot;dangling&quot; TaskInstance&quot; rows.</p>
 <p>As part of this change the <code class="docutils literal notranslate"><span class="pre">clean_tis_without_dagrun_interval</span></code> config option under <code class="docutils literal notranslate"><span class="pre">[scheduler]</span></code> section has been removed and has no effect.</p>
 </div>
 <div class="section" id="taskinstance-and-taskreschedule-now-define-run-id-instead-of-execution-date">
@@ -3009,7 +3014,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>AIP-39: Add (customizable) Timetable class to Airflow for richer scheduling behaviour (#15397, #16030,
 #16352, #17030, #17122, #17414, #17552, #17755, #17989, #18084, #18088, #18244, #18266, #18420, #18434,
 #18421, #18475, #18499, #18573, #18522, #18729, #18706, #18742, #18786, #18804)</p></li>
-<li><p>AIP-40: Add Deferrable “Async” Tasks (#15389, #17564, #17565, #17601, #17745, #17747, #17748, #17875,
+<li><p>AIP-40: Add Deferrable &quot;Async&quot; Tasks (#15389, #17564, #17565, #17601, #17745, #17747, #17748, #17875,
 #17876, #18129, #18210, #18214, #18552, #18728, #18414)</p></li>
 <li><p>Add a Docker Taskflow decorator (#15330, #18739)</p></li>
 <li><p>Add Airflow Standalone command (#15826)</p></li>
@@ -3047,7 +3052,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Small improvements for Airflow UI (#18715, #18795)</p></li>
 <li><p>Rename <code class="docutils literal notranslate"><span class="pre">processor_poll_interval</span></code> to <code class="docutils literal notranslate"><span class="pre">scheduler_idle_sleep_time</span></code> (#18704)</p></li>
 <li><p>Check the allowed values for the logging level (#18651)</p></li>
-<li><p>Fix error on triggering a dag that doesn’t exist using <code class="docutils literal notranslate"><span class="pre">dagrun_conf</span></code> (#18655)</p></li>
+<li><p>Fix error on triggering a dag that doesn't exist using <code class="docutils literal notranslate"><span class="pre">dagrun_conf</span></code> (#18655)</p></li>
 <li><p>Add muldelete action to <code class="docutils literal notranslate"><span class="pre">TaskInstanceModelView</span></code> (#18438)</p></li>
 <li><p>Avoid importing DAGs during clean DB installation (#18450)</p></li>
 <li><p>Require can_edit on DAG privileges to modify TaskInstances and DagRuns (#16634)</p></li>
@@ -3067,7 +3072,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Refactor <code class="docutils literal notranslate"><span class="pre">BranchDayOfWeekOperator</span></code>, <code class="docutils literal notranslate"><span class="pre">DayOfWeekSensor</span></code> (#17940)</p></li>
 <li><p>Update error message to guide the user into self-help mostly (#17929)</p></li>
 <li><p>Update to Celery 5 (#17397)</p></li>
-<li><p>Add links to provider’s documentation (#17736)</p></li>
+<li><p>Add links to provider's documentation (#17736)</p></li>
 <li><p>Remove Marshmallow schema warnings (#17753)</p></li>
 <li><p>Rename <code class="docutils literal notranslate"><span class="pre">none_failed_or_skipped</span></code> by <code class="docutils literal notranslate"><span class="pre">none_failed_min_one_success</span></code> trigger rule (#17683)</p></li>
 <li><p>Remove <code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">store_dag_code</span></code> &amp; use DB to get Dag Code (#16342)</p></li>
@@ -3081,7 +3086,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Use gunicorn to serve logs generated by worker (#17591)</p></li>
 <li><p>Improve validation of Group id (#17578)</p></li>
 <li><p>Simplify 404 page (#17501)</p></li>
-<li><p>Add XCom.clear so it’s hookable in custom XCom backend (#17405)</p></li>
+<li><p>Add XCom.clear so it's hookable in custom XCom backend (#17405)</p></li>
 <li><p>Add deprecation notice for <code class="docutils literal notranslate"><span class="pre">SubDagOperator</span></code> (#17488)</p></li>
 <li><p>Support DAGS folder being in different location on scheduler and runners (#16860)</p></li>
 <li><p>Remove /dagrun/create and disable edit form generated by F.A.B (#17376)</p></li>
@@ -3116,7 +3121,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Marking success/failed automatically clears failed downstream tasks  (#13037)</p></li>
 <li><p>Add close/open indicator for import dag errors (#16073)</p></li>
 <li><p>Add collapsible import errors (#16072)</p></li>
-<li><p>Always return a response in TI’s <code class="docutils literal notranslate"><span class="pre">action_clear</span></code> view (#15980)</p></li>
+<li><p>Always return a response in TI's <code class="docutils literal notranslate"><span class="pre">action_clear</span></code> view (#15980)</p></li>
 <li><p>Add cli command to delete user by email (#15873)</p></li>
 <li><p>Use resource and action names for FAB permissions (#16410)</p></li>
 <li><p>Rename DAG concurrency (<code class="docutils literal notranslate"><span class="pre">[core]</span> <span class="pre">dag_concurrency</span></code>) settings for easier understanding (#16267, #18730)</p></li>
@@ -3140,12 +3145,12 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Only show the task modal if it is a valid instance (#18570)</p></li>
 <li><p>Fix accessing rendered <code class="docutils literal notranslate"><span class="pre">{{</span> <span class="pre">task.x</span> <span class="pre">}}</span></code> attributes from within templates (#18516)</p></li>
 <li><p>Add missing email type of connection (#18502)</p></li>
-<li><p>Don’t use flash for “same-page” UI messages. (#18462)</p></li>
+<li><p>Don't use flash for &quot;same-page&quot; UI messages. (#18462)</p></li>
 <li><p>Fix task group tooltip (#18406)</p></li>
 <li><p>Properly fix dagrun update state endpoint (#18370)</p></li>
 <li><p>Properly handle ti state difference between executor and scheduler (#17819)</p></li>
-<li><p>Fix stuck “queued” tasks in KubernetesExecutor (#18152)</p></li>
-<li><p>Don’t permanently add zip DAGs to <code class="docutils literal notranslate"><span class="pre">sys.path</span></code> (#18384)</p></li>
+<li><p>Fix stuck &quot;queued&quot; tasks in KubernetesExecutor (#18152)</p></li>
+<li><p>Don't permanently add zip DAGs to <code class="docutils literal notranslate"><span class="pre">sys.path</span></code> (#18384)</p></li>
 <li><p>Fix random deadlocks in MSSQL database (#18362)</p></li>
 <li><p>Deactivating DAGs which have been removed from files (#17121)</p></li>
 <li><p>When syncing dags to db remove <code class="docutils literal notranslate"><span class="pre">dag_tag</span></code> rows that are now unused (#8231)</p></li>
@@ -3173,7 +3178,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Fixing bug which restricted the visibility of ImportErrors (#17924)</p></li>
 <li><p>Fix grammar in <code class="docutils literal notranslate"><span class="pre">traceback.html</span></code> (#17942)</p></li>
 <li><p>Fix <code class="docutils literal notranslate"><span class="pre">DagRunState</span></code> enum query for <code class="docutils literal notranslate"><span class="pre">MySQLdb</span></code> driver (#17886)</p></li>
-<li><p>Fixed button size in “Actions” group. (#17902)</p></li>
+<li><p>Fixed button size in &quot;Actions&quot; group. (#17902)</p></li>
 <li><p>Only show import errors for DAGs a user can access (#17835)</p></li>
 <li><p>Show all import_errors from zip files (#17759)</p></li>
 <li><p>fix EXTRA_LOGGER_NAMES param and related docs (#17808)</p></li>
@@ -3232,7 +3237,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Add Brent to Committers list (#17873)</p></li>
 <li><p>Improves documentation about modules management (#17757)</p></li>
 <li><p>Remove deprecated metrics from metrics.rst (#17772)</p></li>
-<li><p>Make sure “production-readiness” of docker-compose is well explained (#17731)</p></li>
+<li><p>Make sure &quot;production-readiness&quot; of docker-compose is well explained (#17731)</p></li>
 <li><p>Doc: Update Upgrade to v2 docs with Airflow 1.10.x EOL dates (#17710)</p></li>
 <li><p>Doc: Replace deprecated param from docstrings (#17709)</p></li>
 <li><p>Describe dag owner more carefully (#17699)</p></li>
@@ -3288,7 +3293,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Silence warnings in tests from using SubDagOperator (#18275)</p></li>
 <li><p>Fix usage of <code class="docutils literal notranslate"><span class="pre">range(len())</span></code> to <code class="docutils literal notranslate"><span class="pre">enumerate</span></code> (#18174)</p></li>
 <li><p>Test coverage on the autocomplete view (#15943)</p></li>
-<li><p>Add “packaging” to core requirements (#18122)</p></li>
+<li><p>Add &quot;packaging&quot; to core requirements (#18122)</p></li>
 <li><p>Adds LoggingMixins to BaseTrigger (#18106)</p></li>
 <li><p>Fix building docs in <code class="docutils literal notranslate"><span class="pre">main</span></code> builds (#18035)</p></li>
 <li><p>Remove upper-limit on <code class="docutils literal notranslate"><span class="pre">tenacity</span></code> (#17593)</p></li>
@@ -3350,7 +3355,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Fix wrong query on running tis (#17631)</p></li>
 <li><p>Add root to tree refresh url (#17633)</p></li>
 <li><p>Do not delete running DAG from the UI (#17630)</p></li>
-<li><p>Improve discoverability of Provider packages’ functionality</p></li>
+<li><p>Improve discoverability of Provider packages' functionality</p></li>
 <li><p>Do not let <code class="docutils literal notranslate"><span class="pre">create_dagrun</span></code> overwrite explicit <code class="docutils literal notranslate"><span class="pre">run_id</span></code> (#17728)</p></li>
 <li><p>Regression on pid reset to allow task start after heartbeat (#17333)</p></li>
 <li><p>Set task state to failed when pod is DELETED while running (#18095)</p></li>
@@ -3387,12 +3392,12 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Fix task retries when they receive <code class="docutils literal notranslate"><span class="pre">sigkill</span></code> and have retries and properly handle <code class="docutils literal notranslate"><span class="pre">sigterm</span></code> (#16301)</p></li>
 <li><p>Fix redacting secrets in context exceptions. (#17618)</p></li>
 <li><p>Fix race condition with dagrun callbacks (#16741)</p></li>
-<li><p>Add ‘queued’ to DagRunState (#16854)</p></li>
-<li><p>Add ‘queued’ state to DagRun (#16401)</p></li>
+<li><p>Add 'queued' to DagRunState (#16854)</p></li>
+<li><p>Add 'queued' state to DagRun (#16401)</p></li>
 <li><p>Fix external elasticsearch logs link (#16357)</p></li>
 <li><p>Add proper warning message when recorded PID is different from current PID (#17411)</p></li>
 <li><p>Fix running tasks with <code class="docutils literal notranslate"><span class="pre">default_impersonation</span></code> config (#17229)</p></li>
-<li><p>Rescue if a DagRun’s DAG was removed from db (#17544)</p></li>
+<li><p>Rescue if a DagRun's DAG was removed from db (#17544)</p></li>
 <li><p>Fixed broken json_client (#17529)</p></li>
 <li><p>Handle and log exceptions raised during task callback (#17347)</p></li>
 <li><p>Fix CLI <code class="docutils literal notranslate"><span class="pre">kubernetes</span> <span class="pre">cleanup-pods</span></code> which fails on invalid label key (#17298)</p></li>
@@ -3453,7 +3458,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <h3>Bug Fixes<a class="headerlink" href="#id34" title="Permalink to this headline">¶</a></h3>
 <ul class="simple">
 <li><p>Only allow webserver to request from the worker log server (#16754)</p></li>
-<li><p>Fix “Invalid JSON configuration, must be a dict” bug (#16648)</p></li>
+<li><p>Fix &quot;Invalid JSON configuration, must be a dict&quot; bug (#16648)</p></li>
 <li><p>Fix <code class="docutils literal notranslate"><span class="pre">CeleryKubernetesExecutor</span></code> (#16700)</p></li>
 <li><p>Mask value if the key is <code class="docutils literal notranslate"><span class="pre">token</span></code> (#16474)</p></li>
 <li><p>Fix impersonation issue with <code class="docutils literal notranslate"><span class="pre">LocalTaskJob</span></code> (#16852)</p></li>
@@ -3483,7 +3488,7 @@ not have any effect in an existing deployment where the <code class="docutils li
 <div class="section" id="id38">
 <h3>Bug Fixes<a class="headerlink" href="#id38" title="Permalink to this headline">¶</a></h3>
 <ul class="simple">
-<li><p>Don’t crash attempting to mask secrets in dict with non-string keys (#16601)</p></li>
+<li><p>Don't crash attempting to mask secrets in dict with non-string keys (#16601)</p></li>
 <li><p>Always install sphinx_airflow_theme from <code class="docutils literal notranslate"><span class="pre">PyPI</span></code> (#16594)</p></li>
 <li><p>Remove limitation for elasticsearch library (#16553)</p></li>
 <li><p>Adding extra requirements for build and runtime of the PROD image. (#16170)</p></li>
@@ -3497,11 +3502,11 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Fix DAG run state not updated while DAG is paused (#16343)</p></li>
 <li><p>Allow null value for operator field in task_instance schema(REST API) (#16516)</p></li>
 <li><p>Avoid recursion going too deep when redacting logs (#16491)</p></li>
-<li><p>Backfill: Don’t create a DagRun if no tasks match task regex (#16461)</p></li>
+<li><p>Backfill: Don't create a DagRun if no tasks match task regex (#16461)</p></li>
 <li><p>Tree View UI for larger DAGs &amp; more consistent spacing in Tree View (#16522)</p></li>
 <li><p>Correctly handle None returns from Query.scalar() (#16345)</p></li>
 <li><p>Adding <code class="docutils literal notranslate"><span class="pre">only_active</span></code> parameter to /dags endpoint (#14306)</p></li>
-<li><p>Don’t show stale Serialized DAGs if they are deleted in DB (#16368)</p></li>
+<li><p>Don't show stale Serialized DAGs if they are deleted in DB (#16368)</p></li>
 <li><p>Make REST API List DAGs endpoint consistent with UI/CLI behaviour (#16318)</p></li>
 <li><p>Support remote logging in elasticsearch with <code class="docutils literal notranslate"><span class="pre">filebeat</span> <span class="pre">7</span></code> (#14625)</p></li>
 <li><p>Queue tasks with higher priority and earlier execution_date first. (#15210)</p></li>
@@ -3513,14 +3518,14 @@ not have any effect in an existing deployment where the <code class="docutils li
 <li><p>Add <code class="docutils literal notranslate"><span class="pre">passphrase</span></code> and <code class="docutils literal notranslate"><span class="pre">private_key</span></code> to default sensitive field names (#16392)</p></li>
 <li><p>Fix tasks in an infinite slots pool were never scheduled (#15247)</p></li>
 <li><p>Fix Orphaned tasks stuck in CeleryExecutor as running (#16550)</p></li>
-<li><p>Don’t fail to log if we can’t redact something (#16118)</p></li>
+<li><p>Don't fail to log if we can't redact something (#16118)</p></li>
 <li><p>Set max tree width to 1200 pixels (#16067)</p></li>
-<li><p>Fill the “job_id” field for <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">task</span> <span class="pre">run</span></code> without <code class="docutils literal notranslate"><span class="pre">--local</span></code>/<code class="docutils literal notranslate"><span class="pre">--raw</span></code> for KubeExecutor (#16108)</p></li>
+<li><p>Fill the &quot;job_id&quot; field for <code class="docutils literal notranslate"><span class="pre">airflow</span> <span class="pre">task</span> <span class="pre">run</span></code> without <code class="docutils literal notranslate"><span class="pre">--local</span></code>/<code class="docutils literal notranslate"><span class="pre">--raw</span></code> for KubeExecutor (#16108)</p></li>
 <li><p>Fixes problem where conf variable was used before initialization (#16088)</p></li>
 <li><p>Fix apply defaults for task decorator (#16085)</p></li>
 <li><p>Parse recently modified files even if just parsed (#16075)</p></li>
-<li><p>Ensure that we don’t try to mask empty string in logs (#16057)</p></li>
-<li><p>Don’t die when masking <code class="docutils literal notranslate"><span class="pre">log.exception</span></code> when there is no exception (#16047)</p></li>
+<li><p>Ensure that we don't try to mask empty string in logs (#16057)</p></li>
+<li><p>Don't die when masking <code class="docutils literal notranslate"><span class="pre">log.exception</span></code> when there is no exception (#16047)</p></li>
 <li><p>Restores apply_defaults import in base_sensor_operator (#16040)</p></li>
 <li><p>Fix auto-refresh in tree view When webserver ui is not in <code class="docutils literal notranslate"><span class="pre">/</span></code> (#16018)</p></li>
 <li><p>Fix dag.clear() to set multiple dags to running when necessary (#15382)</p></li>
@@ -3533,8 +3538,8 @@ not have any effect in an existing deployment where the <code class="docutils li
 <div class="section" id="id39">
 <h3>Significant Changes<a class="headerlink" href="#id39" title="Permalink to this headline">¶</a></h3>
 <div class="section" id="new-deprecated-api-extra">
-<h4>New “deprecated_api” extra<a class="headerlink" href="#new-deprecated-api-extra" title="Permalink to this headline">¶</a></h4>
-<p>We have a new ‘[deprecated_api]’ extra that should be used when installing airflow when the deprecated API
+<h4>New &quot;deprecated_api&quot; extra<a class="headerlink" href="#new-deprecated-api-extra" title="Permalink to this headline">¶</a></h4>
+<p>We have a new '[deprecated_api]' extra that should be used when installing airflow when the deprecated API
 is going to be used. This is now an optional feature of Airflow now because it pulls in <code class="docutils literal notranslate"><span class="pre">requests</span></code> which
 (as of 14 May 2021) pulls LGPL <code class="docutils literal notranslate"><span class="pre">chardet</span></code> dependency.</p>
 </div>
@@ -3545,12 +3550,12 @@ dependency of <code class="docutils literal notranslate"><span class="pre">reque
 See <a class="reference external" href="https://github.com/psf/requests/pull/5797">PR to replace chardet with charset-normalizer</a></p>
 </div>
 <div class="section" id="apply-default-decorator-isn-t-longer-necessary">
-<h4><code class="docutils literal notranslate"><span class="pre">&#64;apply_default</span></code> decorator isn’t longer necessary<a class="headerlink" href="#apply-default-decorator-isn-t-longer-necessary" title="Permalink to this headline">¶</a></h4>
+<h4><code class="docutils literal notranslate"><span class="pre">&#64;apply_default</span></code> decorator isn't longer necessary<a class="headerlink" href="#apply-default-decorator-isn-t-longer-necessary" title="Permalink to this headline">¶</a></h4>
 <p>This decorator is now automatically added to all operators via the metaclass on BaseOperator</p>
 </div>
 <div class="section" id="change-the-configuration-options-for-field-masking">
 <h4>Change the configuration options for field masking<a class="headerlink" href="#change-the-configuration-options-for-field-masking" title="Permalink to this headline">¶</a></h4>
-<p>We’ve improved masking for sensitive data in Web UI and logs. As part of it, the following configurations have been changed:</p>
+<p>We've improved masking for sensitive data in Web UI and logs. As part of it, the following configurations have been changed:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">hide_sensitive_variable_fields</span></code> option in <code class="docutils literal notranslate"><span class="pre">admin</span></code> section has been replaced by <code class="docutils literal notranslate"><span class="pre">hide_sensitive_var_conn_fields</span></code> section in <code class="docutils literal notranslate"><span class="pre">core</span></code> section,</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">sensitive_variable_fields</span></code> option in <code class="docutils literal notranslate"><span class="pre">admin</span></code> section has been replaced by <code class="docutils literal notranslate"><span class="pre">sensitive_var_conn_names</span></code> section in <code class="docutils literal notranslate"><span class="pre">core</span></code> section.</p></li>
@@ -3594,13 +3599,13 @@ serve as a DagBag cache burst time.</p>
 <li><p>Add rest API to query for providers (#13394)</p></li>
 <li><p>Mask passwords and sensitive info in task logs and UI (#15599)</p></li>
 <li><p>Add <code class="docutils literal notranslate"><span class="pre">SubprocessHook</span></code> for running commands from operators (#13423)</p></li>
-<li><p>Add DAG Timeout in UI page “DAG Details” (#14165)</p></li>
+<li><p>Add DAG Timeout in UI page &quot;DAG Details&quot; (#14165)</p></li>
 <li><p>Add <code class="docutils literal notranslate"><span class="pre">WeekDayBranchOperator</span></code> (#13997)</p></li>
 <li><p>Add JSON linter to DAG Trigger UI (#13551)</p></li>
 <li><p>Add DAG Description Doc to Trigger UI Page (#13365)</p></li>
 <li><p>Add airflow webserver URL into SLA miss email. (#13249)</p></li>
 <li><p>Add read only REST API endpoints for users (#14735)</p></li>
-<li><p>Add files to generate Airflow’s Python SDK (#14739)</p></li>
+<li><p>Add files to generate Airflow's Python SDK (#14739)</p></li>
 <li><p>Add dynamic fields to snowflake connection (#14724)</p></li>
 <li><p>Add read only REST API endpoint for roles and permissions (#14664)</p></li>
 <li><p>Add new datetime branch operator (#11964)</p></li>
@@ -3641,7 +3646,7 @@ serve as a DagBag cache burst time.</p>
 <li><p>Add an option to trigger a dag w/o changing conf (#15591)</p></li>
 <li><p>Add Airflow UI instance_name configuration option (#10162)</p></li>
 <li><p>Add a decorator to retry functions with DB transactions (#14109)</p></li>
-<li><p>Add return to PythonVirtualenvOperator’s execute method (#14061)</p></li>
+<li><p>Add return to PythonVirtualenvOperator's execute method (#14061)</p></li>
 <li><p>Add verify_ssl config for kubernetes (#13516)</p></li>
 <li><p>Add description about <code class="docutils literal notranslate"><span class="pre">secret_key</span></code> when Webserver &gt; 1 (#15546)</p></li>
 <li><p>Add Traceback in LogRecord in <code class="docutils literal notranslate"><span class="pre">JSONFormatter</span></code> (#15414)</p></li>
@@ -3655,7 +3660,7 @@ serve as a DagBag cache burst time.</p>
 <li><p>Deactivate trigger, refresh, and delete controls on dag detail view. (#14144)</p></li>
 <li><p>Turn off autocomplete for connection forms (#15073)</p></li>
 <li><p>Increase default <code class="docutils literal notranslate"><span class="pre">worker_refresh_interval</span></code> to <code class="docutils literal notranslate"><span class="pre">6000</span></code> seconds (#14970)</p></li>
-<li><p>Only show User’s local timezone if it’s not UTC (#13904)</p></li>
+<li><p>Only show User's local timezone if it's not UTC (#13904)</p></li>
 <li><p>Suppress LOG/WARNING for a few tasks CLI for better CLI experience (#14567)</p></li>
 <li><p>Configurable API response (CORS) headers (#13620)</p></li>
 <li><p>Allow viewers to see all docs links (#14197)</p></li>
@@ -3669,7 +3674,7 @@ serve as a DagBag cache burst time.</p>
 <h3>Bug Fixes<a class="headerlink" href="#id42" title="Permalink to this headline">¶</a></h3>
 <ul class="simple">
 <li><p>Fix 500 error from <code class="docutils literal notranslate"><span class="pre">updateTaskInstancesState</span></code> API endpoint when <code class="docutils literal notranslate"><span class="pre">dry_run</span></code> not passed (#15889)</p></li>
-<li><p>Ensure that task preceding a PythonVirtualenvOperator doesn’t fail (#15822)</p></li>
+<li><p>Ensure that task preceding a PythonVirtualenvOperator doesn't fail (#15822)</p></li>
 <li><p>Prevent mixed case env vars from crashing processes like worker (#14380)</p></li>
 <li><p>Fixed type annotations in DAG decorator (#15778)</p></li>
 <li><p>Fix on_failure_callback when task receive SIGKILL (#15537)</p></li>
@@ -3684,7 +3689,7 @@ serve as a DagBag cache burst time.</p>
... 3348 lines suppressed ...