From e23de90f19cfb8c9951ae42c66a3acb96faa28af Mon Sep 17 00:00:00 2001
From: Bob Killen <bobkillen@google.com>
Date: Thu, 3 Dec 2020 07:57:25 -0500
Subject: [PATCH] Correct dockershim release removal target

---
 .../blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md b/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md
index a262ef64c9..4a69653ba0 100644
--- a/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md
+++ b/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md
@@ -34,7 +34,7 @@ testing and planning.
 If you’re rolling your own clusters, you will also need to make changes to avoid
 your clusters breaking. At v1.20, you will get a deprecation warning for Docker.
 When Docker runtime support is removed in a future release (currently planned
-for the 1.23 release in late 2021) of Kubernetes it will no longer be supported
+for the 1.22 release in late 2021) of Kubernetes it will no longer be supported
 and you will need to switch to one of the other compliant container runtimes,
 like containerd or CRI-O. Just make sure that the runtime you choose supports
 the docker daemon configurations you currently use (e.g. logging).