From 7fefeb6d08bd7253355c59ee8ea13a582999694a Mon Sep 17 00:00:00 2001
From: Konstantin Lebedev <9497591+kmlebedev@users.noreply.github.com>
Date: Wed, 27 Sep 2023 11:43:05 +0500
Subject: [PATCH] Updated Replication (markdown)

---
 Replication.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Replication.md b/Replication.md
index bcef2d2..981e200 100644
--- a/Replication.md
+++ b/Replication.md
@@ -86,11 +86,11 @@ If one replica is missing, there are no automatic repair right away. This is to
 To repair the missing replicas, you can use `volume.fix.replication` in `weed shell`.
 
 ### Replicate without deleting
-In certain circumstances—like adding/removing/altering replication settings of volumes or servers—the best strategy is to only repair under-replicated volumes and not delete any while working on volume and server modifications, in this situation use the flag `noDelete`: 
+In certain circumstances—like adding/removing/altering replication settings of volumes or servers—the best strategy is to only repair under-replicated volumes and not delete any while working on volume and server modifications, in this situation use the flag `doDelete`: 
 
-`volume.fix.replication -noDelete`
+`volume.fix.replication -doDelete=false`
 
- After all replications and modifications are finished, desired replication consensus can then be obtained by running `volume.fix.replication` without the 'noDelete' flag.
+ After all replications and modifications are finished, desired replication consensus can then be obtained by running `volume.fix.replication` without the 'doDelete' flag.
 
 ## Change replication