Documentation: recursive is the default strategy these days.

We still said resolve was the default in handful places.

Signed-off-by: Junio C Hamano <junkio@cox.net>

1 files changed, 5 insertions, 5 deletions

diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt
index 3ec56d22e..7df0266ba 100644
--- a/Documentation/merge-strategies.txt
+++ b/Documentation/merge-strategies.txt
@@ -6,27 +6,27 @@ resolve::
 	and another branch you pulled from) using 3-way merge
 	algorithm.  It tries to carefully detect criss-cross
 	merge ambiguities and is considered generally safe and
-	fast.  This is the default merge strategy when pulling
-	one branch.
+	fast.
 
 recursive::
 	This can only resolve two heads using 3-way merge
 	algorithm.  When there are more than one common
 	ancestors that can be used for 3-way merge, it creates a
-	merged tree of the common ancestores and uses that as
+	merged tree of the common ancestors and uses that as
 	the reference tree for the 3-way merge.  This has been
 	reported to result in fewer merge conflicts without
 	causing mis-merges by tests done on actual merge commits
 	taken from Linux 2.6 kernel development history.
 	Additionally this can detect and handle merges involving
-	renames.
+	renames.  This is the default merge strategy when
+	pulling or merging one branch.
 
 octopus::
 	This resolves more than two-head case, but refuses to do
 	complex merge that needs manual resolution.  It is
 	primarily meant to be used for bundling topic branch
 	heads together.  This is the default merge strategy when
-	pulling more than one branch.
+	pulling or merging more than one branches.
 
 ours::
 	This resolves any number of heads, but the result of the