Someone reading release notes is usually deciding whether to upgrade and what the upgrade will require. A list of internal changes forces them to reconstruct the consequence.
Put required actions first
Name a changed default, renamed setting or migration next to the command or edit needed. Separate those changes from improvements that require no action.
Describe the result
A fix should identify the behaviour that changed and who encountered it. Avoid calling a release “more reliable” when the evidence only establishes one corrected failure path.