This is an automated email from the ASF dual-hosted git repository.
pierrejeambrun pushed a commit to branch v2-5-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v2-5-test by this push:
new f7c473033a Fixed typo (#28687)
f7c473033a is described below
commit f7c473033a4befc382f5ca226d103b1d3f80f4e9
Author: Adylzhan Khashtamov <[email protected]>
AuthorDate: Tue Jan 3 12:11:34 2023 +0300
Fixed typo (#28687)
(cherry picked from commit e598a1b294956448928c82a444e081ff67c6aa47)
---
docs/apache-airflow/concepts/scheduler.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/apache-airflow/concepts/scheduler.rst
b/docs/apache-airflow/concepts/scheduler.rst
index d9ba22be82..10057c386d 100644
--- a/docs/apache-airflow/concepts/scheduler.rst
+++ b/docs/apache-airflow/concepts/scheduler.rst
@@ -280,7 +280,7 @@ When you know what your resource usage is, the improvements
that you can conside
parsed continuously so optimizing that code might bring tremendous
improvements, especially if you try
to reach out to some external databases etc. while parsing DAGs (this should
be avoided at all cost).
The :ref:`best_practices/top_level_code` explains what are the best
practices for writing your top-level
- Python code. The :ref:`best_practices/reducing_dag_complexity` document
provides some ares that you might
+ Python code. The :ref:`best_practices/reducing_dag_complexity` document
provides some areas that you might
look at when you want to reduce complexity of your code.
* improve utilization of your resources. This is when you have a free capacity
in your system that
seems underutilized (again CPU, memory I/O, networking are the prime
candidates) - you can take
