From 6a5fc75ff50dbcc5f9cff41724e17e1708262238 Mon Sep 17 00:00:00 2001
From: Loann Le <84412881+taoism4504@users.noreply.github.com>
Date: Wed, 10 Nov 2021 09:38:02 -0800
Subject: [PATCH] fixed link error (#13103)

---
 website/content/docs/internals/security.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/internals/security.mdx b/website/content/docs/internals/security.mdx
index 8b46de813..2785337ab 100644
--- a/website/content/docs/internals/security.mdx
+++ b/website/content/docs/internals/security.mdx
@@ -109,7 +109,7 @@ This client token is then returned to the client.
 
 On each request a client provides this token. Vault then uses it to check that
 the token is valid and has not been revoked or expired, and generates an ACL
-based on the associated policies. Vault uses a strict default deny 
+based on the associated policies. Vault uses a strict default deny
 enforcement strategy. This means unless an associated policy allows for a given action,
 it will be denied. Each policy specifies a level of access granted to a path in
 Vault. When the policies are merged (if multiple policies are associated with a
@@ -118,7 +118,7 @@ client), the highest access level permitted is used. For example, if the
 "ops" policy permits read access to the "ops/" path, then the user gets the
 union of those. Policy is matched using the most specific defined policy, which
 may be an exact match or the longest-prefix match glob pattern. See
-[Policy Syntax](../concepts/policies#policy-syntax) for more details.
+[Policy Syntax](/docs/concepts/policies#policy-syntax) for more details.
 
 Certain operations are only permitted by "root" users, which is a distinguished
 policy built into Vault. This is similar to the concept of a root user on a