diff --git a/changelog/unreleased/issue-21866 b/changelog/unreleased/issue-21866
index 815a472c1..3e6141874 100644
--- a/changelog/unreleased/issue-21866
+++ b/changelog/unreleased/issue-21866
@@ -1,8 +1,8 @@
-Bugfix: Hide progress bar for stats command in JSON mode
+Bugfix: Hide `stats` progress bar in JSON mode
 
-Since restic 0.19.0, the stats command shows a progress bar. However,
-it was also active when given the `--json` option resulting in text
-mixed with JSON. This has been fixed.
+Since restic 0.19.0, the `stats` command shows a progress bar. This
+progress bar was unintentionally displayed also when using the `--json`
+option, mixing regular text output with JSON. This is now fixed.
 
 https://github.com/restic/restic/issues/21866
 https://github.com/restic/restic/pull/21871
diff --git a/changelog/unreleased/issue-21869 b/changelog/unreleased/issue-21869
index 774c5e4d1..3b69fce76 100644
--- a/changelog/unreleased/issue-21869
+++ b/changelog/unreleased/issue-21869
@@ -1,11 +1,12 @@
 Bugfix: Restore old behavior of `snapshots --latest <n>` without `--group-by`
 
-Restic 0.19.0 changed the behavior of `snapshots --latest <n>` to no longer
-group snapshots by default.
+Restic 0.19.0 accidentally changed the behavior of `snapshots --latest <n>`
+to no longer group snapshots by host and paths by default.
 
-`snapshots --latest <n>` has been reverted to the old behavior if `--group-by`
-is not specified. When specifying `--group-by`, the output is still grouped as
-requested like in restic 0.19.0.
+The `snapshots --latest <n>` command now again uses the old behavior of
+grouping by host and paths when `--group-by` is not specified. However, when
+specifying `--group-by` the output is still grouped as requested, as in restic
+0.19.0.
 
 https://github.com/restic/restic/issues/21869
 https://github.com/restic/restic/pull/21875
diff --git a/changelog/unreleased/issue-21899 b/changelog/unreleased/issue-21899
index 1eceba1d9..87c32d068 100644
--- a/changelog/unreleased/issue-21899
+++ b/changelog/unreleased/issue-21899
@@ -1,9 +1,8 @@
-Bugfix: Fix excludes of duplicate directory entries during `backup`
+Bugfix: Make `backup` respect excludes for duplicate directory entries
 
-Since restic 0.19.0, creating a backup of a directory containing
-duplicate directory entries always resulted in "Warning: at least
-one source file could not be read" even if the files in question
-were excluded. This has been fixed.
+Since restic 0.19.0, backing up a directory with duplicate directory
+entries always produced "Warning: at least one source file could not be
+read", even when those files were excluded. This has now been fixed.
 
 https://github.com/restic/restic/issues/21899
 https://github.com/restic/restic/pull/21900
diff --git a/changelog/unreleased/pull-21876 b/changelog/unreleased/pull-21876
index ec8e2d8f1..008a70318 100644
--- a/changelog/unreleased/pull-21876
+++ b/changelog/unreleased/pull-21876
@@ -1,8 +1,9 @@
 Bugfix: Show timezone location in `snapshots` output
 
-Since restic 0.19.0, the `snapshots` command printed the current timezone when
-listing snapshots. However, the timezone can change during the year, for example,
-due to daylight saving time. Instead just print the name of the current location.
+With restic 0.19.0, the `snapshots` command printed the current timezone when
+listing snapshots. However, that timezone label might change during the year,
+for example with daylight saving time. Restic now prints a more consistent and
+shorter version of the text.
 
 https://github.com/restic/restic/pull/21876
 https://forum.restic.net/t/possible-bug-in-timezone-naming/10867
diff --git a/changelog/unreleased/pull-21879 b/changelog/unreleased/pull-21879
index a64a4900f..00fc1948f 100644
--- a/changelog/unreleased/pull-21879
+++ b/changelog/unreleased/pull-21879
@@ -1,7 +1,7 @@
-Bugfix: prevent crash in mountpoint validation if mountpoint is inaccessible
+Bugfix: Prevent crash in mountpoint validation if mountpoint is inaccessible
 
 Since restic 0.19.0, the `mount` command validates a mountpoint before loading
 the repository. If restic was unable to stat the mountpoint, this would result
-in a crash. This has been fixed to correctly return an error instead.
+in a crash. This has now been fixed to correctly return an error instead.
 
 https://github.com/restic/restic/pull/21879