Audit: Identify hotfixes and capture as issues

[jessicaschilling]

Following on from the content inventory created in issue #190, available at https://docs.google.com/spreadsheets/d/1fUsep3keTFrp7TkfiVHcwOdOK0mKvPmdOd5dSFEdhjI/edit?ts=5d6982c8#gid=0 :

• Examine items for potential near- to mid-term hotfixes. (Hotfixes can vary in size of effort required, but must be limited to a discrete effort; in other words, items that touch multiple foci of work or attempt to solve larger, more strategic problems with our docs don't count as hotfixes.)
• Capture those hotfixes in this repo, prefixing the title of the issue with Hotfix for optical usefuleness. Be sure to use the docs-ipfs and OKR: Hotfixes labels, assign an appropriate difficulty label, and assign to the OKR: Hotfixes epic.
• If a hotfix is a good candidate for community involvement, be sure to add the help wanted label.
• Move the newly-created issue into the Soon pipeline.

[jessicaschilling]

@ericronne and I will work through these -- but anyone else's help is more than appreciated! If you want to join in the fun, hit us up to talk through how we're dividing and conquering.

[jessicaschilling]

ETA: @ericronne nailed this with pretty much zero help on my part ...

[jessicaschilling]

All of the items in the spreadsheet have been accounted for and issue-ized! Closing this issue.