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

Author: NickLarsenNZ

docs/modules/trino/pages/usage_guide/configuration.adoc

@@ -107,7 +107,7 @@ By default, in case nothing is configured in the custom resource for a certain r
 // The "nightly" version is needed because the "include" directive searches for
 // files in the "stable" version by default.
 // TODO: remove the "nightly" version after the next platform release (current: 22.09)
-include::home:concepts:stackable_resource_requests.adoc[]
+include::concepts:stackable_resource_requests.adoc[]
 
 If no resource requests are configured explicitly, the Trino operator uses the following defaults:
 

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

@@ -35,14 +35,14 @@ include::example$usage_guide/trino-file-auth-snippet.yaml[tag=trino]
 
 === 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=authclass]
 ----
 
-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 referincing the LDAP AuthenticationClass: