From 0eeea9d2911c654397c4fa627216fecce0f28535 Mon Sep 17 00:00:00 2001
From: Shannon Appelcline <shannona@skotos.net>
Date: Wed, 24 May 2017 14:32:03 -0700
Subject: [PATCH] Update 9_2_Using_CLTV_in_Scripts.md

---
 9_2_Using_CLTV_in_Scripts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/9_2_Using_CLTV_in_Scripts.md b/9_2_Using_CLTV_in_Scripts.md
index 333a3d3..c0f9dfa 100644
--- a/9_2_Using_CLTV_in_Scripts.md
+++ b/9_2_Using_CLTV_in_Scripts.md
@@ -4,7 +4,7 @@
 
 `OP_CHECKLOCKTIMEVERIFY` (or CLTV) is the natural complement to `nLockTime`. It moves the idea of locking transactions by an absolute time or blockheight into the realm of opcodes, allowing for the locking of individual UTXOs.
 
-### Remember nLockTime
+## Remember nLockTime
 
 Before digging into CLTV, we should first recall how `nLockTime` works.