From e9ea4265c22b19c19659710874a2f8a61fddb13c Mon Sep 17 00:00:00 2001
From: Shannon Appelcline <shannon.appelcline@gmail.com>
Date: Tue, 20 Oct 2020 08:32:31 -1000
Subject: [PATCH] removed warning

---
 11_2_Using_CLTV_in_Scripts.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/11_2_Using_CLTV_in_Scripts.md b/11_2_Using_CLTV_in_Scripts.md
index 4ba2886..1d934d6 100644
--- a/11_2_Using_CLTV_in_Scripts.md
+++ b/11_2_Using_CLTV_in_Scripts.md
@@ -1,7 +1,5 @@
 # 11.2: Using CLTV in Scripts
 
-> :information_source: **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
-
 `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.
 
 > :warning: **VERSION WARNING:** CLTV became available with Bitcoin Core 0.11.2, but should be fairly widely deployed at this time.