diff --git a/howto/ldap.md b/howto/ldap.md
index 0db628c4539755964fa0018c3cd41c773e9af6e7..34d05d85dfdf48a834dea5443e1256bfc81a5338 100644
--- a/howto/ldap.md
+++ b/howto/ldap.md
@@ -34,6 +34,14 @@ The email forward can also be changed in the [web interface][db.torproject.org].
 
 # How-to
 
+## Know when will my change take effect?
+
+Once a change is saved to LDAP, the actual change will take at least 5
+minutes and at most 15 minutes to propagate to the relevant host. See
+the [configuration file distribution
+section](#configuration-file-distribution) for more details on why it
+is so.
+
 ## Locking an account
 
 See [the user retirement procedures](retire-a-user).
@@ -508,11 +516,14 @@ This diagram covers those inter-dependencies at the time of writing.
 
 ### Configuration file distribution
 
-An important part of `ud-ldap` is the `ud-generate`  command, which
+An important part of `ud-ldap` is the `ud-generate` command, which
 generates configuration files for each host. Then the `ud-replicate`
 command runs on each node to `rsync` those files. Both commands are
-ran from cron on regular intervals, the latter defined in Puppet, the
-former hard-coded to 15 minutes.
+ran from cron on regular intervals. `ud-replicate` is configured by
+the `userdir-ldap` package, at every 5 mintues. `ud-generate` is also
+configured to run every 5 minutes, starting on the third minute of
+every hour, in `/etc/cron.d/local-ud-generate` (so at minute 3, 8, 13,
+..., 53, 58).
 
 More specifically, this is what happens: