Update CHANGELOG.md

CHANGELOG.md

@@ -6,15 +6,15 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
 ## <a name="v0.5.0">v0.5.0</a> - 2024-08-25
+
 ### Added
-- branch checkout: Add 'spice.branchCheckout.showUntracked' configuration to always show untracked branches in checkout prompt.
-- branch create: Add `--[no-]commit` flag and accompayning `spice.branchCreate.commit` configuration to create stacked branches without committing changes.
-- {branch, downstack, upstack, stack} submit: Support changing the default for --no-publish with the 'spice.submit.publish' configuration. If the configuration is set to false, use the --publish flag to opt-in to publishing.
-- submit: When importing existing CRs, git-spice will also detect existing stack navigation comments and update them instead of posting duplicates. This will work only for comments posted by this version or newer.
-### Changed
-- {branch, upstack} onto: Rebase commits even if the branch's base matches the target. This better matches expectations when the branch falls behind the target.
+- submit: Add `spice.submit.publish` configuration to allow making `--no-publish` the default. Use this to work with unsupported Git hosting services.
+- branch checkout: Add `spice.branchCheckout.showUntracked` configuration to always show untracked branches in checkout prompt.
+- branch create: Add `--[no-]commit` flag and accompanying `spice.branchCreate.commit` configuration to create stacked branches without committing changes.
+- submit: When importing existing CRs, also detect existing stack navigation comments and update them instead of posting duplicates. This will only work for comments posted git-spice v0.5 or newer.
 ### Fixed
-- {branch, stack, upstack, downstack} submit: When submitting with --no-publish, allow pushing to repositories managed by unsupported forges.
+- submit: When submitting with `--no-publish`, don't fail if the repository is hosted in an unsupported Git hosting services.
+- {branch, upstack} onto: Always rebase commits after the operation--even if the branch's base already matches the target. This better matches user expectations when the branch and base diverge.
 
 ## <a name="v0.4.0">v0.4.0</a> - 2024-08-09