update protocol readmes

Author: apenzk

protocol/mcr/README.md

@@ -4,11 +4,9 @@ This directory contains the implementation of the MCR protocol, which handles ro
 
 ## Overview
 
-**MCR** implements a staking-based settlement where validators commit L2-blocks on Layer 1 (L1). MCR is responsible for aggregating multiple commitments into a single commitment. It provides:
+**MCR** implements a staking-based settlement where validators commit to a state from L2 on Layer 1 (L1). MCR accepts commitments from all staked attesters and aggregates them into a single confirmation. The contracts on L1 tracks block commitments, epochs, stake and rewards.
 
-The distinguishing feature is that there is only one type of actor, which is the attester.
-
-Validators stake tokens to participate in block validation. They commit to L2-blocks on L1, and the contract on L1 tracks block commitments, epochs, and stake. The contracts also manage validators and custodian staking and unstaking. The contract validates if commitments have reached two-thirds supermajority stake, and rewards or slashes validators based on their actions.
+The distinguishing feature to PCP is that there is only one type of actor, which is the attester.
 
 For further details see the [RFC for MCR](https://github.com/movementlabsxyz/rfcs/pull/29) and the [MIP-34](https://github.com/movementlabsxyz/MIP/blob/main/MIP/mip-34).
 
@@ -35,11 +33,3 @@ For further details see the [RFC for MCR](https://github.com/movementlabsxyz/rfc
 - [`util/`](util/) - Shared utilities
   - [`config/`](util/config/) - Configuration management
   - [`types/`](util/types/) - Common type definitions
-
------
-
-TODO: remove once we have used this content at the correct place
-
-- **Setup**: Prepares local environments or deploys contracts, manages configuration for local and deployment setups, and ensures contract deployment when needed.
-- **Runner**: Orchestrates the setup and execution of configuration tasks, applies setup steps, and logs processes for debugging.
-

protocol/mcr/dlu/README.md

@@ -1,4 +1,5 @@
 # Deployed Logic Units (DLU)
-DLUs are units of logic that are not generally run within an independent process, but which must be deployed somewhere. Smart contracts are DLU. 
 
-In this directory, we include DLU and the means via which to deploy them to various environments.
+DLUs are units of logic that are not generally run within an independent process, but which must be deployed somewhere. Smart contracts are DLU.
+
+In this directory, we include DLU and the means via which to deploy them to various environments.

protocol/pcp/README.md

@@ -4,12 +4,11 @@ This directory contains the implementation of the PCP protocol, which handles co
 
 ## Overview
 
-PCP (Postconfirmation Protocol) is responsible for handling post-confirmation commitment settlement between different parts of the system. It provides:
+**PCP** implements a staking-based settlement where validators commit to a state from L2 on Layer 1 (L1). PCP accepts commitments from all staked attesters. A specialized attester - the acceptor - aggregates them into a single confirmation, called a postconfirmation. The contracts on L1 tracks block commitments, epochs, stake and rewards.
 
-1. Contract deployment and management
-2. Commitment posting and verification
-3. Client interfaces for interacting with the protocol
-4. Testing and mock implementations
+The distinguishing feature to MCR is that there are two types of actors, which are the attesters and the acceptors.
+
+For further details see the [MIP-37](https://github.com/movementlabsxyz/MIP/blob/main/MIP/mip-37).
 
 ## Architecture
 

sdk/cli/ffs-client/README.md

@@ -1,2 +1,3 @@
 # `ffs-client`
-The command line tool for interacting with live FFS services.
+
+The command line tool for interacting with live FFS services.