update links

Author: krofax

pages/stack/interop/reading-logs.mdx

@@ -47,7 +47,7 @@ The process works through the [`CrossL2Inbox`](https://github.com/ethereum-optim
 ### Key components
 
 *   **[Identifier](/stack/interop/tutorials/relay-messages-cast#message-identifier)**: A struct containing information about the log, including `chainId`, `origin` (contract address), and other log metadata
-*   **validateMessage**: Function that verifies a log's authenticity before allowing its use
+*   **[validateMessage](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L79)**: Function that verifies a log's authenticity before allowing its use
 
 ## Example: cross-chain attestation verification
 
@@ -104,7 +104,7 @@ sequenceDiagram
 
 2.  The DeFi application calls a verification function on an attestation verifier contract, passing the attestation's identifier and event data.
 
-3.  The attestation verifier calls [`validateMessage()`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L79) on the `CrossL2Inbox` contract, passing the attestation identifier and a hash of the event data.
+3.  The attestation verifier calls `validateMessage()` on the `CrossL2Inbox` contract, passing the attestation identifier and a hash of the event data.
 
 4.  The [`CrossL2Inbox`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol) contract interacts with the [`OP-Supervisor`](/stack/interop/op-supervisor) service to check if the specified log exists on the source chain.
 
@@ -120,7 +120,7 @@ sequenceDiagram
 
 When implementing an attestation verification system using `CrossL2Inbox`, you would need to:
 
-1.  **Create an [Identifier struct](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L13)** that uniquely identifies the attestation event:
+1.  **Create an Identifier struct** that uniquely identifies the attestation event:
     *   Include the source chain ID where the attestation was created
     *   Specify the EAS contract address (origin) that emitted the event
     *   Include other necessary parameters to identify the specific log