Merge pull request #413 from xifedI/patch-1

transfer-protocols.asc: Update the git-receive-pack response explanation

Author: ben

book/10-git-internals/sections/transfer-protocols.asc

@@ -154,8 +154,7 @@ The `git-receive-pack` command immediately responds with one line for each refer
 The first line also has a list of the server's capabilities (here, `report-status`, `delete-refs`, and some others, including the client identifier).
 
 Each line starts with a 4-character hex value specifying how long the rest of the line is.
-Your first line starts with 005b, which is hexadecimal for 91, meaning that 91 bytes remain on that line.
-The next line starts with 003e, which is 62, so you read the remaining 62 bytes.
+Your first line starts with 00a5, which is hexadecimal for 165, meaning that 165 bytes remain on that line.
 The next line is 0000, meaning the server is done with its references listing.
 
 Now that it knows the server's state, your `send-pack` process determines what commits it has that the server doesn't.