[airflow] branch master updated: Fix typo in Custom XCom backend (#10588)

[ka...@apache.org]

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

kaxilnaik 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 2fc9614  Fix typo in Custom XCom backend (#10588)
2fc9614 is described below

commit 2fc961458ede6a0b40798b36878f75e3aee1fcb3
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Wed Aug 26 19:04:33 2020 +0100

    Fix typo in Custom XCom backend (#10588)
---
 docs/concepts.rst            | 2 +-
 docs/executor/kubernetes.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/concepts.rst b/docs/concepts.rst
index b8e036c..6f304bf 100644
--- a/docs/concepts.rst
+++ b/docs/concepts.rst
@@ -741,7 +741,7 @@ for inter-task communication rather than global settings.
 Custom XCom backend
 -------------------
 
-It is possible to change ``XCom`` behaviour os serialization and deserialization of tasks' result.
+It is possible to change ``XCom`` behaviour of serialization and deserialization of tasks' result.
 To do this one have to change ``xcom_backend`` parameter in Airflow config. Provided value should point
 to a class that is subclass of :class:`~airflow.models.xcom.BaseXCom`. To alter the serialization /
 deserialization mechanism the custom class should override ``serialize_value`` and ``deserialize_value``
diff --git a/docs/executor/kubernetes.rst b/docs/executor/kubernetes.rst
index d3664b9..87235aa 100644
--- a/docs/executor/kubernetes.rst
+++ b/docs/executor/kubernetes.rst
@@ -52,7 +52,7 @@ When a DAG submits a task, the KubernetesExecutor requests a worker pod from the
 
 In contrast to the Celery Executor, the Kubernetes Executor does not require additional components such as Redis and Flower, but does require the Kubernetes infrastructure.
 
-One example of an Airflow deployment running on a distributed set of five nodes in a Kubernetes cluster is shown below. 
+One example of an Airflow deployment running on a distributed set of five nodes in a Kubernetes cluster is shown below.
 
 .. image:: ../img/arch-diag-kubernetes2.png