diff --git a/CHANGELOG.md b/CHANGELOG.md
index 37b3da0f8..353ccf863 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,23 +2,31 @@
 
 ## v0.54.0
 
-*August 9, 2024*
+*August 12, 2024*
 
-This release includes a number of breaking changes, including separating the packet
-timeout timestamp from the host `Timestamp` via defining a new bespoke `TimeoutTimestamp`
-type. The `cosmwasm` feature flag has been removed. CosmWasm implementations have also
-been migrated into their own separate workspace under the `cosmwasm` directory in an
-effort to simplify dependency management.
+This release includes a number of breaking changes, including separating the
+packet timeout timestamp from the host `Timestamp` via defining a new bespoke
+`TimeoutTimestamp` type. The `cosmwasm` feature flag has been removed. CosmWasm
+implementations have also been migrated into their own separate workspace under
+the `cosmwasm` directory in an effort to simplify dependency management.
 
 Notable bug fixes include:
-- correctly preventing expired client creation
-- expiring clients when the elapsed time from a trusted header matches the trusting period
-- allowing user-defined upgrade paths for client upgrades rather than just defaulting to `UPGRADED_IBC_STATE`
-- preventing `Timestamp::nanoseconds` from panicking by disallowing negative values from `tendermint::Time`
 
-Lastly, this release adds some new features, including allowing proof verification methods to accept custom paths, thus allowing light client developers to introduce custom path serialization logicinto their applications. CosmWasm response types have been refactored to match the `08-wasm` client API.
+- Correctly preventing expired client creation
+- Expiring clients when the elapsed time from a trusted header matches the
+  trusting period
+- Allowing user-defined upgrade paths for client upgrades rather than just
+  defaulting to `UPGRADED_IBC_STATE`
+- Preventing `Timestamp::nanoseconds` from panicking by disallowing negative
+  values from `tendermint::Time`
 
-This release bumps the MSRV of ibc-rs to 1.72.1. The `cosmwasm` dependency has also been bumped to 2.1.0.
+Lastly, this release adds some new features, including allowing proof
+verification methods to accept custom paths, thus allowing light client
+developers to introduce custom path serialization logic into their applications.
+CosmWasm response types have been refactored to match the `08-wasm` client API.
+
+This release bumps the MSRV of ibc-rs to 1.72.1. The `cosmwasm` dependency has
+also been bumped to 2.1.0.
 
 ### BREAKING CHANGES
 
@@ -66,7 +74,7 @@ instead of defaulting to `UPGRADED_IBC_STATE`.
 
 ### IMPROVEMENTS
 
-- Update `ibc-proto` to v0.46.0 and `tendermint` to v0.37.0.
+- [ibc] Update `ibc-proto` to v0.46.0 and `tendermint` to v0.37.0.
   ([\#1264](https://github.com/cosmos/ibc-rs/pull/1264))
 - [ibc-client-cw] Supersede `Bytes` with `cosmwasm::Binary`.
   ([\#1271](https://github.com/cosmos/ibc-rs/issues/1271))
diff --git a/RELEASES.md b/RELEASES.md
index 6d9263b53..680b6126f 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -3,21 +3,24 @@
 Currently, the ibc-rs repository contains multiple workspaces that each require
 a separate release via PR. When performing an ibc-rs, each of the following
 workspaces should be released:
+
 - [ ] The `ibc-derive` crate
-- [ ] The "main" ibc-rs workspace, which contains `ibc-core`, `ibc-apps`, `ibc-primitives`,
-      `ibc-query`, `ibc-clients`, `ibc-data-types`, and `ibc-testkit`
+- [ ] The "main" ibc-rs workspace, which contains `ibc-core`, `ibc-apps`,
+      `ibc-primitives`, `ibc-query`, `ibc-clients`, `ibc-data-types`, and
+      `ibc-testkit`
 
 ### ibc-derive
 
-As `ibc-derive` is an independent dependency of ibc-rs, if any changes were introduced to
-this crate, then a new version needs to be released prior to releasing a new version of ibc-rs.
-This is done by:
+As `ibc-derive` is an independent dependency of ibc-rs, if any changes were
+introduced to this crate, then a new version needs to be released prior to
+releasing a new version of ibc-rs. This is done by:
+
 1. Bumping the version of `ibc-derive` in `crates/ibc-derive/Cargo.toml`
 2. Running `cargo publish -p ibc-derive` to publish the crate to crates.io
 3. Update the version of `ibc-derive` in the `Cargo.toml` of each crate that depends on it
 
-If no changes were introduced since the last release of ibc-rs, then there is no need to
-publish a new version of this crate.
+If no changes were introduced since the last release of ibc-rs, then there is no
+need to publish a new version of this crate.
 
 ### ibc-rs