diff --git a/content/karpenter/050_karpenter/consolidation.md b/content/karpenter/050_karpenter/consolidation.md
index 8202ef6f..4f0da21f 100644
--- a/content/karpenter/050_karpenter/consolidation.md
+++ b/content/karpenter/050_karpenter/consolidation.md
@@ -11,7 +11,7 @@ In the previous section we did set the default provisioner configured with a spe
 Automated deprovisioning is configured through the ProvisionerSpec `.ttlSecondsAfterEmpty`, `.ttlSecondsUntilExpired` and `.consolidation.enabled` fields. If these are not configured, Karpenter will not default values for them and will not terminate nodes.
 {{% /notice %}}
 
-There is another way to configure Karpenter to deprovision nodes called **Consolidation**. This mode is preferred for workloads such as microservices and is imcompatible with setting up the `ttlSecondsAfterEmpty` . When set in consolidation mode Karpenter works to actively reduce cluster cost by identifying when nodes can be removed as their workloads will run on other nodes in the cluster and when nodes can be replaced with cheaper variants due to a change in the workloads.
+There is another way to configure Karpenter to deprovision nodes called **Consolidation**. This mode is preferred for workloads such as microservices and is incompatible with setting up the `ttlSecondsAfterEmpty` . When set in consolidation mode Karpenter works to actively reduce cluster cost by identifying when nodes can be removed as their workloads will run on other nodes in the cluster and when nodes can be replaced with cheaper variants due to a change in the workloads.
 
 Before we proceed to see how Consolidation works, let's change the default provisioner configuration:
 ```
@@ -59,7 +59,7 @@ EOF
 ## Challenge
 
 {{% notice tip %}}
-You can use **Kube-ops-view** or just plain **kubectl** cli to visualize the changes and answer the questions below. In the answers we will provide the CLI commands that will help you check the resposnes. Remember: to get the url of **kube-ops-view** you can run the following command `kubectl get svc kube-ops-view | tail -n 1 | awk '{ print "Kube-ops-view URL = http://"$4 }'`.
+You can use **Kube-ops-view** or just plain **kubectl** cli to visualize the changes and answer the questions below. In the answers we will provide the CLI commands that will help you check the responses. Remember: to get the url of **kube-ops-view** you can run the following command `kubectl get svc kube-ops-view | tail -n 1 | awk '{ print "Kube-ops-view URL = http://"$4 }'`.
 Note the current version of Kube-ops-view sometimes takes time to reflect the correct state of the cluster.
 {{% /notice %}}
 
@@ -288,4 +288,4 @@ In this section we have learned:
 
 * **Delete** Consolidation does also include events where instances are moved from `on-demand` to `spot`, however karpenter does not trigger **Replace** to make Spot node smaller as this can have an impact on the level of interruptions.
 
-* Karpenter uses cordon and drain [best practices](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) to terminate nodes. to make it safer, Karpenter adds a finalizer so that a `kubernetes delete node` command, results in a graceful termination that remove the node safely from the cluster.
\ No newline at end of file
+* Karpenter uses cordon and drain [best practices](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) to terminate nodes. to make it safer, Karpenter adds a finalizer so that a `kubernetes delete node` command, results in a graceful termination that remove the node safely from the cluster.