# [PATCH] Documentation: Fix a few i.e./e.g. mix-ups

1 messages from 2009-12-01 to 2009-12-01. Participants: Michael J Gruber.
Thread: https://gitlist.dev/t/21804

## Michael J Gruber, 2009-12-01 09:19

Subject: [PATCH] Documentation: Fix a few i.e./e.g. mix-ups
Message-ID: <81ffa57ff9292b0a85e812c14154a2291aa3c2f9.1259658926.git.git@drmicha.warpmail.net>
URL: https://gitlist.dev/e/81ffa57ff9292b0a85e812c14154a2291aa3c2f9.1259658926.git.git%40drmicha.warpmail.net

```
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>
---
 Documentation/git-bundle.txt       |    2 +-
 Documentation/gitcore-tutorial.txt |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index aee7e4a..c3a066e 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -24,7 +24,7 @@ ssh, rsync, http) cannot be used.  This command provides support for
 'git-fetch' and 'git-pull' to operate by packaging objects and references
 in an archive at the originating machine, then importing those into
 another repository using 'git-fetch' and 'git-pull'
-after moving the archive by some means (i.e., by sneakernet).  As no
+after moving the archive by some means (e.g., by sneakernet).  As no
 direct connection between the repositories exists, the user must specify a
 basis for the bundle that is held by the destination repository: the
 bundle assumes that all objects in the basis are already in the
diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index e237394..f762dca 100644
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -602,7 +602,7 @@ $ git tag -s <tagname>
 ----------------
 
 which will sign the current `HEAD` (but you can also give it another
-argument that specifies the thing to tag, i.e., you could have tagged the
+argument that specifies the thing to tag, e.g., you could have tagged the
 current `mybranch` point by using `git tag <tagname> mybranch`).
 
 You normally only do signed tags for major releases or things
-- 
1.6.6.rc0.274.g71380

```
