diff --git a/docs/operational-procedures/rde-deposits.md b/docs/operational-procedures/rde-deposits.md
index b31f82463..5e2d43662 100644
--- a/docs/operational-procedures/rde-deposits.md
+++ b/docs/operational-procedures/rde-deposits.md
@@ -119,7 +119,7 @@ manually by visiting the following URL:
     https://backend-dot-{PROJECT-ID}.appspot.com/_dr/task/rdeStaging
 
 That will spawn a staging task for each TLD under the backend module in that App
-Engine project.
+Engine project. You can also run the task from the cron tab of the GAE console.
 
 ## Notification of upload problems
 
@@ -185,8 +185,12 @@ ICANN.
 
 ## Generating RDE files
 
-You can use the `nomulus` command to generate the RDE files on a per-TLD basis.
-Here's an example:
+In general RDE files should be regenerated by updating the cursors to before the
+desired date and then re-running the mapreduce (either by waiting until the next
+scheduled cron execution, or by manually invoking the RDE staging action).
+
+In very rare cases (and only for small TLDs) you can use `nomulus` to generate
+the RDE files on a per-TLD basis. Here's an example:
 
 ```shell
 # Define the tld/date combination.
@@ -245,7 +249,7 @@ $ gsutil cp ${tld}_${date}_full_S1_R0{,-report}.xml.ghostryde gs://{PROJECT-ID}-
 
 If the rdeStaging or rdeUpload tasks are failing and you find yourself needing
 to perform this process manually, you must make sure to update the appropriate
-cursors. Again, you can use the `nomulus` to perform this operation.
+cursors. Again, you can use `nomulus` to perform this operation.
 
 ```shell
 $ nomulus -e production update_cursors --timestamp=2015-05-21T00:00:00Z --type=RDE_STAGING $tld