diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1e792d7..ce80416 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,12 +17,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Support for [RFC 9758](https://www.rfc-editor.org/rfc/rfc9758.html): implement the `ipn` 3-element format and LocalNode (`ipn:!.x`) EIDs
 - Custom source EIDs (including `dtn:none`) can be specified via AAP 2.0 and the corresponding tools (e.g. `aap2-send --source <eid>`), as long as the client provides the administrative (BDM) secret and requests BDM authorization
 - Add a compile-time flag `CLA_MTCP_ION_STCP_COMPATIBILITY` to make the MTCP CLA compatible with ION's STCP, which uses a different encoding for the length field. Note that this breaks compatibility with other implementations of the current MTCP draft specification.
+- Add a compile-time flag `BUNDLE7_ALLOW_NO_PRIMARY_CRC_NO_BIB` (on by default) to allow processing bundles without a primary block CRC and no BIB.
 - Add a small Python tool (`aap2-fib-logger`) to show FIB changes propagated via AAP 2.0 (also as an example how to handle this)
 
 ### Removed
 
 - The `--agentid` option has been removed for `aap2-bdm-static` and `aap2-configure-link`, which do not need to register an agent ID, as they do not send/receive bundles.
-- Add a compile-time flag `BUNDLE7_ALLOW_NO_PRIMARY_CRC_NO_BIB` (on by default) to allow processing bundles without a primary block CRC and no BIB.
 
 ### Changed
 
@@ -33,7 +33,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 
-- AAP 2.0 agents can now registered without an agent ID in case they do not wish to send/receive bundles (e.g. if they only do FIB control).
+- AAP 2.0 agents can now be registered without an agent ID in case they do not wish to send/receive bundles (e.g. if they only do FIB control).
 - The full FIB is now only sent once to AAP 2.0 FIB subscribers, when they connect. Then, only changes are propagated.