aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMirek Kratochvil <exa.exa@gmail.com>2025-09-05 22:00:29 +0200
committerMirek Kratochvil <exa.exa@gmail.com>2025-09-05 22:00:29 +0200
commit6cdd70feafe7b8047c38ac1e4f5d6fa9ffe97f28 (patch)
treebab7b6c3d99f22cfa479509837d8d76016a1b968
parent50a3d08aa82a07894147b77278de57e8db15f736 (diff)
downloadwerge-6cdd70feafe7b8047c38ac1e4f5d6fa9ffe97f28.tar.gz
werge-6cdd70feafe7b8047c38ac1e4f5d6fa9ffe97f28.tar.bz2
wording
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 10273a5..27fec8b 100644
--- a/README.md
+++ b/README.md
@@ -207,8 +207,8 @@ and `git mergetool -t werge`:
```
One issue with `git` mergetools is that they are supposed to be interactive,
-and thus `git` assumes them to always produce a completely merged, conflictless
-result. In turn, the auto-merging with `git mergetool -t werge` fails with
+and thus `git` expects them to always produce a completely merged, conflictless
+result. In turn, if the auto-merging with `git mergetool -t werge` fails with
conflicts, `git` assumes a complete failure and restores the original version
from the backup. To enable a more useful behavior, use `werge` as a merge
driver (see below).