Correct CHANGELOG to mention inset not inline

[ginnyTheCat]

I noticed this when reading the changelog to migrate a project to the new version. I'm not sure whether retroactively changing the changelog is considered acceptable behaviour in this project or whether appending a notice in the next changelog would be better.

Funnily this was actually guessed in #19613, though hard to notice among the other many false guesses.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

The CHANGELOG.md was updated to reflect a deprecation notice. The update documents a shift in preferred utility naming conventions, where inline-s-\* and inline-e-\* utility classes are being deprecated in favor of inset-s-\* and inset-e-\* utility classes. This is a documentation-only change with minimal modifications.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: correcting the CHANGELOG to reference 'inset' instead of 'inline' utilities, which aligns with the changeset.
Description check	✅ Passed	The description is related to the changeset, explaining the author's discovery of the error and uncertainty about retroactive changelog updates, which contextualizes the fix.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[RobinMalfait]

Thanks!