Update objects.asc

Author: jingsam

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

@@ -381,12 +381,13 @@ You can calculate the SHA-1 value of a string in Ruby by including the SHA1 dige
 => "bd9dbf5aae1a3862dd1526723246b20206e5fc37"
 ----
 
-Let's validate the hash with `git hash-object`. It shows that they are identical. Note that `echo` will add a trailing newline character in string, which is not we want in this case. `echo -n` can prevent from adding a trailing newline character.
+Let's compare that to the output of `git hash-object`.
+Here we use `echo -n` to prevent adding a newline to the input.
 
 [source,console]
 ----
->> $ echo -n "what is up, doc?" | git hash-object --stdin
-=> bd9dbf5aae1a3862dd1526723246b20206e5fc37
+$ echo -n "what is up, doc?" | git hash-object --stdin
+bd9dbf5aae1a3862dd1526723246b20206e5fc37
 ----
 
 Git compresses the new content with zlib, which you can do in Ruby with the zlib library.
@@ -417,6 +418,15 @@ Then, open the file with `File.open()` and write out the previously zlib-compres
 => 32
 ----
 
+Let's check the content of the object using `git cat-file`:
+
+[source,console]
+---
+$ git cat-file -p bd9dbf5aae1a3862dd1526723246b20206e5fc37
+what is up, doc?
+---
+
 That's it – you've created a valid Git blob object.
+
 All Git objects are stored the same way, just with different types – instead of the string blob, the header will begin with commit or tree.
 Also, although the blob content can be nearly anything, the commit and tree content are very specifically formatted.