diff --git a/examples/docs/ex_14_Wait_For_NDEF_Write.md b/examples/docs/ex_14_Wait_For_NDEF_Write.md
index 02fff14..bf17d65 100644
--- a/examples/docs/ex_14_Wait_For_NDEF_Write.md
+++ b/examples/docs/ex_14_Wait_For_NDEF_Write.md
@@ -83,8 +83,8 @@ This prevents _most_ App confusion. You may still see occasions where the App th
 a new RF transaction is attempted while the tag is already performing an I2C transaction (memory read). Once the RF read-modify-write is underway, the two second
 timer prevents the next I2C transaction from interfering with it.
 
-**It also helps a lot if you bring your phone near the tag first _and then_ press the "Write to Tag" button.** Bringing your phone near the tag generates a field.
-The code then goes into its two second timeout and isn't accessing I2C when the RF write starts.
+**It also helps a lot if you bring your phone near the tag first _and then_ press the "Write to Tag" button.** Bringing your phone near the tag generates a field
+which causes the tag to go into RF mode early. This locks out I2C, ahead of you pushing the button to start the actual RF write.
 
 ## Writing an Empty NDEF Record