Merge pull request #3203 from adamdmharvey/doc-updates-2nov

chore(docs): Minor documentation updates

docs/api/utility-apis.md

@@ -22,7 +22,7 @@ during their entire life cycle.
 
 Each Utility API is tied to an `ApiRef` instance, which is a global singleton
 object without any additional state or functionality, its only purpose is to
-reference Utility APIs. `ApiRef`s are create using `createApiRef`, which is
+reference Utility APIs. `ApiRef`s are created using `createApiRef`, which is
 exported by `@backstage/core`. There are many
 [predefined Utility APIs](../reference/utility-apis/README.md) defined in
 `@backstage/core`, and they're all exported with a name of the pattern

docs/dls/design.md

@@ -99,9 +99,10 @@ issues in GitHub with ‘design’ and/or ‘storybook’ - so feel free to brow
 tackle the tasks that interest you. If you have any questions regarding an
 issue, you can ask them in the comments section of the issue or on
 [Discord](https://discord.gg/EBHEGzX). We absolutely adore our external
-contributors and will send you virtual semlas for your contributions!
+contributors and will send you virtual
+[semlas](https://en.wikipedia.org/wiki/Semla) for your contributions!
 
-### Request a component.
+### Request a component
 
 Create an issue (label it design and assign it to katz95) or send us a message
 on [Discord](https://discord.gg/EBHEGzX) (_#design_ channel) with details of
@@ -135,5 +136,3 @@ contributing to Backstage as a designer is easy. From styling guidelines to UX
 principles to Figma documents, we’ll make sure you’re equipped to chip in on
 this project. We’re excited to work with you! In the meantime, we’d love to hear
 from you on [Discord](https://discord.gg/EBHEGzX).
-
-[Back to Docs](../README.md)

docs/plugins/publishing.md

@@ -56,5 +56,3 @@ $ git reset --hard master
 $ yarn release
 $ git push --force
 ```
-
-[Back to Docs](../README.md)