diff --git a/docs/getting-started/email-auth.md b/docs/getting-started/email-auth.md
index 5518895..2d55180 100644
--- a/docs/getting-started/email-auth.md
+++ b/docs/getting-started/email-auth.md
@@ -10,7 +10,7 @@ Email Auth enables a user to authenticate their Turnkey account via email. In th
 
 #### Mechanism
 
-In short, Email Auth is built with expiring API keys as the foundation: email is simply the mechanism through which the API key credential is safely delivered. Once the credential is live on the client side (within the context of an iframe), it is readily available to stamp (authenticate) requests. See the [cryptographic details](#cryptographic-details) section for more info on how we achieve secure delivery.
+In short, Email Auth is built with expiring API keys as the foundation: email is simply the mechanism through which the API key credential is safely delivered. Once the credential is live on the client side (within the context of an iframe), it is readily available to stamp (authenticate) requests. See the [cryptographic details](#mechanism-and-cryptographic-details) section for more info on how we achieve secure delivery.
 
 ## User Experience
 
diff --git a/docs/user-management/credentials.md b/docs/user-management/credentials.md
index 0d6feac..c573353 100644
--- a/docs/user-management/credentials.md
+++ b/docs/user-management/credentials.md
@@ -25,4 +25,4 @@ Turnkey API requests are authenticated with API key signatures. When you generat
 
 Requests made via SDK or CLI use the private API key to sign requests. Turnkey's public API expects all requests (e.g. to get data or to submit activities) to be signed.
 
-See our [API reference](./api#tag/API-Keys/operation/CreateApiKeys) for how to programmatically create API keys.
+See our [API reference](../../api/#tag/API-Keys/operation/CreateApiKeys) for how to programmatically create API keys.