- don't want to have multiple references to versions that need to be
  updated along with package.json changes
  - these are for the most part wrapped by TSDX, so would only need to
    know a version in an advanced use-case, where having to check the
    package.json is not unreasonable
  - we also try to keep up with latest, so if it's bleeding edge or not
    shouldn't be impactful for too long
    - e.g. will be upgrading to Rollup v2 soon enough, no one's even
      requested it, so no need to add changing version in a few places
      to maintenance burden
      - also easy to forget to update and then have outdated/incorrect
        docs

- same jive with permalink to PR -- if it's not already outdated, it's
  likely to become outdated often
  - reference Parcel's aliasing docs instead of PR that adds it

- basically `diff templates/react/README.md templates/react-with-storybook/README.md`
  should only show the Storybook differences
  - make code block annotation are consistent
    - one had bash and shell and the other didn't
    - also use txt instead of shell for file structure
      - file structure isn't a shell command
  - make `np` link consistent

- the React w/ Storybook README should say its with Storybook, not just
  for plain React to be explicit

- these directions already exist in the "Commands" section, so no need
  to duplicate them

- also consistently call it "example plaground"
- and fix order and grammar in Storybook "Commands" section that
  references both

- welp, this never got updated when Actions were added

- those are far more detailed about various pieces than the basic one

- basically just remove the React-specific pieces of the React one
- substitute some references with non-React ones where applicable

- also be more explicit about library use-case in each README