diff --git a/docs/concepts.rst b/docs/concepts.rst
index b8e036cd74..6f304bfda7 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 d3664b94ff..87235aa6b6 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