diff --git a/CHANGES b/CHANGES
index 8ee3c16f8e..19976358be 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,8 @@
 
+3.3.0-dev.390 | 2020-10-12 17:43:15 -0700
+
+  * Improve documentation for zeek_init event scheduling pitfalls (Jon Siwek, Corelight)
+
 3.3.0-dev.388 | 2020-10-12 17:02:20 -0700
 
   * Add CaptureLoss::Too_Little_Traffic notice (Vlad Grigorescu)
diff --git a/VERSION b/VERSION
index 85691726f1..ea0e8675c9 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-3.3.0-dev.388
+3.3.0-dev.390
diff --git a/doc b/doc
index ddec4e6750..4f37431a11 160000
--- a/doc
+++ b/doc
@@ -1 +1 @@
-Subproject commit ddec4e675013eff12746064fa4b6b723e86b5804
+Subproject commit 4f37431a116bd8951c5a63bb4d1e3ffb065152f4
diff --git a/src/event.bif b/src/event.bif
index 362cfa42ff..4271d01ca2 100644
--- a/src/event.bif
+++ b/src/event.bif
@@ -41,10 +41,10 @@
 ##
 ##    When a ``zeek_init`` handler executes, Zeek has not yet seen any input
 ##    packets and therefore :zeek:id:`network_time` is not initialized yet. An
-##    artifact of that is that any timer installed in a ``zeek_init`` handler
-##    will fire immediately with the first packet. The standard way to work
-##    around that is to ignore the first time the timer fires and immediately
-##    reschedule.
+##    artifact of that is that any timer installed in a ``zeek_init`` handler,
+##    like with :zeek:keyword:`schedule`, will fire immediately with the first
+##    packet. The standard way to work around that is to ignore the first time
+##    the timer fires and immediately reschedule.
 ##
 event zeek_init%(%);