Updated CHANGELOG

Author: connelly38

CHANGELOG.md

@@ -6,17 +6,17 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
 ## Unpublished
 
 ### Added
-- Rate Limiting:
-  - New RateLimiter interface and SimpleRateLimiter implementation.
-  - Cloud only: new RateLimiterConfig that can be set on NoSQLHandleConfig to enable automatic internal rate limiting based on table read and write throughput limits.
+- Rate Limiting (cloud only):
+  - Cloud only: new method NoSQLHandleConfig.setRateLimitingEnabled() to enable automatic internal rate limiting based on table read and write throughput limits.
   - If rate limiting is enabled:
-    - QueryRequest and PrepareRequest now require a table name (via setTableName())
+    - NoSQLHandleConfig.setDefaultRateLimitingPercentage() can control how much of a table's full limits this client handle can consume (default = 100%).
     - Result classes now have a getRateLimitDelayedMs() method to return the amount of time an operation was delayed due to internal rate limiting.
+  - Alternately, rate limiters can be supplied on a per-request basis.
   - For more information, see RateLimitingExample.java and the java docs for RateLimiterConfig.
 - RetryStats: New object allows the application to see how much time and for what reasons an operation was internally retried.
   - For successful operations, retry stats can be retrieved using Result.getRetryStats().
   - Otherwise, the original Request may have retry stats available via Request.getRetryStats() (for example, after an exception was thrown).
-- Cloud only. New regions: ap-chiyoda-1, me-dubai-1, uk-cardiff-1 and sa-santiago-1
+- Cloud only: New regions: ap-chiyoda-1, me-dubai-1, uk-cardiff-1 and sa-santiago-1
 
 ### Fixed
 - Ensure that TableLimits is always null in TableResult on-premise.