From ca413bf30e7b464825fb0749bca6c16579b1f4f2 Mon Sep 17 00:00:00 2001
From: Tej Singh Rana <58101587+Tej-Singh-Rana@users.noreply.github.com>
Date: Fri, 29 Apr 2022 18:07:53 +0530
Subject: [PATCH] fixed the broken link

---
 .../index.md                                                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX/index.md b/content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX/index.md
index 25161b8c96..dff7428219 100644
--- a/content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX/index.md
+++ b/content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX/index.md
@@ -45,7 +45,7 @@ Linux containers (and underlying mechanisms such as kernel namespaces) work.
 You can read about cgroups in the Kubernetes glossary: [`cgroup`](https://kubernetes.io/docs/reference/glossary/?fundamental=true#term-cgroup) and learn more about cgroups interact with namespaces in the NGINX project article
 [What Are Namespaces and cgroups, and How Do They Work?](https://www.nginx.com/blog/what-are-namespaces-cgroups-how-do-they-work/).
 (As you read that, bear in mind that Linux kernel namespaces are a different thing from
-[Kubernetes namespaces](/docs/concepts/overview/working-with-objects/namespaces/)).
+[Kubernetes namespaces](/docs/concepts/overview/working-with-objects/namespaces/).
 
 ## Skip the talk, what do I need to use this new approach?