From a76cdcef8b595c0ac772916bade500b0f74bd33d Mon Sep 17 00:00:00 2001
From: Alex Reisner <alex@alexreisner.com>
Date: Mon, 14 Apr 2014 23:50:56 -0400
Subject: [PATCH] Clean up language.

---
 README.md | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 297276aa..06f4efeb 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
 
-- 
GitLab