send to -> sent to

Author: Matt Carroll

packages/optimizely-sdk/CHANGELOG.MD

@@ -12,7 +12,7 @@ Changes that have landed but are not yet released.
 ### New Features
 
 - Added support for event batching via the event processor.
-  - Events generated by methods like `activate`, `track`, and `isFeatureEnabled` will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be combined into a request and send to the event dispatcher.
+  - Events generated by methods like `activate`, `track`, and `isFeatureEnabled` will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be combined into a request and sent to the event dispatcher.
   - To configure event batching, include the `eventBatchSize` and `eventFlushInterval` number properties in the object you pass to `createInstance`.
   - Event batching is enabled by default. `eventBatchSize` defaults to `10`. `eventFlushInterval` defaults to `30000` in Node and `1000` in browsers.
 - Added `localStorage` mitigation against lost events in the browser