patch, 2 partsdocs: explain behaviour of remote add without tag option

diff --git a/Documentation/config.txt b/Documentation/config.txt
index 440784c..394042a 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -2241,8 +2241,9 @@ remote.<name>.tagopt::
 	Setting this value to \--no-tags disables automatic tag following when
 	fetching from remote <name>. Setting it to \--tags will fetch every
 	tag from remote <name>, even if they are not reachable from remote
-	branch heads. Passing these flags directly to linkgit:git-fetch[1] can
-	override this setting. See options \--tags and \--no-tags of
+	branch heads. When not set, fetches only tags reachable by the
+	downloaded refs. Passing these flags directly to linkgit:git-fetch[1]
+	can override this setting. See options \--tags and \--no-tags of
 	linkgit:git-fetch[1].
 
 remote.<name>.vcs::

diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index a77607b..5bde0e1 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -58,6 +58,9 @@ remote repository.
 With `--no-tags` option, `git fetch <name>` does not import tags from
 the remote repository.
 +
+With neither `--tags` or `--no-tags` set, imports only tags that are
+reachable from downloaded history.
++
 With `-t <branch>` option, instead of the default glob
 refspec for the remote to track all branches under
 the `refs/remotes/<name>/` namespace, a refspec to track only `<branch>`