From 82121a205b06208540c8864b6b25334d8a81ccbc Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Sat, 25 Mar 2023 15:08:39 +0900 Subject: [PATCH] docs(rdb): fix typo (#989) peform -> perform Signed-off-by: Ikko Eltociear Ashimine --- docs/rdbsave.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rdbsave.md b/docs/rdbsave.md index 5a8b34f8c..db2de5567 100644 --- a/docs/rdbsave.md +++ b/docs/rdbsave.md @@ -42,7 +42,7 @@ through all the process shards. Snapshotting may take time, during which, DF may These mutations won't be part of the snapshot, because the cut captures data up to the point **it has started**. This is perfect for backups. I call this variation - conservative snapshotting. -However, when we peform snapshotting for replication, we would like to produce a snapshot +However, when we perform snapshotting for replication, we would like to produce a snapshot that includes all the data upto point in time when the snapshotting **finishes**. I called this *relaxed snapshotting*. The reason for relaxed snapshotting is to avoid keeping the changelog of all mutations during the snapshot creation.