diff --git a/modules/openshift-cluster-limits.adoc b/modules/openshift-cluster-limits.adoc
index 6e895a3f8f..0a19ff3d24 100644
--- a/modules/openshift-cluster-limits.adoc
+++ b/modules/openshift-cluster-limits.adoc
@@ -7,7 +7,7 @@
 
 [options="header",cols="5*"]
 |===
-| Limit type |3.9 limit |3.10 limit |3.11 limit |4.1 limit
+| Limit type |3.10 limit |3.11 limit |4.1 limit |4.2 Limit
 
 | Number of nodes footnoteref:[numberofnodes,Clusters with more than the stated limit are not supported. Consider splitting into multiple clusters.]
 | 2,000
@@ -16,7 +16,7 @@
 | 2,000
 
 | Number of pods footnoteref:[numberofpods,The pod count displayed here is the number of test pods. The actual number of pods depends on the application’s memory, CPU, and storage requirements.]
-| 120,000
+| 150,000
 | 150,000
 | 150,000
 | 150,000
@@ -28,7 +28,7 @@
 | 250
 
 | Number of pods per core
-| 10 is the default value. The maximum supported value is the number of pods per node.
+| There is no default value. The maximum supported value is the number of pods per node..
 | There is no default value. The maximum supported value is the number of pods per node.
 | There is no default value. The maximum supported value is the number of pods per node.
 | There is no default value. The maximum supported value is the number of pods per node.
@@ -49,10 +49,10 @@
 a number of control loops in the system that must iterate over all objects
 in a given namespace as a reaction to some changes in state. Having a large
 number of objects of a given type in a single namespace can make those loops
-expensive and slow down processing given state changes. The limit assumes that 
+expensive and slow down processing given state changes. The limit assumes that
 the system has enough CPU, memory, and disk to satisfy the application requirements.]
 | 3,000
-| 3,000
+| 25,000
 | 25,000
 | 25,000
 
@@ -63,7 +63,7 @@ the system has enough CPU, memory, and disk to satisfy the application requireme
 | 10,000
 
 | Number of services per namespace
-| N/A
+| 5,000
 | 5,000
 | 5,000
 | 5,000
@@ -82,8 +82,5 @@ the system has enough CPU, memory, and disk to satisfy the application requireme
 
 |===
 
-In {product-title} {product-version}, half of a CPU core (500 millicore) is now reserved by
-the system compared to {product-title} 3.11 and previous versions.
-
-In {product-title} 4.1, the tested node limit has been lowered until scale tests can be run at
-a higher node count.
+In {product-title} {product-version}, half of a CPU core (500 millicore) is
+reserved by the system compared to {product-title} 3.11 and previous versions.