diff --git a/bip-hashrate-escrows.mediawiki b/bip-hashrate-escrows.mediawiki
index 82c436cb..0987bf5c 100644
--- a/bip-hashrate-escrows.mediawiki
+++ b/bip-hashrate-escrows.mediawiki
@@ -315,7 +315,7 @@ In fact, M4 can also be *nothing*. In other words, it may be optional. This is p
 
 The following sections assume a maximum of one sucessful withdrawal per sidechain at a time. In other words, as WT^s are proposed, only one can make progress toward the finish line. As a result, a given side-to-main transfer will always take between 3 and 6 months. If there were more simulataneous withdrawals, the worst-case transfer duration would improve.
 
-<img src="bip-hasrate-escrows/two-groups.png?raw=true" align="middle"></img>
+<img src="bip-hashrate-escrows/two-groups.png?raw=true" align="middle"></img>
 
 The worst-case withdrawal time obeys f(n)=3+(3/n) months, where n is the number of simultaneous withdrawals.
 
@@ -453,12 +453,12 @@ As a soft fork, older software will continue to operate without modification. No
 
 This BIP will be deployed by "version bits" BIP9 with the name "hrescrow" and using bit 4.
 
-```
+<pre>
 // Deployment of Drivechains (BIPX, BIPY)
 consensus.vDeployments[Consensus::DEPLOYMENT_DRIVECHAINS].bit = 4;
 consensus.vDeployments[Consensus::DEPLOYMENT_DRIVECHAINS].nStartTime = 1515974401; // January 15th, 2018.
 consensus.vDeployments[Consensus::DEPLOYMENT_DRIVECHAINS].nTimeout = 1547510401; // January 15th, 2019.
-```
+</pre>
 
 ==Reference Implementation==