Added BatchLoaderScheduler into the mix- doco update

Author: bbakerman

README.md

@@ -512,7 +512,7 @@ in the load request queue will never be batched, and thus _will never complete_!
 
 ## The BatchLoader Scheduler
 
-By default, when `dataLoader.dispatch()` is called the `BatchLoader` / `MappedBatchLoader` function will be invoked
+By default, when `dataLoader.dispatch()` is called, the `BatchLoader` / `MappedBatchLoader` function will be invoked
 immediately.  
 
 However, you can provide your own `BatchLoaderScheduler` that allows this call to be done some time into
@@ -553,6 +553,8 @@ each batch of keys.
 
 Do not assume that a single call to `dispatch()` results in a single call to `BatchLoaderScheduler`.
 
+This code is inspired from the scheduling code in the [reference JS implementation](https://github.com/graphql/dataloader#batch-scheduling)
+
 ## Scheduled Registry Dispatching
 
 `ScheduledDataLoaderRegistry` is a registry that allows for dispatching to be done on a schedule. It contains a

src/main/java/org/dataloader/scheduler/BatchLoaderScheduler.java

@@ -11,7 +11,7 @@
 import java.util.concurrent.CompletionStage;
 
 /**
- * By default, when  {@link DataLoader#dispatch()} is called the {@link BatchLoader} / {@link MappedBatchLoader} function will be invoked
+ * By default, when  {@link DataLoader#dispatch()} is called, the {@link BatchLoader} / {@link MappedBatchLoader} function will be invoked
  * immediately.  However, you can provide your own {@link BatchLoaderScheduler} that allows this call to be done some time into
  * the future.  You will be passed a callback ({@link ScheduledBatchLoaderCall} / {@link ScheduledMappedBatchLoaderCall} and you are expected
  * to eventually call this callback method to make the batch loading happen.