diff --git a/2023/day23.md b/2023/day23.md
index 3c6d890a0..86704234e 100644
--- a/2023/day23.md
+++ b/2023/day23.md
@@ -2,8 +2,8 @@
 
 In the previous two days we learned why and how to scan container images.
 
-However, usually our infrastucture consists of more than just container images.
-Yes, our services wil run as containers, but around them we can also have other artifacts like:
+However, usually our infrastructure consists of more than just container images.
+Yes, our services will run as containers, but around them we can also have other artifacts like:
 
 - Kubernetes manifests
 - Helm templates
@@ -12,7 +12,7 @@ Yes, our services wil run as containers, but around them we can also have other
 For maximum security, you would be scanning all the artifacts that you use for your environment, not only your container images.
 
 The reason for that is that even if you have the most secure Docker images with no CVEs,
-but run then on an insecure infrastrucure with bad Kubernetes configuration,
+but run then on an insecure infrastructure with bad Kubernetes configuration,
 then your environment will not be secure.
 
 **Each system is as secure as its weakest link.**