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

Author: NickLarsenNZ

docs/modules/trino/pages/usage-guide/catalogs/generic.adoc

@@ -53,4 +53,4 @@ An entry must be an valid `SecretKeySelector` or `ConfigMapKeySelector`.
 
 == Add additional contents
 
-In case you need more contents, such as the need to mount Secrets - containing e.g. certificates or keytabs - please consult the xref:home:concepts:overrides.adoc#_pod_overrides[documentation on podOverrides].
+In case you need more contents, such as the need to mount Secrets - containing e.g. certificates or keytabs - please consult the xref:concepts:overrides.adoc#_pod_overrides[documentation on podOverrides].

docs/modules/trino/pages/usage-guide/configuration.adoc

@@ -130,7 +130,7 @@ By default, in case nothing is configured in the custom resource for a certain r
 
 === Resource Requests
 
-include::home:concepts:stackable_resource_requests.adoc[]
+include::concepts:stackable_resource_requests.adoc[]
 
 A minimal HA setup consisting of 1 coordinator and 2 worker instances has the following https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[resource requirements]:
 

docs/modules/trino/pages/usage-guide/log_aggregation.adoc

@@ -22,4 +22,4 @@ spec:
 Currently, the logs are collected only for `server.log`. Logging for `http-request.log` is disabled by default.
 
 Further information on how to configure logging, can be found in
-xref:home:concepts:logging.adoc[].
+xref:concepts:logging.adoc[].

docs/modules/trino/pages/usage-guide/monitoring.adoc

@@ -1,5 +1,5 @@
 = Monitoring
 
 The managed Trino instances are automatically configured to export Prometheus metrics. See
-xref:home:operators:monitoring.adoc[] for more details.
+xref:operators:monitoring.adoc[] for more details.
 

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

@@ -51,14 +51,14 @@ Adding or removing an `AuthenticationClass` will however result in a `Pod` resta
 
 ==== LDAP
 
-The Trino operator supports https://trino.io/docs/current/security/ldap.html[LDAP authentication] as well and authentication in Stackable is done using xref:home:concepts:authentication.adoc#authenticationclass[AuthenticationClasses]:
+The Trino operator supports https://trino.io/docs/current/security/ldap.html[LDAP authentication] as well and authentication in Stackable is done using xref:concepts:authentication.adoc#authenticationclass[AuthenticationClasses]:
 
 [source,yaml]
 ----
 include::example$usage-guide/trino-ldap-auth-snippet.yaml[tag=authentication_class]
 ----
 
-NOTE: You can follow the xref:home:tutorials:authentication_with_openldap.adoc[] tutorial to learn how to create an AuthenticationClass for an LDAP server.
+NOTE: You can follow the xref:tutorials:authentication_with_openldap.adoc[] tutorial to learn how to create an AuthenticationClass for an LDAP server.
 
 With an AuthenticationClass ready, `PASSWORD` authentication using LDAP is done by referencing the LDAP AuthenticationClass: