diff --git a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc
index a902b796..778a1f72 100644
--- a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc
+++ b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc
@@ -21,14 +21,17 @@ A license key for SUSE Observability server can be obtained via the SUSE Custome
 
 === Requirements
 
-To install SUSE Observability, ensure that the nodes have enough CPU and memory capacity. Below are the specific requirements.
+To install SUSE Observability, ensure that the cluster has enough CPU and memory capacity. Below are the specific requirements.
 
-There are different installation options available for SUSE Observability. It is possible to install SUSE Observability either in a High-Availability (HA) or single instance (non-HA) setup. The non-HA setup is recommended for testing purposes or small environments. For production environments, it is recommended to install SUSE Observability in a HA setup.
+There are different installation options available for {stackstate-product-name}. It is possible to install {stackstate-product-name} either in a High-Availability (HA) or single instance (non-HA) setup. The non-HA setup is recommended for testing purposes or small environments. For production environments, it is recommended to install {stackstate-product-name} in a HA setup.
 
 The HA production setup can support from 150 up to 4000 observed nodes. An observed node in this sizing table is taken to be 4 vCPUs and 16GB of memory, our `default node size`.
 If nodes in your observed cluster are bigger, they can count for multiple `default nodes`, so a node of 12vCPU and 48GB counts as 3 `default nodes` under observation when picking
 a profile.
-The Non-HA setup can support up to 100 Nodes under observation.
+The Non-HA setup can support up to 100 `default nodes` under observation.
+
+
+The following table describes the resources required to deploy the {stackstate-product-name} server in a cluster, given the amount of `default nodes` that will be observed and whether the installation should be HA or not.
 
 |===
 |  | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA
@@ -93,12 +96,12 @@ NOTE: An additional 20% of resources is required for pod (unequal) distribution,
 
 [NOTE]
 ====
-The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server.
+The requirement shown for profile represent the total amount of resources needed to run the {stackstate-product-name} server.
 To ensure that all different services of Suse Observability server can be allocated:
 
-* For non-HA installations the recommended node size is 4VCPU, 8GB
-* For HA installations up to 500 nodes the min recommended node size is 8VCPU, 16GB
-* For 4000 nodes HA installations the min recommended node size is 16VCPU, 32GB
+* For non-HA installations the minimum per-node size is 4VCPU, 8GB
+* For HA installations up to 500 nodes the minimum per-node size is 8VCPU, 16GB
+* For 4000 nodes HA installations the minimum per-node size is 16VCPU, 32GB
 ====