docs: remove home module from refs (stackabletech/documentation#637)

Author: NickLarsenNZ

docs/modules/zookeeper/pages/usage_guide/authentication.adoc

@@ -1,7 +1,7 @@
 = Authentication
 
 The communication between nodes (server to server) is encrypted via TLS by default.
-In order to enforce TLS authentication for client-to-server communication, you can set an xref:home:concepts:authentication.adoc[AuthenticationClass] reference in the `spec.clusterConfig.authentication` property.
+In order to enforce TLS authentication for client-to-server communication, you can set an xref:concepts:authentication.adoc[AuthenticationClass] reference in the `spec.clusterConfig.authentication` property.
 
 Currently it is possible to configure a single form of authentication (of type TLS) by adding one (and only one) entry
 in the `authentication` sequence as shown in the example below. Additional authentication methods, such as Kerberos, are
@@ -28,5 +28,5 @@ and unauthenticated access to the ZooKeeper cluster is still possible.
 
 == Learn more
 
-* Read the xref:home:concepts:authentication.adoc[authentication concept] of the Stackable Data Platform.
-* Read the {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/[AuthenticationClass reference {external-link-icon}^].
+* Read the xref:concepts:authentication.adoc[authentication concept] of the Stackable Data Platform.
+* Read the {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/[AuthenticationClass reference {external-link-icon}^].

docs/modules/zookeeper/pages/usage_guide/log_aggregation.adoc

@@ -27,4 +27,4 @@ spec:
 ----
 
 Further information on how to configure logging, can be found in
-xref:home:concepts:logging.adoc[].
+xref:concepts:logging.adoc[].

docs/modules/zookeeper/pages/usage_guide/resource_configuration.adoc

@@ -22,7 +22,7 @@ You can also configure which StorageClass to use, consult the xref:concepts:reso
 
 == Resource requests
 
-include::home:concepts:stackable_resource_requests.adoc[]
+include::concepts:stackable_resource_requests.adoc[]
 
 A minimal HA setup consisting of 3 ZooKeeper instances has the following https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[resource requirements]:
 

docs/modules/zookeeper/pages/usage_guide/using_multiple_role_groups.adoc

@@ -1,7 +1,7 @@
 = Using multiple role groups
 
 // abstract/summary
-ZooKeeper uses a unique ID called _myid_ to identify each server in the cluster. The Stackable Operator for Apache ZooKeeper assigns the _myid_ to each Pod from the https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#ordinal-index[ordinal index] given to the Pod by Kubernetes. This index is unique over the Pods in the StatefulSet of the xref:home:concepts:roles-and-role-groups.adoc[role group].
+ZooKeeper uses a unique ID called _myid_ to identify each server in the cluster. The Stackable Operator for Apache ZooKeeper assigns the _myid_ to each Pod from the https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#ordinal-index[ordinal index] given to the Pod by Kubernetes. This index is unique over the Pods in the StatefulSet of the xref:concepts:roles-and-role-groups.adoc[role group].
 
 When using multiple role groups in a cluster, this will lead to different ZooKeeper Pods using the same _myid_. Each role group is represented by its own StatefulSet, and therefore always identified starting with `0`.
 
@@ -29,4 +29,4 @@ spec:
 
 <1> The `myidOffset` property set to 10 for the secondary role group
 
-The `secondary` role group _myid_ starts from id `10`. The `primary` role group will start from `0`. This means, the replicas of the role group `primary` should not be scaled higher than `10` which results in `10` `primary` Pods using a _myid_ from `0` to `9`, followed by the `secondary` Pods starting at _myid_ `10`. 
+The `secondary` role group _myid_ starts from id `10`. The `primary` role group will start from `0`. This means, the replicas of the role group `primary` should not be scaled higher than `10` which results in `10` `primary` Pods using a _myid_ from `0` to `9`, followed by the `secondary` Pods starting at _myid_ `10`.