update TOC

pubsub/README.md

@@ -32,6 +32,7 @@ and spec status.
     - [The RPC](#the-rpc)
     - [The Message](#the-message)
     - [Message Signing](#message-signing)
+    - [Message Identification](#message-identification)
     - [The Topic Descriptor](#the-topic-descriptor)
         - [AuthOpts](#authopts)
             - [AuthMode 'NONE'](#authmode-none)
@@ -145,7 +146,7 @@ economics (see e.g.
 and
 [here](https://ethresear.ch/t/improving-the-ux-of-rent-with-a-sleeping-waking-mechanism/1480)).
 
-## Message identification
+## Message Identification
 
 To uniquely identify a message in a set of topics, a `message_id` is computed based on the message.
 This can be configured on the application layer, as `message_id_fn(*Message) => message_id`, 

pubsub/gossipsub/gossipsub-v1.1.md

@@ -37,7 +37,8 @@ See the [lifecycle document][lifecycle-spec] for context about maturity level an
   - [Explicit Peering Agreements](#explicit-peering-agreements)
   - [PRUNE Backoff and Peer Exchange](#prune-backoff-and-peer-exchange)
     - [Protobuf](#protobuf)
-  - [Signature policy](#signature-policy)
+  - [Signature Policy](#signature-policy)
+    - [Signature Policy Options](#signature-policy-options)
   - [Flood Publishing](#flood-publishing)
   - [Adaptive Gossip Dissemination](#adaptive-gossip-dissemination)
   - [Outbound Mesh Quotas](#outbound-mesh-quotas)
@@ -135,7 +136,7 @@ message PeerInfo {
 }
 ```
 
-### Signature policy
+### Signature Policy
 
 The usage of the `signature`, `key`, `from`, and `seqno` fields in `Message` is now configurable.
 Initially this could be configured globally, however, configuration on a per-topic basis will facilitate mixed protocols better.
@@ -146,7 +147,7 @@ the `seqno` and `from` fields form the `message_id`, and should be verified to a
 In content-stamped messaging, the fields may negatively affect privacy:
 revealing the relationship between `data` and `from`/`seqno`.
 
-#### Signature policy options
+#### Signature Policy Options
 
 In gossipsub v1.1, these fields are strictly present and verified, or completely omitted altogether:
 - `StrictSign`: