diff --git a/README.md b/README.md
index 297276aaf022b23e15f1a7d5d83ec50442ab5962..06f4efeb73b44dc46abc6fef9836c8f6354f874e 100644
--- a/README.md
+++ b/README.md
@@ -98,14 +98,9 @@ If you have just added geocoding to an existing application with a lot of object
 
     rake geocode:all CLASS=YourModel
 
-Geocoder will print warnings if you exceed the rate limit for your geocoding service. Some services — Google notably — enforce a per-second limit in addition to a per-day limit. To avoid exceeding the per-second limit, you can add a `sleep` option to the rake task, like so:
-
-    rake geocode:all CLASS=YourModel sleep=0.25
-
-Batch processing.If your database is large, you can handle batches:
-
-    rake geocode:all CLASS=YourModel sleep=0.25 batch=100
+Geocoder will print warnings if you exceed the rate limit for your geocoding service. Some services — Google notably — enforce a per-second limit in addition to a per-day limit. To avoid exceeding the per-second limit, you can add a `SLEEP` option to pause between requests for a given amount of time. You can also load objects in batches to save memory, for example:
 
+    rake geocode:all CLASS=YourModel SLEEP=0.25 BATCH=100
 
 ### Avoiding Unnecessary API Requests