diff --git a/modules/concepts/pages/resources.adoc b/modules/concepts/pages/resources.adoc
index 85b0b551b..c2633b665 100644
--- a/modules/concepts/pages/resources.adoc
+++ b/modules/concepts/pages/resources.adoc
@@ -71,7 +71,7 @@ It can not use more CPU resources than `500m` (which is half of a physical or vi
 
 === CPU and memory
 
-include::stackable_resource_requests.adoc[]
+include::partial$stackable_resource_requests.adoc[]
 
 === Storage
 
diff --git a/modules/concepts/pages/stackable_resource_requests.adoc b/modules/concepts/pages/stackable_resource_requests.adoc
index 016127ac0..b53033a3f 100644
--- a/modules/concepts/pages/stackable_resource_requests.adoc
+++ b/modules/concepts/pages/stackable_resource_requests.adoc
@@ -1,49 +1 @@
-// 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 slightly different manner than Kubernetes.
-Resource requests are defined on xref:concepts:stacklet.adoc#roles[role] or xref:concepts:stacklet.adoc#role-groups[role group] level.
-On a role level this means that by default, 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{external-link-icon}^]:
-
-[source, yaml]
-----
----
-apiVersion: example.stackable.tech/v1alpha1
-kind: ExampleCluster
-metadata:
-  name: example
-spec:
-  workers: # role-level
-    config:
-      resources:
-        cpu:
-          min: 300m
-          max: 600m
-        memory:
-          limit: 3Gi
-    roleGroups: # role-group-level
-      resources-from-role: # role-group 1
-        replicas: 1
-      resources-from-role-group: # role-group 2
-        replicas: 1
-        config:
-          resources:
-            cpu:
-              min: 400m
-              max: 800m
-            memory:
-              limit: 4Gi
-----
-
-In this case, the role group `resources-from-role` will inherit the resources specified on the role level, resulting in a maximum of `3Gi` memory and `600m` CPU resources.
-
-The role group `resources-from-role-group` has a maximum of `4Gi` memory and `800m` CPU resources (which overrides the role CPU resources).
-
-IMPORTANT: For Java products the actual used heap memory is lower than the specified memory limit due to other processes in the Container requiring memory to run as well.
-Currently, 80% of the specified memory limit is passed to the JVM.
-
-For memory, only a limit can be specified, which will be set as memory request and limit in the container.
-This is to always guarantee a container the full amount memory during Kubernetes scheduling.
+include::partial$stackable_resource_requests.adoc[]
diff --git a/modules/concepts/partials/stackable_resource_requests.adoc b/modules/concepts/partials/stackable_resource_requests.adoc
new file mode 100644
index 000000000..bb655e121
--- /dev/null
+++ b/modules/concepts/partials/stackable_resource_requests.adoc
@@ -0,0 +1,48 @@
+// 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 slightly different manner than Kubernetes.
+Resource requests are defined on xref:concepts:stacklet.adoc#roles[role] or xref:concepts:stacklet.adoc#role-groups[role group] level.
+On a role level this means that by default, 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{external-link-icon}^]:
+
+[source, yaml]
+----
+---
+apiVersion: example.stackable.tech/v1alpha1
+kind: ExampleCluster
+metadata:
+  name: example
+spec:
+  workers: # role-level
+    config:
+      resources:
+        cpu:
+          min: 300m
+          max: 600m
+        memory:
+          limit: 3Gi
+    roleGroups: # role-group-level
+      resources-from-role: # role-group 1
+        replicas: 1
+      resources-from-role-group: # role-group 2
+        replicas: 1
+        config:
+          resources:
+            cpu:
+              min: 400m
+              max: 800m
+            memory:
+              limit: 4Gi
+----
+
+In this case, the role group `resources-from-role` will inherit the resources specified on the role level, resulting in a maximum of `3Gi` memory and `600m` CPU resources.
+
+The role group `resources-from-role-group` has a maximum of `4Gi` memory and `800m` CPU resources (which overrides the role CPU resources).
+
+IMPORTANT: For Java products the actual used heap memory is lower than the specified memory limit due to other processes in the Container requiring memory to run as well.
+Currently, 80% of the specified memory limit is passed to the JVM.
+
+For memory, only a limit can be specified, which will be set as memory request and limit in the container.
+This is to always guarantee a container the full amount memory during Kubernetes scheduling.