some more wording and formatting

Author: Felix Hennig

docs/modules/hdfs/pages/usage-guide/configuration-environment-overrides.adoc

@@ -53,7 +53,7 @@ nameNodes:
 All override property values must be strings.
 The properties are formatted and escaped correctly into the XML file.
 
-For a full list of configuration options we refer to the Apache Hdfs documentation for https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/hdfs-default.xml[hdfs-site.xml] and https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/core-default.xml[core-site.xml].
+For a full list of configuration options refer to the Apache Hdfs documentation for https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/hdfs-default.xml[hdfs-site.xml] and https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/core-default.xml[core-site.xml].
 
 === The security.properties file
 

docs/modules/hdfs/pages/usage-guide/operations/pod-disruptions.adoc

@@ -3,7 +3,7 @@
 
 You can configure the permitted Pod disruptions for HDFS nodes as described in xref:concepts:operations/pod_disruptions.adoc[].
 
-Unless you configure something else or disable our PodDisruptionBudgets (PDBs), the operator write the following PDBs:
+Unless you configure something else or disable the default PodDisruptionBudgets (PDBs), the operator writes the following PDBs:
 
 == JournalNodes
 Only a single JournalNode is allowed to be offline at any given time, regardless of the number of replicas or `roleGroups`.
@@ -20,7 +20,7 @@ The default replication factor is `3` - which can be configured using `spec.clus
 When you have a replication of `3`, you can safely take down 2 DataNodes, as there is always a third DataNode holding a copy of each block currently assigned to one of the unavailable DataNodes.
 However, you need to be aware that you are now down to a single point of failure -- the last of three replicas!
 
-Taking this into consideration, our operator uses the following algorithm to determine the maximum number of DataNodes allowed to be unavailable at the same time:
+Taking this into consideration, the operator uses the following algorithm to determine the maximum number of DataNodes allowed to be unavailable at the same time:
 
 `num_datanodes` is the number of DataNodes in the HDFS cluster, summed over all `roleGroups`.
 

docs/modules/hdfs/pages/usage-guide/security.adoc

@@ -56,7 +56,7 @@ There is an https://github.com/stackabletech/hdfs-operator/blob/main/tests/templ
 
 == Authorization
 For authorization we developed https://github.com/stackabletech/hdfs-utils[hdfs-utils], which contains an OPA authorizer and group mapper.
-This matches our general xref:concepts:opa.adoc[] mechanisms.
+This matches the general xref:concepts:opa.adoc[] mechanisms.
 
 IMPORTANT: It is recommended to enable Kerberos when doing Authorization, as otherwise you don't have any security measures at all.
 There still might be cases where you want authorization on top of a cluster without authentication, as you don't want to accidentally drop files and therefore use different users for different use-cases.