Documentation: Fix a few i.e./e.g. mix-ups

A git bundle can be transported by several means (such as e-mail), not only by snekaernet, so use e.g. instead of i.e. The mix-up in git-bundle.txt is obvious. Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Michael J Gruber committed Dec 1, 2009 at 10:19 UTC 3c652d16713c27d0abb2003d83a237f7d47ef569

2 files changed +2 -2

Documentation/git-bundle.txt

+1 -1

@@ -24,7 +24,7 @@ ssh, rsync, http) cannot be used. This command provides support for

24 'git-fetch' and 'git-pull' to operate by packaging objects and references

25 in an archive at the originating machine, then importing those into

26 another repository using 'git-fetch' and 'git-pull'

27 -after moving the archive by some means (i.e., by sneakernet). As no

27 +after moving the archive by some means (e.g., by sneakernet). As no

28 direct connection between the repositories exists, the user must specify a

29 basis for the bundle that is held by the destination repository: the

30 bundle assumes that all objects in the basis are already in the

Documentation/gitcore-tutorial.txt

+1 -1

@@ -602,7 +602,7 @@ $ git tag -s <tagname>

602 ----------------

603

604 which will sign the current `HEAD` (but you can also give it another

605 -argument that specifies the thing to tag, i.e., you could have tagged the

605 +argument that specifies the thing to tag, e.g., you could have tagged the

606 current `mybranch` point by using `git tag <tagname> mybranch`).

607

608 You normally only do signed tags for major releases or things