From dd72aff98a46c6e20848ac7ae5f7b19d45802493 Mon Sep 17 00:00:00 2001
From: Gerard Bosch <30733556+gerardbosch@users.noreply.github.com>
Date: Tue, 28 Feb 2023 12:47:28 +0100
Subject: [PATCH] docs: bisync: clarification of --resync

---
 docs/content/bisync.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/content/bisync.md b/docs/content/bisync.md
index 1d99acdbb..df88cf87e 100644
--- a/docs/content/bisync.md
+++ b/docs/content/bisync.md
@@ -146,9 +146,9 @@ The base directories on the both Path1 and Path2 filesystems must exist
 or bisync will fail. This is required for safety - that bisync can verify
 that both paths are valid.
 
-When using `--resync` a newer version of a file on the Path2 filesystem
-will be overwritten by the Path1 filesystem version.
-Carefully evaluate deltas using [--dry-run](/flags/#non-backend-flags).
+When using `--resync`, a newer version of a file either on Path1 or Path2
+filesystem, will overwrite the file on the other path (only the last version
+will be kept). Carefully evaluate deltas using [--dry-run](/flags/#non-backend-flags).
 
 For a resync run, one of the paths may be empty (no files in the path tree).
 The resync run should result in files on both paths, else a normal non-resync