Minor tweaks (syntax, rewording) of "Packfiles" section

Author: robertpjday

book/10-git-internals/sections/packfiles.asc

@@ -1,7 +1,6 @@
 === Packfiles
 
-Let's go back to the object database for your test Git repository.
-At this point, you have 11 objects – 4 blobs, 3 trees, 3 commits, and 1 tag:
+If you followed all of the instructions in the example from the previous section, you should now have a test Git repository with 11 objects -- four blobs, three trees, three commits, and one tag:
 
 [source,console]
 ----
@@ -20,8 +19,8 @@ $ find .git/objects -type f
 ----
 
 Git compresses the contents of these files with zlib, and you're not storing much, so all these files collectively take up only 925 bytes.
-You'll add some larger content to the repository to demonstrate an interesting feature of Git.
-To demonstrate, we'll add the `repo.rb` file from the Grit library – this is about a 22K source code file:
+Now you'll add some more sizable content to the repository to demonstrate an interesting feature of Git.
+To demonstrate, we'll add the `repo.rb` file from the Grit library -- this is about a 22K source code file:
 
 [source,console]
 ----
@@ -36,7 +35,7 @@ $ git commit -m 'added repo.rb'
  rewrite test.txt (100%)
 ----
 
-If you look at the resulting tree, you can see the SHA-1 value your `repo.rb` file got for the blob object:
+If you look at the resulting tree, you can see the SHA-1 value that was calculated for your new `repo.rb` blob object:
 
 [source,console]
 ----
@@ -46,15 +45,15 @@ $ git cat-file -p master^{tree}
 100644 blob e3f094f522629ae358806b17daf78246c27c007b      test.txt
 ----
 
-You can then use `git cat-file` to see how big that object is:
+You can then use `git cat-file` to see how large that object is:
 
 [source,console]
 ----
 $ git cat-file -s 033b4468fa6b2a9547a70d88d1bbe8bf3f9ed0d5
 22044
 ----
 
-Now, modify that file a little, and see what happens:
+At this point, modify that file a little, and see what happens:
 
 [source,console]
 ----
@@ -64,7 +63,7 @@ $ git commit -am 'modified repo a bit'
  1 file changed, 1 insertion(+)
 ----
 
-Check the tree created by that commit, and you see something interesting:
+Check the tree created by that last commit, and you see something interesting:
 
 [source,console]
 ----
@@ -113,7 +112,7 @@ $ find .git/objects -type f
 .git/objects/pack/pack-978e03944f5c581011e6998cd0e9e30000905586.pack
 ----
 
-The objects that remain are the blobs that aren't pointed to by any commit – in this case, the ``what is up, doc?'' example and the ``test content'' example blobs you created earlier.
+The objects that remain are the blobs that aren't pointed to by any commit -- in this case, the ``what is up, doc?'' example and the ``test content'' example blobs you created earlier.
 Because you never added them to any commits, they're considered dangling and aren't packed up in your new packfile.
 
 The other files are your new packfile and an index.
@@ -158,7 +157,7 @@ chain length = 1: 3 objects
 
 Here, the `033b4` blob, which if you remember was the first version of your `repo.rb` file, is referencing the `b042a` blob, which was the second version of the file.
 The third column in the output is the size of the object in the pack, so you can see that `b042a` takes up 22K of the file, but that `033b4` only takes up 9 bytes.
-What is also interesting is that the second version of the file is the one that is stored intact, whereas the original version is stored as a delta – this is because you're most likely to need faster access to the most recent version of the file.
+What is also interesting is that the second version of the file is the one that is stored intact, whereas the original version is stored as a delta -- this is because you're most likely to need faster access to the most recent version of the file.
 
 The really nice thing about this is that it can be repacked at any time.
 Git will occasionally repack your database automatically, always trying to save more space, but you can also manually repack at any time by running `git gc` by hand.