Fixes small typos and improves clarity in changesets

[arthurgousset]

Description

Fixes small typos and improves clarity in changesets created in this PR:

• Fix releasing + beta release info #66

Left comments in #66 a couple of seconds after it was merged. This small PR applies those changes retrospectively.

Tested

No code change

Related issues

• Fix releasing + beta release info #66

Backwards compatibility

No code change

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8d2c864

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[aaronmgdr]

thank you for this

[arthurgousset]

better to make the changes in the changeset files so they are there for the actual release

Originally posted by @aaronmgdr in #66 (comment)

@aaronmgdr: As suggested, I made the changes in the changeset files, rather than in CHANGELOG.md directly.
That means the next time changeset version is run, the updated changeset files should reflect in the changelog.

I didn't re-generate and commit the changelog manually, because when I ran the command I got the following messages:

$ GITHUB_TOKEN=<my-personal-access-token> yarn changeset version
🦋  warn ===============================IMPORTANT!===============================
🦋  warn You are in prerelease mode
🦋  warn If you meant to do a normal release you should revert these changes and run `changeset pre exit`
🦋  warn You can then run `changeset version` again to do a normal release
🦋  warn ----------------------------------------------------------------------
🦋  All files have been updated. Review them and commit at your leisure

No CHANGELOG is generated unless I exit prerelease mode. When I exit prerelease mode, the changelog reflects a "production" release (i.e. not beta).

I was not sure that exiting prerelease mode is appropriate here.
Perhaps best to just commit this and leave CHANGELOG unchanged?
What do you think?

[aaronmgdr]

@arthurgousset yeah no need to do anything.

[arthurgousset]

Sounds good, thanks!