diff --git a/README.md b/README.md
index 69c3bd5ae77f2a3ae9851827e9026ac34fd1c060..da22daedb6f2b9368df58678608dd09eb5b6eb90 100644
--- a/README.md
+++ b/README.md
@@ -181,6 +181,8 @@ while (n < 5000) {
 js.do_callbacks = true;
 ```
 
+*(You can put `js.do_callbacks = true;` anywhere, but I prefer it at the end of the script as a matter of form.)*
+
 ##### Handlers vs. Callbacks
 
 Serveral `*Device` methods accept a `responseHandler` parameter, which is a `packetHandler` function that accepts a single `MeshPacket` as a parameter. The `responseHandler` is typically optional, but if supplied it will be called when a packet is received in response to this message.
diff --git a/readme.md b/readme.md
index 6d9eb47135f3a5c92beb17e0a607027c1a10e741..1b5cfd42a9db4ae366f3a0df5278c47347552873 100644
--- a/readme.md
+++ b/readme.md
@@ -153,6 +153,8 @@ while (n < 5000) {
 js.do_callbacks = true;
 ```
 
+*(You can put `js.do_callbacks = true;` anywhere, but I prefer it at the end of the script as a matter of form.)*
+
 #### Handlers vs. Callbacks
 
 Serveral `*Device` methods accept a `responseHandler` parameter, which is a `packetHandler` function that accepts a single `MeshPacket` as a parameter. The `responseHandler` is typically optional, but if supplied it will be called when a packet is received in response to this message.