Fix typos in documentation

[toyeshhm]

Summary

Corrects typos in the documentation site. Two of them change what the docs
tell you the API is.

useElementInteraction publishes a type that does not compile

The Parameters section declares:

export interface ElementInteractionOptions<
  E extends HTMLElement,
> extends Parital<ElementInteractionHandlers<E>> {

Parital is not a TypeScript utility type, so copying this declaration out of
the API docs produces Cannot find name 'Parital'. The source
(packages/core/src/interaction/useElementInteraction.tsx) declares Partial.

useRadioGroup documents a prop name that does not exist

The Returns section lists requried among the props getRadioProps returns,
while the CombinedRadioGroupReturnValue signature immediately below it has
required?: boolean.

Remaining corrections

• accordian → accordion in the Collapse description and prose, and in the
  alias frontmatter for Collapse and ExpansionPanel — so the correct spelling
  matches when searching the docs
• constrast → contrast in the keywords frontmatter for contrastColor
  and isContrastCompliant
• implicity → implicitly in the quoted TypeScript error in the Autocomplete
  demo
• isntead → instead, simpley → simply, cololrs → colors,
  Diable → Disable (a Button label in the v5-to-v6 guide)
• doubled words: "the the" in the InitialCoords doc comment on the
  useFixedPositioning page, "to to" in the randomInt description

Documentation only — no source, test or build files touched.

Deliberately left alone

• transitionIn and initialX/initialY are real prop names, not typos
• the blog post's exerpt: frontmatter key is misspelled, but blog/data.ts,
  blog/page.tsx and scripts/updateAlgoliaIndex.ts all read exerpt, so
  renaming it here alone would break the blog excerpt. Happy to fix it across
  those files in a separate PR if you want it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2b8fb85

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

[vercel]

@toyeshhm is attempting to deploy a commit to the Mikkel Laursen's projects Team on Vercel.

A member of the Team first needs to authorize it.