From e7ee7d60edf482180efdc9d5eaead5284c3a2ff5 Mon Sep 17 00:00:00 2001
From: Shannon Appelcline <shannona@skotos.net>
Date: Fri, 26 May 2017 13:51:37 -0700
Subject: [PATCH] Update 9_2_Using_CLTV_in_Scripts.md

---
 9_2_Using_CLTV_in_Scripts.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/9_2_Using_CLTV_in_Scripts.md b/9_2_Using_CLTV_in_Scripts.md
index b3f2bc6..0d380f8 100644
--- a/9_2_Using_CLTV_in_Scripts.md
+++ b/9_2_Using_CLTV_in_Scripts.md
@@ -31,22 +31,22 @@ This is how a `OP_CHECKLOCKTIMEVERIFY` might be used to check against May 24, 20
 ```
 But we'll usually depict this in an abstraction like this:
 ```
-<May24> OP_CHECKLOCKTIME VERIFY
+<May24> OP_CHECKLOCKTIMEVERIFY
 ```
 Or this:
 ```
-<AbsoluteTime> OP_CHECKLOCKTIME VERIFY
+<AbsoluteTime> OP_CHECKLOCKTIMEVERIFY
 ```
 
 ### Understand a CLTV Absolute Block Height
 
 This is how `OPCHECKLOCKTIMEVERIFY` might be used to check against a blockheight that was reached on May 24, 2017:
 ```
-467951 OP_CHECKLOCKTIME VERIFY
+467951 OP_CHECKLOCKTIMEVERIFY
 ```
 But we'll usually abtract it like this:
 ```
-<AbsoluteBlockHeight> OP_CHECKLOCKTIME VERIFY
+<AbsoluteBlockHeight> OP_CHECKLOCKTIMEVERIFY
 ```
 
 ### Understand How CLTV Really Works