Update tap16.md

Co-authored-by: Joshua Lock <[email protected]>

tap16.md

@@ -84,7 +84,7 @@ information for all targets metadata files into a single file, it instead uses t
 information to generate a Merkle tree.  Each targets metadata file's version information forms
 a leaf of the tree, then these leaves are used to build a Merkle tree. The
 internal nodes of a Merkle tree contain the hash of their child nodes. The exact
-algorithm for generating this Merkle tree (ie the order of nodes in the hash,
+algorithm for generating this Merkle tree (i.e. the order of nodes in the hash,
 how version information is encoded, etc.), is left to the implementer, but this
 algorithm should be documented in a [POUF](https://github.com/theupdateframework/taps/blob/master/tap11.md)
 so that implementations can be