Updated A Round Of Applause Semantic Release For The Clapper Component

_drafts/a-round-of-applause-semantic-release-for-the-clapper-component.markdown

@@ -81,7 +81,7 @@ Generates a tarball of the npm package.
 
 Generates zip and tarball of source code for the GitHub release.
 
-#### Notes
+#### A note on bundling
 
 There are important differences between the bundles generated by these two plugins.
 
@@ -93,11 +93,11 @@ Secondly, we have an npm script (`prepack`) which runs the build before preparin
 
 ### Publish
 
-#### [GitHub plugin][github-plugin]
+#### [npm plugin][npm-plugin]
 
 Here's another thing to love about semantic-release: contributors have provided a set of [recipes for common release tasks](https://semantic-release.gitbook.io/semantic-release/recipes/ci-configurations), including a recipe for [releasing to npm via GitHub Actions](https://semantic-release.gitbook.io/semantic-release/recipes/ci-configurations/github-actions#node-project-configuration).
 
-I also wanted to try out releasing with [npm provenance](https://github.blog/security/supply-chain-security/introducing-npm-package-provenance/), a relatively new concept which is gaining traction: packages can gain a provenance badge by providing a verifiable link back to the source code _and_ to the build configuration, to give consumers full knowledge of how your package was built from sources. GitHub Actions are one of the current verifiable build systems, which is another good reason to use them instead of Travis.
+I also wanted to try out releasing with [npm provenance](https://github.blog/security/supply-chain-security/introducing-npm-package-provenance/), a relatively new concept which is gaining traction: packages can gain a provenance badge by providing a verifiable link back to the source code _and_ to the build configuration, to give consumers full knowledge of how a package was built from sources. GitHub Actions are one of the current verifiable build systems, which is another good reason to use them instead of Travis.
 
 The workflow is simple to set up following the recipe linked above; the only extra config needed for provenance is this section inside `package.json`: