[airflow] branch master updated: Fix some typos in celery_kubernetes.rst (#13606)

[ka...@apache.org]

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

kamilbregula pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/master by this push:
     new 2909c38  Fix some typos in celery_kubernetes.rst (#13606)
2909c38 is described below

commit 2909c389d45f0ef4cc9deb456e0e96e52428ff10
Author: andrzejsydor <an...@users.noreply.github.com>
AuthorDate: Thu Jan 14 15:27:10 2021 +0100

    Fix some typos in celery_kubernetes.rst (#13606)
    
    fix some typos
---
 docs/apache-airflow/executor/celery_kubernetes.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/apache-airflow/executor/celery_kubernetes.rst b/docs/apache-airflow/executor/celery_kubernetes.rst
index 28e37f9..6e2471b 100644
--- a/docs/apache-airflow/executor/celery_kubernetes.rst
+++ b/docs/apache-airflow/executor/celery_kubernetes.rst
@@ -22,22 +22,22 @@ CeleryKubernetes Executor
 =========================
 
 The :class:`~airflow.executors.celery_kubernetes_executor.CeleryKubernetesExecutor` allows users
-to run simultaneously ``CeleryExecutor`` and a ``KubernetesExecutor``.
+to run simultaneously a ``CeleryExecutor`` and a ``KubernetesExecutor``.
 An executor is chosen to run a task based on the task's queue.
 
-``CeleryKubernetesExecutor`` inherits the scalability of ``CeleryExecutor`` to
-handle the high load at the peak time and runtime isolation of ``KubernetesExecutor``.
+``CeleryKubernetesExecutor`` inherits the scalability of the ``CeleryExecutor`` to
+handle the high load at the peak time and runtime isolation of the ``KubernetesExecutor``.
 
 
 When to use CeleryKubernetesExecutor
 ####################################
 
-``CeleryKubernetesExecutor`` should only be used at certain cases, given that
-it requires setting up ``CeleryExecutor`` and ``KubernetesExecutor``.
+The ``CeleryKubernetesExecutor`` should only be used at certain cases, given that
+it requires setting up the ``CeleryExecutor`` and the ``KubernetesExecutor``.
 
-We recommend considering ``CeleryKubernetesExecutor`` when your use case meets:
+We recommend considering the ``CeleryKubernetesExecutor`` when your use case meets:
 
-1. The number of tasks needed to be scheduled at the peak exceeds the scale that your kubernetes cluster
+1. The number of tasks needed to be scheduled at the peak exceeds the scale that your Kubernetes cluster
    can comfortably handle
 
 2. A relative small portion of your tasks requires runtime isolation.