diff --git a/content/scalability/docs/control-plane.md b/content/scalability/docs/control-plane.md
index 9818ea60d..5c7d03c36 100644
--- a/content/scalability/docs/control-plane.md
+++ b/content/scalability/docs/control-plane.md
@@ -250,7 +250,7 @@ spec:
 - The matching precedence 8000 is lower than the value of 9000 used by the existing service-accounts FlowSchema so these list event calls will match list-events-default-service-accounts rather than service-accounts.
 - We're using the catch-all PriorityLevelConfiguration to isolate these requests. This bucket only allows 13 inflight requests to be used by these long-running list event calls. Pods will start to receive 429s as soon they try to issue more than 13 of these requests concurrently.
 
-## Retreiving resources in the API server
+## Retrieving resources in the API server
 
 Getting information from the API server is an expected behavior for clusters of any size. As you scale the number of resources in the cluster the frequency of requests and volume of data can quickly become a bottleneck for the control plane and will lead to API latency and slowness. Depending on the severity of the latency it cause unexpected downtime if you are not careful.