1
0
Fork 0
mirror of https://github.com/dragonflydb/dragonfly.git synced 2024-12-14 11:58:02 +00:00

docs(rdb): fix typo (#989)

peform -> perform

Signed-off-by: Ikko Eltociear Ashimine <eltociear@gmail.com>
This commit is contained in:
Ikko Eltociear Ashimine 2023-03-25 15:08:39 +09:00 committed by GitHub
parent 52ac06e358
commit 82121a205b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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.