fix link

Author: TylerMSFT

docs/code-quality/build-reliable-secure-programs.md

@@ -185,7 +185,7 @@ Remove the now-invalidated secrets from your source code, and replace them with
 AzDO users can scan their code through GitHub Advanced Security for Azure DevOps (GHAzDO). GHAzDO also allows users to prevent secret exposures by enabling Push Protection on their repositories, catching potential exposures before they're ever leaked. For more information on how to detect hardcoded secrets in code in Azure DevOps, see *Secret Scanning for Github Advanced Security for Azure DevOps* in each of the following links:
 
 - [GitHub advanced security for Azure DevOps](https://azure.microsoft.com/products/devops/github-advanced-security)
-- [Secret Scanning for GitHub Advanced Security for Azure DevOps](azure/devops/repos/security/github-advanced-security-secret-scanning)
+- [Secret Scanning for GitHub Advanced Security for Azure DevOps](/azure/devops/repos/security/github-advanced-security-secret-scanning)
 - [Microsoft Defender for DevOps Preview](https://www.microsoft.com/security/business/cloud-security/microsoft-defender-devops)
 
 **In GitHub**