nit clarification

Author: khadni

src/content/cre/concepts/finality-ts.mdx

@@ -42,17 +42,17 @@ CRE uses the chain's native `safe` and `latest` block tags respectively for all
 
 **FINALIZED:**
 
-When you specify `FINALIZED` in your workflow, CRE automatically maps this to a native finality tag or a block depth threshold depending on the chain.
-
-| Chain                           | Finality Method              | Block Depth |
-| ------------------------------- | ---------------------------- | ----------- |
-| Arbitrum One / Arbitrum Sepolia | Native `finalized` tag       | —           |
-| Avalanche / Avalanche Fuji      | Native `finalized` tag       | —           |
-| Base / Base Sepolia             | Native `finalized` tag       | —           |
-| BNB Chain / BNB Testnet         | Native `finalized` tag       | —           |
-| Ethereum / Ethereum Sepolia     | Native `finalized` tag       | —           |
-| OP Mainnet / OP Sepolia         | Native `finalized` tag       | —           |
-| Polygon / Polygon Amoy          | Block depth (500 blocks ago) | 500         |
+When you specify `FINALIZED` in your workflow, CRE automatically maps this to its finality method—whether it uses the native finality tag or block depth (with the number of blocks specified for block depth).
+
+| Chain                           | Finality Method          |
+| ------------------------------- | ------------------------ |
+| Arbitrum One / Arbitrum Sepolia | Native `finalized` tag   |
+| Avalanche / Avalanche Fuji      | Native `finalized` tag   |
+| Base / Base Sepolia             | Native `finalized` tag   |
+| BNB Chain / BNB Testnet         | Native `finalized` tag   |
+| Ethereum / Ethereum Sepolia     | Native `finalized` tag   |
+| OP Mainnet / OP Sepolia         | Native `finalized` tag   |
+| Polygon / Polygon Amoy          | Block depth (500 blocks) |
 
 ## Finality for chain reads