This is an automated email from the ASF dual-hosted git repository. ephraimanierobi pushed a commit to branch v2-6-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 4f95a6c7ae5b1ba97acb640a84db1a90e8386a66 Author: Jed Cunningham <[email protected]> AuthorDate: Wed May 3 12:06:45 2023 -0500 Fix some typos in the cluster policies docs (#31031) (cherry picked from commit 366ae51e21dfb70da85962ca753e8cba8c4d3ec8) --- .../administration-and-deployment/cluster-policies.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/apache-airflow/administration-and-deployment/cluster-policies.rst b/docs/apache-airflow/administration-and-deployment/cluster-policies.rst index 139e5809d8..ddf05fde69 100644 --- a/docs/apache-airflow/administration-and-deployment/cluster-policies.rst +++ b/docs/apache-airflow/administration-and-deployment/cluster-policies.rst @@ -65,7 +65,7 @@ There are two ways to configure cluster policies: .. note:: |experimental| - This method is more advanced for for people who are already comfortable with python packaging. + This method is more advanced and for people who are already comfortable with python packaging. First create your policy function in a module: @@ -97,9 +97,9 @@ There are two ways to configure cluster policies: [project.entry-points.'airflow.policy'] _ = 'my_airflow_plugin.policies' - The entrypoint group must be ``airflow.policy``, and the name is ignored. The value should be your module (or class) decorated with the ``@hookimpl`` marker + The entrypoint group must be ``airflow.policy``, and the name is ignored. The value should be your module (or class) decorated with the ``@hookimpl`` marker. - One you have done that, and you have installed your distribution into your Airflow env the policy functions will get called by the various Airflow components. (The exact call order is undefined, so don't rely on any particular calling order if you have multiple plugins). + Once you have done that, and you have installed your distribution into your Airflow env, the policy functions will get called by the various Airflow components. (The exact call order is undefined, so don't rely on any particular calling order if you have multiple plugins). One important thing to note (for either means of defining policy functions) is that the argument names must
