Improve terminology precision in How It Works section

- Replace 'embedded' with 'included in the transaction' (more precise, commonly used term)
- Change 'request status updates and you receive webhook' to 'you receive webhook with payment details'
- Avoids claiming request state changes (technically inaccurate - IPFS stores request state, payments detected via subgraphs, status derived from combining both)
- Focuses on what user experiences (webhook notification) rather than internal state management

Author: MantisClone

use-cases/payment-detection.mdx

@@ -72,15 +72,15 @@ These scenarios all use automatic payment detection. [See technical details on d
   </Step>
 
   <Step title="Customer Pays">
-    Customer sends payment to your wallet address - the Request ID is automatically embedded
+    Customer sends payment to your wallet address - the Request ID is automatically included in the transaction
   </Step>
 
   <Step title="Automatic Detection">
     Request Network monitors <Tooltip tip="Decentralized networks where cryptocurrency transactions are recorded">blockchains</Tooltip> and matches payments to your requests
   </Step>
 
   <Step title="Get Notified">
-    When a payment is matched, your request status updates and you receive a <Tooltip tip="HTTP callback that notifies your server when payment events occur">webhook</Tooltip> notification
+    When a payment is detected, you receive a <Tooltip tip="HTTP callback that notifies your server when payment events occur">webhook</Tooltip> notification with payment details
   </Step>
 </Steps>