Package authentication documentation has confusing PAT wording

content/packages/learn-github-packages/publishing-a-package.md

@@ -26,8 +26,6 @@ If a new version of a package fixes a security vulnerability, you should publish
 
 ## Publishing a package
 
-{% data reusables.package_registry.packages-classic-pat-only %}
-
 You can publish a package to {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
 
 1. Create or use an existing {% data variables.product.pat_v1 %} with the appropriate scopes for the task you want to accomplish. For more information, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages)."

data/reusables/package_registry/authenticate-packages.md

@@ -1,9 +1,7 @@
-{% data reusables.package_registry.packages-classic-pat-only %}
-
 You need an access token to publish, install, and delete private, internal, and public packages.
 
 You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
 
 To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
 * `GITHUB_TOKEN` to publish packages associated with the workflow repository.
 * a {% data variables.product.pat_v1 %} with at least `read:packages` scope to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).