Update content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md

Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com>

Author: asciimike

content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md

@@ -40,6 +40,6 @@ Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %
 
 If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
 
-If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's *Dependabot secrets*.
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](https://docs.github.com/en/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
 
 If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues) repository.