Add colons in about-github-packages-and-github-actions#workflows-for-…

…publishing-packages | issue/35774 (#35791)

Co-authored-by: Alex Nguyen <[email protected]>

data/reusables/package_registry/about-packaging-and-actions.md

@@ -16,12 +16,12 @@ This will let you run the code in the pull request on your machine, which can he
 
 In addition to uploading packaging artifacts for testing in a continuous integration workflow, you can create workflows that build your project and publish packages to a package registry.
 
-* **Publish packages to {% data variables.product.prodname_registry %}**
+* **Publish packages to {% data variables.product.prodname_registry %}:**
   {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. You can choose to share your packages with all of {% data variables.product.prodname_dotcom %}, or private packages to share with collaborators or an organization. For more information, see "[AUTOTITLE](/packages/learn-github-packages/introduction-to-github-packages)."
 
   You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.
 
-* **Publish packages to a package registry**
+* **Publish packages to a package registry:**
   For many projects, publishing to a package registry is performed whenever a new version of a project is released. For example, a project that produces a JAR file may upload new releases to the Maven Central repository. Or, a .NET project may produce a nuget package and upload it to the NuGet Gallery.
 
   You can automate this by creating a workflow that publishes packages to a package registry on every release creation. For more information, see "[AUTOTITLE](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."