From dfc873788e6bfb441a60db370382e1151cec137b Mon Sep 17 00:00:00 2001 From: Mehdi AOUADI Date: Thu, 21 Dec 2023 17:40:33 +0100 Subject: [PATCH] update dg slashing wording --- docs/how-to/enable-doppelganger-detection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to/enable-doppelganger-detection.md b/docs/how-to/enable-doppelganger-detection.md index 66907aab7..7d2081418 100644 --- a/docs/how-to/enable-doppelganger-detection.md +++ b/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 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