diff --git a/blocks/form-captcha/README.md b/blocks/form-captcha/README.md
index d89913707..82f319092 100644
--- a/blocks/form-captcha/README.md
+++ b/blocks/form-captcha/README.md
@@ -11,13 +11,13 @@ Display a captcha form element, conditionally.
 ## Description
 
 This captcha is powered by Cloudflare's Turnstile. It is a simple captcha that can be used to protect block applications from bots and spam.
-It is conditionally displayed when it's parent and target namespace have a context.captchaHidden value of false, by default most applications will have this set to true.
+It is conditionally displayed when it's parent and target namespace have a `context.captchaHidden` value of `false`, by default most applications will have this set to `true`.
 
 Upon successful completion of the captcha, the challenge token will be returned back to the targetnamespace at `context.captchaToken` which you should further validate in your rest request. See `\PRC\Platform\Mailchimp->verify_captcha()` for an example of how to validate the captcha token.
 
 ## Instructions
 
-Drop block in block application, set the targetnamespace attribute in the PRC Interactiity API panel. This will be the namespace of the parent block that will control the captcha visibility. It is incumbent upon the parent block to handle toggling the block on|off and further validation of the returned challenge token.
+op block in block application, set the targetnamespace attribute in the PRC Interactiity API panel. This will be the namespace of the parent block that will control the captcha visibility. **It is incumbent upon the parent block to handle toggling the block on|off and further validation of the returned challenge token.**
 
 ## Frequently Asked Questions
 
@@ -25,9 +25,6 @@ Drop block in block application, set the targetnamespace attribute in the PRC In
 
 An answer to that question.
 
-### What about foo bar?
-
-Answer to foo bar dilemma.
 
 ## Screenshots
 
@@ -41,7 +38,3 @@ Answer to foo bar dilemma.
 * Release
 
 ## Developer Notes
-
-You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
-blocks where more information needs to be conveyed that doesn't fit into the categories of "description" or
-"installation." Arbitrary sections will be shown below the built-in sections outlined above.
diff --git a/includes/print-engine/class-print-engine.php b/includes/print-engine/class-print-engine.php
index 96de2a6a0..44c9826c5 100644
--- a/includes/print-engine/class-print-engine.php
+++ b/includes/print-engine/class-print-engine.php
@@ -150,6 +150,7 @@ public function render( $block_content, $block ) {
 		$w = new WP_HTML_Tag_Processor( $block_content );
 		if ( $w->next_tag() ) {
 			if ( $hide_on_print ) {
+				// @TODO: Check for a query var and render the "print view" using /iframe support and exclude the hide on print blocks explicilty from the markup... but do that later.
 				$w->set_attribute( 'data-hide-on-print', 'true' );
 			}
 			if ( $display_on_print ) {