diff --git a/Documentation/Books/Manual/Deployment/Kubernetes/Drain.md b/Documentation/Books/Manual/Deployment/Kubernetes/Drain.md
index b0568eb9ff..2f6fc0ec75 100644
--- a/Documentation/Books/Manual/Deployment/Kubernetes/Drain.md
+++ b/Documentation/Books/Manual/Deployment/Kubernetes/Drain.md
@@ -311,9 +311,10 @@ POST /_admin/cluster/cleanOutServer
 
 (please compare the above output of the `/_admin/cluster/health` API).
 The value of the `"server"` attribute should be the name of the DBserver
-which is one the pod which shall be drained next. This uses the UI short
-name, alternatively one can use the internal name, which corresponds to
-the pod name. In our example, the pod name is:
+which is the one in the pod which resides on the node that shall be
+drained next. This uses the UI short name, alternatively one can use the
+internal name, which corresponds to the pod name. In our example, the
+pod name is:
 
 ```
 my-arangodb-cluster-prmr-wbsq47rz-5676ed
diff --git a/Documentation/Books/Manual/Tutorials/Kubernetes/README.md b/Documentation/Books/Manual/Tutorials/Kubernetes/README.md
index 0201a14465..56f7e65543 100644
--- a/Documentation/Books/Manual/Tutorials/Kubernetes/README.md
+++ b/Documentation/Books/Manual/Tutorials/Kubernetes/README.md
@@ -52,15 +52,19 @@ For now, any recent Kubernetes cluster will do (e.g. `minikube`).
 Then run (replace `<version>` with the version of the operator that you want to install):
 
 ```bash
+kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/<version>/manifests/arango-crd.yaml
 kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/<version>/manifests/arango-deployment.yaml
-# Optional
+# To use `ArangoLocalStorage`, also run
 kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/<version>/manifests/arango-storage.yaml
+# To use `ArangoDeploymentReplication`, also run
+kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/<version>/manifests/arango-deployment-replication.yaml
 ```
 
 The first command installs two `CustomResourceDefinitions` in your Kubernetes cluster:
 
 - `ArangoDeployment` is the resource used to deploy ArangoDB database.
-- `ArangoLocalStorage` is the resource used to provision `PersistentVolumes` on local storage.
+- `ArangoDeploymentReplication` is the resource used to deploy ArangoDB DC2DC
+  replications.
 
 The second command installs a `Deployment` that runs the operator that controls
 `ArangoDeployment` resources.
@@ -68,7 +72,13 @@ The second command installs a `Deployment` that runs the operator that controls
 The optional third command installs a `Deployment` that runs the operator that
 provides `PersistentVolumes` on local disks of the cluster nodes.
 Use this when running on bare-metal or if there is no provisioner for fast
-storage in your Kubernetes cluster.
+storage in your Kubernetes cluster. Furthermore, this also installs a
+new custom resource definition:
+
+- `ArangoLocalStorage` is the resource used to provision `PersistentVolumes` on local storage.
+
+The optioal fourth command installs a `Deployment` that runs the
+operator that takes care of DC2DC replications.
 
 ## Deploying your first ArangoDB database