@@ -39,12 +39,12 @@ Tokens are always securely stored on your cluster and never in the Codefresh pla
3939###Scopes for Git tokens
4040{% if page.collection != site.gitops_collection %}
4141Create Git tokens with your Git provider, ensuring they have the required scopes.
42- See[ Git Runtime token scopes] ( {{site.baseurl}}// docs/security/git-tokens/#git-runtime-token-scopes ) and[ Git user token scopes] ( {{site.baseurl}}/ /docs/security/git-tokens/#git-user-access-token-scopes ) .
42+ See[ Git Runtime token scopes] ( {{site.baseurl}}/docs/security/git-tokens/#git-runtime-token-scopes ) and[ Git user token scopes] ( {{site.baseurl}}/docs/security/git-tokens/#git-user-access-token-scopes ) .
4343{% endif %}
4444
4545{% if page.collection == site.gitops_collection %}
4646Create personal access tokens in GitHub with the required scopes. GitHub supports Classic and Fine-Grained tokens.
47- See[ Git Runtime token scopes] ( {{site.baseurl}}// docs/security/git-tokens/#git-runtime-token-scopes ) and[ Git user token scopes] ( {{site.baseurl}}/ /docs/security/git-tokens/#git-user-access-token-scopes ) .
47+ See[ Git Runtime token scopes] ( {{site.baseurl}}/docs/security/git-tokens/#git-runtime-token-scopes ) and[ Git user token scopes] ( {{site.baseurl}}/docs/security/git-tokens/#git-user-access-token-scopes ) .
4848{% endif %}
4949
5050###Using the Git Runtime token as the Git user token