diff --git a/content/en/blog/_posts/2021-05-30-update-with-ingress-nginx.md b/content/en/blog/_posts/2021-05-30-update-with-ingress-nginx.md
index c579e53c66..1b571182ed 100644
--- a/content/en/blog/_posts/2021-05-30-update-with-ingress-nginx.md
+++ b/content/en/blog/_posts/2021-05-30-update-with-ingress-nginx.md
@@ -11,8 +11,7 @@ With all Kubernetes APIs, there is a process to creating, maintaining, and
 ultimately deprecating them once they become GA. The network API is no
 different. With the release of Kubernetes 1.22, the network API goes from
 v1beta1 to v1, with v1beta is deprecated. This move has been in discussion
-for quite some time now in 2017 in
-[issue #43214](https://github.com/kubernetes/kubernetes/issues/43214),
+since [2017](https://github.com/kubernetes/kubernetes/issues/43214),
 [2019 with 1.16 api deprecation](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/)
 , and more recently in
 [KEP-1453:Graduate Ingress API to GA.](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1453-ingress-api#122)
@@ -56,4 +55,3 @@ Ingress-Nginx Sub-project regularly hold community meetings where we discuss
 this and other issues facing the project, meeting notes and details are
 [here](https://github.com/kubernetes/community/tree/master/sig-network)
 
-