From 538857e41411dde53d51b619fea5e02a0b73d7c1 Mon Sep 17 00:00:00 2001
From: Edith Puclla <58795858+edithturn@users.noreply.github.com>
Date: Tue, 13 Aug 2024 17:18:05 +0100
Subject: [PATCH] Update 2024-08-13-Kubernetes-v1-31-Release.md

Replacing AppApArmor with "AppArmor"
---
 content/en/blog/_posts/2024-08-13-Kubernetes-v1-31-Release.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2024-08-13-Kubernetes-v1-31-Release.md b/content/en/blog/_posts/2024-08-13-Kubernetes-v1-31-Release.md
index 8d42487232..2a66b9b10e 100644
--- a/content/en/blog/_posts/2024-08-13-Kubernetes-v1-31-Release.md
+++ b/content/en/blog/_posts/2024-08-13-Kubernetes-v1-31-Release.md
@@ -38,7 +38,7 @@ Kubernetes v1.31's Elli is all about celebrating this wonderful spirit! Here's t
 
 _This is a selection of some of the improvements that are now stable following the v1.31 release._
 
-### AppAprmor support is now stable
+### AppArmor support is now stable
 
 Kubernetes support for AppArmor is now GA. Protect your containers using AppArmor by setting the `appArmorProfile.type` field in the container's `securityContext`. 
 Note that before Kubernetes v1.30, AppArmor was controlled via annotations; starting in v1.30 it is controlled using fields.