Fixed line wrapping

Charlie O'Keefe · Charlie O'Keefe · commit 787c8226ef29 · 2008-08-12T17:55:48.000-06:00
diff --git a/text/02_Git_Object_Db_Basics/0_ Git_Object_Db_Basics.markdown b/text/02_Git_Object_Db_Basics/0_ Git_Object_Db_Basics.markdown
@@ -48,4 +48,8 @@ on top of your machine's filesystem.
 ### Different from SVN ###
 
 It is important to note that this is very different from most SCM systems
-that you may be familiar with.  Subversion, CVS, Perforce, Mercurial and the like all use _Delta Storage_ systems - they store the differences between one commit and the next.  Git does not do this - it stores a snapshot of what all the files in your project look like in this tree structure each time you commit. This is a very important concept to understand when using Git.
+that you may be familiar with.  Subversion, CVS, Perforce, Mercurial and the
+like all use _Delta Storage_ systems - they store the differences between one
+commit and the next.  Git does not do this - it stores a snapshot of what all
+the files in your project look like in this tree structure each time you
+commit. This is a very important concept to understand when using Git.
diff --git a/text/02_Git_Object_Db_Basics/1_Trees_and_Blobs.markdown b/text/02_Git_Object_Db_Basics/1_Trees_and_Blobs.markdown
@@ -49,12 +49,13 @@ As you can see, a tree object contains a list of entries, each with a
 mode, object type, SHA1 name, and name, sorted by name.  It represents
 the contents of a single directory tree.
 
-An object referenced by a tree may be blob, representing the contents of a file, or another tree, representing the contents of a subdirectory.  Since trees and blobs, like all other objects, are named by the SHA1 hash of their
-contents, two trees have the same SHA1 name if and only if their
-contents (including, recursively, the contents of all subdirectories)
-are identical.  This allows git to quickly determine the differences
-between two related tree objects, since it can ignore any entries with
-identical object names.
+An object referenced by a tree may be blob, representing the contents of a
+file, or another tree, representing the contents of a subdirectory.  Since
+trees and blobs, like all other objects, are named by the SHA1 hash of their
+contents, two trees have the same SHA1 name if and only if their contents
+(including, recursively, the contents of all subdirectories) are identical.
+This allows git to quickly determine the differences between two related tree
+objects, since it can ignore any entries with identical object names.
 
 (Note: in the presence of submodules, trees may also have commits as
 entries.  See the **Submodules** section.)
diff --git a/text/02_Git_Object_Db_Basics/3_Trust_and_Tags.markdown b/text/02_Git_Object_Db_Basics/3_Trust_and_Tags.markdown
@@ -3,7 +3,10 @@
 
 [fig:object-tag]
 
-A tag object contains an object name (called simply 'object'), object type, tag name, the name of the person ("tagger") who created the tag, and a message, which may contain a signature, as can be seen using linkgit:git-cat-file[1]:
+A tag object contains an object name (called simply 'object'), object type,
+tag name, the name of the person ("tagger") who created the tag, and a
+message, which may contain a signature, as can be seen using
+linkgit:git-cat-file[1]:
 
     $ git cat-file tag v1.5.0
     object 437b1b20df4b356c9342dac8d38849f24ef44f27
diff --git a/text/02a_Git_Directory_and_Working_Directory/0_ Git_Directory_and_Working_Directory.markdown b/text/02a_Git_Directory_and_Working_Directory/0_ Git_Directory_and_Working_Directory.markdown
@@ -2,9 +2,14 @@
 
 ### The Git Directory ###
 
-The 'git directory' is the directory that stores all Git's history and meta information for your project - including all of the objects (commits, trees, blobs, tags), all of the pointers to where different branches are and more. 
-
-There is only one Git Directory per project (as opposed to one per subdirectory like with SVN or CVS), and that directory is (by default, though not necessarily) '.git' in the root of your project.  If you look at the contents of that directory, you can see all of your important files:
+The 'git directory' is the directory that stores all Git's history and meta
+information for your project - including all of the objects (commits, trees,
+blobs, tags), all of the pointers to where different branches are and more.
+
+There is only one Git Directory per project (as opposed to one per
+subdirectory like with SVN or CVS), and that directory is (by default, though
+not necessarily) '.git' in the root of your project.  If you look at the
+contents of that directory, you can see all of your important files:
 
     $>tree -L 1
     .
diff --git a/text/03_The_Git_Index/0_ The_Git_Index.markdown b/text/03_The_Git_Index/0_ The_Git_Index.markdown
@@ -2,14 +2,15 @@
 
 The Git index is used as a staging area between your working directory 
 and your repository.  You can use the index to build up a set of changes
-that you want to commit together.  When you create a commit, what is committed is what is currently in the index, not what is in your working
-directory.
+that you want to commit together.  When you create a commit, what is committed
+is what is currently in the index, not what is in your working directory.
 
 ### Looking at the Index ###
 
 The easiest way to see what is in the index is with the linkgit:git-status[1]
-command.  When you run git status, you can see which files are staged (currently in your index),
-which are modified but not yet staged, and which are completely untracked.
+command.  When you run git status, you can see which files are staged
+(currently in your index), which are modified but not yet staged, and which
+are completely untracked.
 
     $>git status
     # On branch master
