diff --git a/keps/753-descheduling-framework/README.md b/keps/753-descheduling-framework/README.md
index 2dde2ad148..85794f7a9b 100644
--- a/keps/753-descheduling-framework/README.md
+++ b/keps/753-descheduling-framework/README.md
@@ -487,7 +487,7 @@ Plugins are expected to be executed in the same order as they are specified acro
 
 ### Descheduling workflow
 
-The following diagram depicts the descheduling cycle workflow. In each descheduling cycle a list of nodes is passed to each Deschedule and Balance pod. Both extension points are expected to list all pods on each node before further processing. First, all Deschedule extension points from all profiles are executed. Followed by all Balance extension points. The framework can be configured to keep a track of pods evicted per node/namespaces per each descheduling cycle. When a limit on the number of evicted pods is configured and exceeded, the descheduling cycle is prematurely finished. So it’s recommended to put the profiles in a way that the most preferable pods are evicted first.
+The following diagram depicts the descheduling cycle workflow. In each descheduling cycle a list of nodes is passed to each Deschedule and Balance plugin. Both extension points are expected to list all pods on each node before further processing. First, all Deschedule extension points from all profiles are executed. Followed by all Balance extension points. The framework can be configured to keep a track of pods evicted per node/namespaces per each descheduling cycle. When a limit on the number of evicted pods is configured and exceeded, the descheduling cycle is prematurely finished. So it’s recommended to put the profiles in a way that the most preferable pods are evicted first.
 
 ![Descheduling framework workflow diagram](framework-workflow-diagram.png)