diff --git a/RELEASE-NOTES-next b/RELEASE-NOTES-next
index 2d64c7d0..e5ce52de 100644
--- a/RELEASE-NOTES-next
+++ b/RELEASE-NOTES-next
@@ -19,6 +19,7 @@ working. Please reach out to us in that case!
   • configure: respect --program-suffix
   • use exec to avoid leaving useless shell process
   • ipc: always include the marks property (even if empty)
+  • ipc: introduce GET_BINDING_STATE command
   • introduce “tiling_from” and ”floating_from” criteria
   • make dock client order deterministic (sorted by class/instance) as a
     side effect, i3bars without an explicit bar-id will be sorted according
diff --git a/docs/ipc b/docs/ipc
index 6cd43f58..d9bde97f 100644
--- a/docs/ipc
+++ b/docs/ipc
@@ -1,7 +1,7 @@
 IPC interface (interprocess communication)
 ==========================================
 Michael Stapelberg <michael@i3wm.org>
-September 2017
+June 2020
 
 This document describes how to interface with i3 from a separate process. This
 is useful for example to remote-control i3 (to write test cases for example) or
@@ -66,7 +66,7 @@ to do that).
 | 9 | +GET_CONFIG+ | <<_config_reply,CONFIG>> | Returns the last loaded i3 config.
 | 10 | +SEND_TICK+ | <<_tick_reply,TICK>> | Sends a tick event with the specified payload.
 | 11 | +SYNC+ | <<_sync_reply,SYNC>> | Sends an i3 sync event with the specified random value to the specified window.
-| 12 | +GET_BINDING_STATE+ | <<_binding_state_reply,BINDING_STATE>> | Request the current binding state, e.g. the currently active binding mode name.
+| 12 | +GET_BINDING_STATE+ | <<_binding_state_reply,BINDING_STATE>> | Request the current binding state, i.e. the currently active binding mode name.
 |======================================================
 
 So, a typical message could look like this: