diff --git a/spec/core/v2/ics-002-client-semantics/README.md b/spec/core/v2/ics-002-client-semantics/README.md
index e58e420ae..ec2357824 100644
--- a/spec/core/v2/ics-002-client-semantics/README.md
+++ b/spec/core/v2/ics-002-client-semantics/README.md
@@ -254,17 +254,6 @@ A `ClientMessage` is an opaque data structure defined by a client type which pro
 type ClientMessage = bytes
 ```
 
-#### `Counterparty`
-
-`Counterparty` is the data structure responsible for maintating the counterparty informations.
-
-```typescript
-interface Counterparty {
-    channelId: Identifier
-    keyPrefix: CommitmentPrefix
-}
-```
-
 ### Store paths
 
 Client state paths are stored under a unique client identifier.
@@ -354,6 +343,17 @@ to intervene to unfreeze a frozen client & provide a new correct ClientMessage w
 It is utilised to verify presence or absence of a particular key/value pair in state
 at a particular finalised height (necessarily associated with a particular commitment root).
 
+#### `Counterparty`
+
+`Counterparty` is the data structure responsible for maintating the counterparty informations.
+
+```typescript
+interface Counterparty {
+    channelId: Identifier
+    keyPrefix: CommitmentPrefix
+}
+```
+
 ### State verification
 
 Client types must define functions to authenticate internal state of the state machine which the client tracks.