Update content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: Sharra-writes

content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md

@@ -274,7 +274,7 @@ This feature enables unified dependency management for both public and private G
 
 **Private Proxy Serving All Modules**: All module requests go through your proxy first. For public modules fetching failures, your proxy returns 404/410 and Go falls back to direct version control system(VCS) access, but for private modules for example published to only a private repository like JFrog Artifactory. The VCS fall back will not work since they are only accessible through the proxy.
 
-**Private Proxy Serving Private Modules**: add a go.env to your repository root, and set up a GONOSUMDB matching the private modules pattern(eg. `GONOSUMDB=my-company.com/*`. For all private modules starting with my-company.com/). This will disable the public checksum validation of your private modules. Because the public checksum does not have your private modules. 
+**Private Proxy Serving Private Modules**: add a go.env to your repository root, and set up a GONOSUMDB matching the private modules pattern (e.g., `GONOSUMDB=my-company.com/*` for all private modules starting with my-company.com/). This will disable the public checksum validation of your private modules because the public checksum database does not have your private modules.
 
 **Direct Access to Private Modules**: Set `GOPRIVATE=my-company.com/*` to bypass proxies and fetch directly from VCS. This only works if private modules are properly published with semantic version tags in your source control.