Updated A Round Of Applause Semantic Release For The Clapper Component

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

@@ -45,7 +45,7 @@ It's worth going into a little more detail on each of these steps.
 
 <img src="/uploads/infinity-steps.jpg" alt="Impossible staircase" title="Continuous deployment anyone?" style="display: block; margin: 1rem auto; max-height: 12rem;" />
 
-### 🛡️ Verify Conditions
+### ✅ Verify Conditions
 
 [GitHub plugin][github-plugin] checks for and validates GITHUB_TOKEN, which must be injected into the environment when running the release. This is straightforward in a GitHub workflow. GitHub creates this token as a secret on your behalf, so you only need to reference it.
 
@@ -75,7 +75,7 @@ However, we do need our package in npm to have the correct version number, there
 
 Additionally, we have an npm script (`prepack`) which runs the build before preparing the npm package, to generate  production-ready JavaScript and CSS files. Therefore, the npm tarball also contains a dist folder with these assets, which the GitHub source bundles do not have.
 
-### <img src="/uploads/npm.svg" alt="npm logo" /> Publish
+### <img src="/uploads/npm.svg" alt="npm logo" style="display:inline; width:1.5rem; vertical-align:sub;" /> Publish
 
 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).