[Bug fix] Clarify which registries support anonymous access (#37165)

content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md

@@ -190,9 +190,7 @@ Once you've selected the package you're interested in sharing with codespaces in
 {% endif %}
 ## Configuring visibility of packages for your personal account
 
-When you first publish a package that is scoped to your personal account, the default visibility is private and only you can see the package. You can modify a private or public  package's access by changing the access settings.
-
-A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+When you first publish a package that is scoped to your personal account, the default visibility is private and only you can see the package. You can modify a private or public  package's access by changing the access settings. Once you make your package public, you cannot make your package private again.
 
 {% data reusables.package_registry.package-settings-option %}
 1. At the bottom of the page, under "Danger Zone", click **Change visibility**.
@@ -220,9 +218,7 @@ For registries that support granular permissions, you can choose the visibility
 
 ## Configuring visibility of packages for an organization
 
-When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your package through the access settings.
-
-A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your package through the access settings. Once you make your package public, you cannot make your package private again.
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}

data/reusables/package_registry/visibility-and-access-permissions.md

@@ -1,6 +1,6 @@
-If a package belongs to a registry that supports granular permissions, anyone with admin permissions to the package can set the package to private or public. Public packages allow anonymous access and can be pulled without authentication or signing in via the CLI. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)."
+If a package belongs to a registry that supports granular permissions, anyone with admin permissions to the package can set the package to private or public, and can grant access permissions for the package that are separate from the permissions set at the organization and repository levels. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)."
 
-Anyone with admin permissions to the package can also grant access permissions for the package that are separate from the permissions set at the organization and repository levels.
+In most registries, to pull a package, you must authenticate with a {% data variables.product.pat_generic %} or `GITHUB_TOKEN`, regardless of whether the package is public or private. However, in the {% data variables.product.prodname_container_registry %}, public packages allow anonymous access and can be pulled without authentication or signing in via the CLI.
 
 {% ifversion packages-inherit-permissions %}
 {% note %}