Refine terminology: 'connected' instead of 'included'

- Change 'included in the transaction' to 'connected to the transaction'
- Fix tooltip formatting: move comma inside tooltip for 'transaction hash'
- 'Connected' is more accurate and user-friendly than 'included'

Author: MantisClone

use-cases/payment-detection.mdx

@@ -6,7 +6,7 @@ description: "Automatically detect and verify crypto payments with real-time blo
 
 ## Overview
 
-Traditional crypto payments lack business context. You receive a <Tooltip tip="Unique identifier of a transaction recorded on the blockchain">transaction hash</Tooltip>, but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale.
+Traditional crypto payments lack business context. You receive a <Tooltip tip="Unique identifier of a transaction recorded on the blockchain">transaction hash,</Tooltip> but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale.
 
 Request IDs solve this by attaching business context to every payment. Each request gets a unique Request ID that connects payments back to your specific invoice, order, or subscription with cryptographic certainty.
 
@@ -72,7 +72,7 @@ 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 included in the transaction
+    Customer sends payment to your wallet address - the Request ID is connected to the transaction
   </Step>
 
   <Step title="Automatic Detection">