diff --git a/content/karpenter/050_karpenter/ec2_spot_deployments.md b/content/karpenter/050_karpenter/ec2_spot_deployments.md
index b2f52f0a..447db21c 100644
--- a/content/karpenter/050_karpenter/ec2_spot_deployments.md
+++ b/content/karpenter/050_karpenter/ec2_spot_deployments.md
@@ -21,7 +21,7 @@ Amazon EC2 terminates, your Spot Instance when Amazon EC2 needs the capacity bac
 
 Karpenter natively handles Spot Interruption Notifications (as of [v0.19.0](https://github.com/aws/karpenter/releases/tag/v0.19.0)) by consuming events from an SQS queue which is populated with Spot Interruption Notifications via EventBridge. All of the infrastructure is setup by Karpenter's CloudFormation template that was applied previously. When Karpenter receives a Spot Interruption Notification, it will gracefully drain the interrupted node of any running pods while also provisioning a new node for those pods to quickly schedule onto.
 
-Karepnter does not yet support Rebalance Recommendation signals, so to capture these signals and handle graceful termination of our nodes, we can  deploy a project called **[AWS Node Termination Handler](https://github.com/aws/aws-node-termination-handler)**. Node termination handler operates in two different modes Queue Mode and Instance Metadata Mode. When using Instance Metadata Mode, the aws-node-termination-handler will monitor the [Instance Metadata Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html) with a small pod running as a ([DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/)) on each host. The DaemonSet will perform monitoring of IMDS paths like /spot and /events and react accordingly to drain and/or cordon the corresponding node. 
+Karpenter does not yet support Rebalance Recommendation signals, so to capture these signals and handle graceful termination of our nodes, we can  deploy a project called **[AWS Node Termination Handler](https://github.com/aws/aws-node-termination-handler)**. Node termination handler operates in two different modes Queue Mode and Instance Metadata Mode. When using Instance Metadata Mode, the aws-node-termination-handler will monitor the [Instance Metadata Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html) with a small pod running as a ([DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/)) on each host. The DaemonSet will perform monitoring of IMDS paths like /spot and /events and react accordingly to drain and/or cordon the corresponding node. 
 
 We will not deploy the Node-Termination-Handler in this workshop since we are using Karpenter's native Spot Interruption handling. But the Node-Termination-Handler is required if you need to handle Rebalance Recommendation signals and can be run safely with Karpenter's Spot Interruption Handling.