maybe fix link

Author: calebdoxsey

content/docs/reference/bearer-token-format.mdx

@@ -29,7 +29,7 @@ Authorization: Bearer Token
 
 Pomerium's `default` behavior is to pass bearer tokens to upstream applications without interpreting them. Pomerium also supports creating sessions from tokens issued by an identity provider without needing to initiate an interactive login. If the `idp_access_token` option is used, then the bearer token will be interpreted as an IdP-issued access token. If the `idp_identity_token` option is used, then the bearer token will be interpreted as an IdP-issued identity token.
 
-Currently only [Microsoft Entra](../../integrations/user-identity/azure) is supported with this option.
+Currently only [Microsoft Entra](../integrations/user-identity/azure) is supported with this option.
 
 This option can also be configured at the route-level.
 

content/docs/reference/idp-access-token-allowed-audiences.mdx

@@ -20,7 +20,7 @@ import TabItem from '@theme/TabItem';
 
 **IdP Access Token Allowed Audiences** controls how the audience claim of an incoming IdP-issued access token is validated.
 
-For [Microsoft Entra](../../integrations/user-identity/azure) an access-token is a JWT with an audience claim. When the IdP Access Token Allowed Audiences option is set, the `aud` claim of the access token JWT must match one of the entries.
+For [Microsoft Entra](../integrations/user-identity/azure) an access-token is a JWT with an audience claim. When the IdP Access Token Allowed Audiences option is set, the `aud` claim of the access token JWT must match one of the entries.
 
 This option can also be configured at the route-level.