diff --git a/07_2_Using_a_Partially_Signed_Bitcoin_Transaction.md b/07_2_Using_a_Partially_Signed_Bitcoin_Transaction.md
index 586ad53..1f2d100 100644
--- a/07_2_Using_a_Partially_Signed_Bitcoin_Transaction.md
+++ b/07_2_Using_a_Partially_Signed_Bitcoin_Transaction.md
@@ -1,6 +1,6 @@
 # 7.2: Using a Partially Signed Bitcoin Transaction
 
-> :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.
+> :information_source: **NOTE:** This section has been recently added to the course and is an early draft that may still be awaiting review. Caveat reader.
 
 Now that you've learned the basic workflow of generating a PSBT, you probably want to do something with it. What can PSBTs do that multi-sigs (and normal raw transactions) can't? To start with, you've got the ease of use of a standardized format, which means that you can use your `bitcoin-cli` transactions and meld them with transactions generated by people (or programs) on other platforms. Beyond that, you can do some things that just weren't easy using other mechanics.