Merge pull request #228 from StevenRoddis/patch-1

Fixed display of exponents

Author: ben

book/07-git-tools/sections/revision-selection.asc

@@ -72,9 +72,9 @@ What then?
 If you do happen to commit an object that hashes to the same SHA-1 value as a previous object in your repository, Git will see the previous object already in your Git database and assume it was already written.
 If you try to check out that object again at some point, you’ll always get the data of the first object.
 
-However, you should be aware of how ridiculously unlikely this scenario is. The SHA-1 digest is 20 bytes or 160 bits. The number of randomly hashed objects needed to ensure a 50% probability of a single collision is about 2^80
-(the formula for determining collision probability is `p = (n(n-1)/2) * (1/2^160))`. 2^80
-is 1.2 x 10^24
+However, you should be aware of how ridiculously unlikely this scenario is. The SHA-1 digest is 20 bytes or 160 bits. The number of randomly hashed objects needed to ensure a 50% probability of a single collision is about 2^80^
+(the formula for determining collision probability is `p = (n(n-1)/2) * (1/2^160))`. 2^80^
+is 1.2 x 10^24^
 or 1 million billion billion. That’s 1,200 times the number of grains of sand on the earth.
 
 Here’s an example to give you an idea of what it would take to get a SHA-1 collision.