Fix some typos

[jaakkonakaza]

Description

Noticed the heading below says Changsets instead of Changesets so used a proofreading plugin to find some typos

Changsets

We use Changesets to automatically create our changelog per each release. Any changes or additions to the Library assets in /lib must be documented with a new Changeset. This can be done as follows:

2. Navigate to the root of the project on your feature branch.
3. Run pnpm changeset to trigger the Changeset CLI.
4. Follow the instructions when prompted.
   • Changesets should be either minor or patch. Never major.
   • Prefix your Changeset description using: feature:, chore: or bugfix:.
5. Changeset .md files are added to the /.changeset directory.
6. Commit and push the the new changeset file.

Checklist

Please read and apply all contribution requirements.

• PR targets the dev branch (NEVER master)
• All website documentation is current with your changes
• Ensure Prettier formatting is current - run pnpm format
• Ensure Prettier linting is current - run pnpm format
• All test cases are passing - run pnpm test
• Includes a changeset (if relevant; see above)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
floating-ui-svelte	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 13, 2024 4:46pm

[Hugos68]

lgtm, thanks!
PS: I see the checklist is left untouched, you can actually check these, this also notifies us you've covered them.

[Hugos68]

@endigo9740 Is this good to merge?

[endigo9740]

@Hugos68 @jaakkonakaza I've given my approval, but looks like a minor merge conflict will need to be resolved here.

[Hugos68]

I've resolved the conflict, I'll merge once CI passes👍