fix paths for linking

Author: AdiSai

fern/customization/custom-transcriber.mdx

@@ -439,7 +439,7 @@ You'll learn how to:
 - **Streaming support requirement:**  
   The custom transcriber must support streaming. Vapi sends continuous audio data over the WebSocket, and your server must handle this stream in real time.
 - **Authentication:**  
-  For secure transcriber endpoints, use **Custom Credentials** with `credentialId`. Create [Custom Credentials](../server-url/server-authentication) in the dashboard to manage Bearer Token, OAuth 2.0, or HMAC authentication. For backward compatibility, the legacy `secret` field is still supported and sends the value as an `x-vapi-secret` HTTP header.
+  For secure transcriber endpoints, use **Custom Credentials** with `credentialId`. Create [Custom Credentials](../../server-url/server-authentication) in the dashboard to manage Bearer Token, OAuth 2.0, or HMAC authentication. For backward compatibility, the legacy `secret` field is still supported and sends the value as an `x-vapi-secret` HTTP header.
 - **Buffering:**  
   The solution buffers PCM audio and performs simple validation (e.g. ensuring stereo PCM data length is a multiple of 4). If the audio data is malformed, it is trimmed to a valid length.
 - **Channel detection:**  

fern/customization/custom-tts.mdx

@@ -75,7 +75,7 @@ Create authentication credentials in the dashboard and reference them by ID:
 </CodeBlocks>
 
 <Note>
-Create [Custom Credentials](../server-url/server-authentication) in the Vapi dashboard for better security and credential management.
+Create [Custom Credentials](../../server-url/server-authentication) in the Vapi dashboard for better security and credential management.
 </Note>
 
 ### Legacy Authentication Methods