update doc

docs/how-to/enable-doppelganger-detection.md

@@ -10,7 +10,7 @@ Doppelganger detection checks if the validators' keys are already active before
 
 When enabled, doppelganger detection is triggered from two entry points:
 
-1. At [validator client startup](../get-started/start-teku.md#start-teku): If at least one doppelganger is detected, the validator client shuts down after it finishes the check.
+1. At [validator client startup](../get-started/start-teku.md#start-teku): If at least one doppelganger is detected, the validator client shuts down after it finishes the check with exit code `2` and should not be restarted by default because more slashing are likely to happen
 2. When importing keys via the [key manager API](https://ethereum.github.io/keymanager-APIs/): Any detected doppelganger's keys are ignored (not imported). The other keys are imported and the validators start performing their duties after it finishes the check.
 
 :::warning

docs/how-to/stop-vc-when-validator-slashed.md

@@ -8,7 +8,7 @@ sidebar_position: 8
 
 When enabled, this feature will monitor the validators slashing and shut down the validator client when any of the owned validator is slashed.
 
-When enabled, the validator client will shut down with exit code `2` if any owned validator is slashed (based on the attester and proposer slashing events received through the peer to peer network).
+If any owned validator is slashed,  the validator client will shut down with exit code `2` (based on the attester and proposer slashing events received through the peer to peer network).
 When that happens, the validator client should not be restarted by default because more slashing are likely to happen. We recommend restarting the validator client with the [Doppelganger Detection](./enable-doppelganger-detection.md) enabled.
 
 :::warning