Fix: Authors and spelling merklize

Author: moonsettler

README.mediawiki

@@ -1299,7 +1299,7 @@ Those proposing changes should consider that ultimately consent may rest with th
 | [[bip-0442.md|442]]
 | Consensus (soft fork)
 | OP_PAIRCOMMIT
-| moonsettler
+| moonsettler, Brandon Black
 | Standard
 | Draft
 |}

bip-0442.md

@@ -149,7 +149,7 @@ Lightning Symmetry channel construction is close to [optimal].
 
 ### In MATT
 
-The Merkelize All The Things ([MATT]) framework proposes to use `OP_CAT` to
+The Merklize All The Things ([MATT]) framework proposes to use `OP_CAT` to
 combine multiple items into a single commitment for use with
 `OP_CHECKCONTRACTVERIFY`. `OP_PAIRCOMMIT` provides a more ergonomic way to
 accomplish this[^4].
@@ -261,11 +261,11 @@ can be reached by all possible input values (i.e. the input entropy space) as
 they must be enumerated and hashed into a Merkle root.
 
 Taproot trees can be 128 levels deep, therefore including up to 2^128 possible
-output values. This is over the practical limits to enumerate and merkelize.
+output values. This is over the practical limits to enumerate and merklize.
 Therefore, we conclude that enabling Merkle commitments in script does not
 materially extend what computations are possible to validate in bitcoin
 script. While `OP_PAIRCOMMIT` is not explicitly limited to a height of 128, greater
-heights are not practical to Merkelize.
+heights are not practical to Merklize.
 
 ## Backward Compatibility