fix typos

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 with exit code `2` and should not be restarted by default because more slashing are likely to happen
+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/reference/cli/index.md

@@ -2604,7 +2604,7 @@ stop-vc-when-validator-slashed-enabled: true
 </Tabs>
 
 
-Set to `true` to enable the [validators slashing protection](../../how-to/stop-vc-when-validator-slashed.md) and shut down the Validator Client when any owned validator is slashed. The default is `false`.
+Set to `true` to [stop the Validator Client when any owned validator is slashed](../../how-to/stop-vc-when-validator-slashed.md). The default is `false`.
 
 
 ### version