diff --git a/01-messaging.md b/01-messaging.md
index cf049f4..98f765f 100644
--- a/01-messaging.md
+++ b/01-messaging.md
@@ -35,8 +35,8 @@ A node MUST fail the channels if it receives a message of unknown type, if that
 The messages are grouped logically into 4 groups by their most significant set bit:
 
  - Setup & signalling (types `0`-`31`): messages related to supported features and error reporting. These are described below.
- - Channel (types `32`-`127`): comprises messages used to setup, update and tear down micropayment channels. These are described in [BOLT #2](02-peer-protocol.md).
- - HTLC (types `128`-`255`: comprises messages related to adding, revoking and settling HTLCs on a micropayment channel. These are described in [BOLT #2](02-peer-protocol.md).
+ - Channel (types `32`-`127`): comprises messages used to setup and tear down micropayment channels. These are described in [BOLT #2](02-peer-protocol.md).
+ - Commitment (types `128`-`255`: comprises messages related to updating the current commitment transaction, which includes adding, revoking, and settling HTLCs, as well as updating fees and exchanging signatures. These are described in [BOLT #2](02-peer-protocol.md).
  - Routing (types `256`-`511`): node and channel announcements, as well as any active route exploration. These are described in [BOLT #7](07-routing-gossip.md).
 
 The size of the message is required to fit into a 2 byte unsigned int by the transport layer, therefore the maximum possible size is 65535 bytes.