From 3097a5a618695a401f95782a7d8dca182e9cd373 Mon Sep 17 00:00:00 2001
From: Julien Dessaux
Date: Sun, 23 Jan 2022 21:45:31 +0100
Subject: typo

---
 content/blog/kubernetes/k3s-ipv6-outgoing-nat.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'content/blog')

diff --git a/content/blog/kubernetes/k3s-ipv6-outgoing-nat.md b/content/blog/kubernetes/k3s-ipv6-outgoing-nat.md
index 1ab40c5..231c5f6 100644
--- a/content/blog/kubernetes/k3s-ipv6-outgoing-nat.md
+++ b/content/blog/kubernetes/k3s-ipv6-outgoing-nat.md
@@ -11,7 +11,7 @@ tags:
 
 If you followed my [Making dual stack ipv6 work with k3s]({{< ref k3s-ipv6.md >}}) article a few months ago, you ended up with a setup where outgoing ipv6 traffic does not work. I only needed to have my pods reachable from the internet and did not try to generate ipv6 traffic originating from the cluster so never encountered the problem.
 
-One of my kind readers did and reached out to me about the issue : thank your Mo!
+One of my kind readers did and reached out to me about the issue : thank you Mo!
 
 ## The problem
 
-- 
cgit v1.2.3