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

Author: lfrancke

docs/modules/nifi/pages/usage_guide/custom_processors.adoc

@@ -22,7 +22,7 @@ FROM docker.stackable.tech/stackable/nifi:1.25.0-stackable0.0.0-dev
 COPY /path/to/your/nar.file /stackable/nifi/lib/
 ----
 
-You then need to make this image available to your Kubernetes cluster and specify it in your NiFi resource as described in xref:home:concepts:product_image_selection.adoc[].
+You then need to make this image available to your Kubernetes cluster and specify it in your NiFi resource as described in xref:concepts:product_image_selection.adoc[].
 
 [source,yaml]
 ----
@@ -120,4 +120,4 @@ spec:
 ----
 
 <1> Specify your prepared PVC here.
-<2> The directory name after `userdata` has to match the name of the volume, while `mycustomlibs` is a name you can freely change.
+<2> The directory name after `userdata` has to match the name of the volume, while `mycustomlibs` is a name you can freely change.

docs/modules/nifi/pages/usage_guide/log-aggregation.adoc

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

docs/modules/nifi/pages/usage_guide/monitoring.adoc

@@ -5,4 +5,4 @@ This is done by creating a https://kubernetes.io/docs/concepts/workloads/control
 
 IMPORTANT: Network access from the Job to NiFi is required. If you are running a Kubernetes with restrictive https://kubernetes.io/docs/concepts/services-networking/network-policies/[NetworkPolicies], make sure to allow access from the Job to NiFi.
 
-See xref:home:operators:monitoring.adoc[] for more details.
+See xref:operators:monitoring.adoc[] for more details.

docs/modules/nifi/pages/usage_guide/resource-configuration.adoc

@@ -32,7 +32,7 @@ In the above example, all nodes in the default group will request `12Gi` of stor
 
 == Resource Requests
 
-include::home:concepts:stackable_resource_requests.adoc[]
+include::concepts:stackable_resource_requests.adoc[]
 
 A minimal HA setup consisting of 2 NiFi instances has the following https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[resource requirements]:
 
@@ -41,4 +41,4 @@ A minimal HA setup consisting of 2 NiFi instances has the following https://kube
 * `8448Mi` memory request and limit
 * `18432Mi` persistent storage
 
-You can find the default resource configuration values in the {crd-docs}/nifi.stackable.tech/NifiCluster/v1alpha1/#spec-nodes-config-resources[NifiCluster reference docs {external-link-icon}^].
+You can find the default resource configuration values in the {crd-docs}/nifi.stackable.tech/NifiCluster/v1alpha1/#spec-nodes-config-resources[NifiCluster reference docs {external-link-icon}^].

docs/modules/nifi/pages/usage_guide/security.adoc

@@ -55,7 +55,7 @@ spec:
 [#authentication-ldap]
 === LDAP
 
-NiFi supports xref:home:concepts:authentication.adoc[authentication] of users against an LDAP server. This requires setting up an AuthenticationClass for the LDAP server.
+NiFi supports xref:concepts:authentication.adoc[authentication] of users against an LDAP server. This requires setting up an AuthenticationClass for the LDAP server.
 The AuthenticationClass is then referenced in the NifiCluster resource as follows:
 
 [source,yaml]
@@ -72,7 +72,7 @@ spec:
 
 <1> The reference to an AuthenticationClass called `ldap`
 
-You can follow the xref:home:tutorials:authentication_with_openldap.adoc[] tutorial to learn how to set up an AuthenticationClass for an LDAP server, as well as consulting the {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/[AuthenticationClass reference {external-link-icon}^].
+You can follow the xref:tutorials:authentication_with_openldap.adoc[] tutorial to learn how to set up an AuthenticationClass for an LDAP server, as well as consulting the {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/[AuthenticationClass reference {external-link-icon}^].
 
 [#authorization]
 == Authorization