Merge pull request #643 from stackabletech/fix/release-24.3-remove-home-xref

fix: remove home component reference

Author: NickLarsenNZ

modules/concepts/pages/overview.adoc

@@ -47,7 +47,7 @@ Learn more about roles: xref:roles-and-role-groups.adoc[]
 [#deployment]
 == Deployment
 
-All operators and products run as containers in a xref:home::kubernetes.adoc[Kubernetes cluster]. The operators are deployed with stackablectl (the Stackable CLI) or Helm.
+All operators and products run as containers in a xref:kubernetes.adoc[Kubernetes cluster]. The operators are deployed with stackablectl (the Stackable CLI) or Helm.
 
 image::deployment.drawio.svg[]
 

modules/concepts/pages/stackable_resource_requests.adoc

@@ -1,7 +1,7 @@
 // This is meant to be inlined using the "include" directive in other pages.
 // WARNING: do not add headers here as they can break the structure of pages
 // that include this file.
-Stackable operators handle resource requests in a sligtly different manner than Kubernetes. Resource requests are defined on role or group level. See xref:home:concepts:roles-and-role-groups.adoc[] for details on these concepts. On a role level this means that e.g. all workers will use the same resource requests and limits. This can be further specified on role group level (which takes priority to the role level) to apply different resources.
+Stackable operators handle resource requests in a sligtly different manner than Kubernetes. Resource requests are defined on role or group level. See xref:concepts:roles-and-role-groups.adoc[] for details on these concepts. On a role level this means that e.g. all workers will use the same resource requests and limits. This can be further specified on role group level (which takes priority to the role level) to apply different resources.
 
 This is an example on how to specify CPU and memory resources using the Stackable https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/[Custom Resources]: