diff --git a/website/content/en/v0.22.0/concepts/_index.md b/website/content/en/v0.22.0/concepts/_index.md
index b1ac46f6c49f..74ec1368b573 100755
--- a/website/content/en/v0.22.0/concepts/_index.md
+++ b/website/content/en/v0.22.0/concepts/_index.md
@@ -90,13 +90,9 @@ Refer to the description of Karpenter constraints in the Application Developer s
 
 ### Scheduling
 
-Karpenter schedules pods that the Kubernetes scheduler has marked unschedulable.
-After solving scheduling constraints and launching capacity, Karpenter creates the Node object and waits for kube-scheduler to bind the pod.
-This stateless approach helps to avoid race conditions and improves performance.
-If something is wrong with the launched node, Kubernetes will automatically migrate the pods to a new node.
+Karpenter launches nodes in response to pods that the Kubernetes scheduler has marked unschedulable. After solving scheduling constraints and launching capacity, Karpenter launches a machine in your chosen cloud provider.
 
 Once Karpenter brings up a node, that node is available for the Kubernetes scheduler to schedule pods on it as well.
-This is useful if there is additional room in the node due to imperfect packing shape or because workloads finish over time.
 
 ### Cloud provider
 Karpenter makes requests to provision new nodes to the associated cloud provider.