Update mev-protection.md (#634)

updates per Odran's request

# Description

<!--- Describe your changes to provide context for reviewers, including
why it is needed -->

# Changes

<!-- List of detailed changes (how the change is accomplished) -->

- [ ] ...
- [ ] ...

<!--
## Related Issues

Fixes #
-->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

## Release Notes

* **Documentation**
* Clarified MEV protection documentation to better explain how the
settlement solution process works and emphasizes the protection
mechanism preventing transaction mempool exposure.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: pretf00d

docs/cow-protocol/concepts/benefits/mev-protection.md

@@ -13,10 +13,8 @@ MEV attacks happen on most major exchanges. However, CoW Protocol's unique tradi
 - **Uniform Clearing Prices**: If the same token pair (such as ETH-USDC) is traded multiple times in the same [batch](../introduction/fair-combinatorial-auction), the assets will clear for the same market prices for each trade in the same direction.
   This mechanism is called a "uniform directed clearing price" and it makes transaction order irrelevant, so MEV bots cannot re-order trades in order to extract a profit.
   Uniform directed clearing prices enable the Ethereum DeFi ecosystem to establish consistent prices for identical directed token pairs within the same block, addressing the inconsistency caused by the design of Constant Function Market Makers (CFMMs) like traditional Uniswap liquidity pools.
-- **Delegated Trade Execution**: On CoW Protocol, bonded third parties known as [solvers](../introduction/solvers) execute trades on behalf of users.
-  This means that users are never directly exposed to MEV on-chain (though the solvers may be).
-  The winning solver is required to give users the price they signed or greater, meaning that solvers take on all price risk from potential MEV attacks.
-  Solvers are professional parties, so they calculate the optimal slippage for each trade and match liquidity off-chain through CoWs or private market makers when possible in order to reduce MEV risk.
+- **Delegated Trade Execution**: On CoW Protocol, independent bonded [solvers](../introduction/solvers) compete to find and submit settlement solutions for batches of user-signed intents. Because users do not submit their swaps directly on-chain, they are not directly exposed to public mempool MEV in the same way as ordinary on-chain swaps. The winning solver must provide at least the price accepted by the user’s signed intent, and bears the risk of sourcing a valid settlement under those constraints.
+
 - **Coincidence of Wants**: MEV attacks rely on the dynamics of automated market makers (AMMs) for their price exploitation. When orders are matched peer-to-peer through a CoW, however, they don't tap into on-chain liquidity, and are therefore protected from MEV 
 
 Read more about CoW Protocol's unparalleled MEV protection [on our blog](https://blog.cow.fi/how-cow-swap-solves-the-mev-problem-fd35b0127390).