updated the table text

Author: krofax

pages/stack/interop/reading-logs.mdx

@@ -24,7 +24,6 @@ Instead of relying solely on [L2ToL2CrossDomainMessenger](https://github.com/eth
 
 This enables developers to:
 
-*   Reference attestations or events from other chains.
 *   Build cross-chain applications that react to events happening across the Superchain.
 *   Create novel applications that leverage data from multiple chains.
 
@@ -202,12 +201,12 @@ flowchart TD
 
 ## Comparison with `L2ToL2CrossDomainMessenger`
 
-| Feature    | L2ToL2CrossDomainMessenger       | CrossL2Inbox#validateMessage          |
-| ---------- | -------------------------------- | ------------------------------------- |
-| Purpose    | Send messages between chains     | Verify logs from other chains         |
-| Initiation | Active sending from source       | Passive reading from destination      |
-| Use Case   | Transfer tokens, trigger actions | Verify attestations, reference events |
-| Flow       | Push model                       | Pull model                            |
+| Feature    | L2ToL2CrossDomainMessenger                     | CrossL2Inbox#validateMessage                      |
+| ---------- | ---------------------------------------------- | ------------------------------------------------- |
+| Purpose    | Send messages between chains                   | Verify logs from other chains or local chain      |
+| Initiation | Source explicitly sends message to destination | Destination queries for existing logs from source |
+| Use Case   | Transfer tokens, trigger actions               | Verify attestations, reference events             |
+| Flow       | Push model                                     | Pull model                                        |
 
 ## End-to-End flow comparison