diff --git a/docs/modules/hdfs/pages/usage-guide/operations/pod_disruptions.adoc b/docs/modules/hdfs/pages/usage-guide/operations/pod_disruptions.adoc
index c485af54..11e71a90 100644
--- a/docs/modules/hdfs/pages/usage-guide/operations/pod_disruptions.adoc
+++ b/docs/modules/hdfs/pages/usage-guide/operations/pod_disruptions.adoc
@@ -3,7 +3,7 @@
 
 You can configure Pod disruptions for HDFS nodes as described in xref:concepts:operations/pod_disruptions.adoc[].
 
-Unless you configure something else or disable our PodDisruptionBudgets (PDBs), we write the following PodDisruptionBudgets:
+Unless you configure something else or disable our PodDisruptionBudgets (PDBs), we write the following PDBs:
 
 == Journalnodes
 We only allow a single journalnode to be offline at a given time, regardless of the number of replicas or roleGroups.
@@ -12,9 +12,8 @@ We only allow a single journalnode to be offline at a given time, regardless of
 We only allow a single namenode to be offline at a given time, regardless of the number of replicas or roleGroups.
 
 == Datanode
-For datanodes the questions how many instances can be offline at the same time is a bit harder.
-
-HDFS stores you in blocks on the datanodes.
+For datanodes the questions how many instances can be offline at the same time is a bit harder:
+HDFS stores your in blocks on the datanodes.
 Every block can be replicated multiple times (to multiple datanodes) to ensure maximum availability.
 The default setting is a replication of `3` - which can be configured using `spec.clusterConfig.dfsReplication`. However, it is also possible to change the replication factor for a specific file or directory to something else than the cluster default.