docs

README.md

@@ -97,11 +97,17 @@ With aggressive location-monitoring enabled, if the user stops for exactly 15 mi
 
 Use the following config-parameters with the #configure method:
 
-  `@param {Integer} [0, 10, 100, 1000] desiredAccuracy in meters`
+  `@param {Integer} [0, 10, 100, 1000] [desiredAccuracy](https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocationManager_Class/CLLocationManager/CLLocationManager.html#//apple_ref/occ/instp/CLLocationManager/desiredAccuracy) in meters`
 
 The lower the number, the more power devoted to GeoLocation resulting in higher accuracy readings.  1000 results in lowest power drain and least accurate readings.
 
-  `@param {Integer} distanceFilter`
+  `@param {Integer} [distanceFilter](https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocationManager_Class/CLLocationManager/CLLocationManager.html#//apple_ref/occ/instp/CLLocationManager/distanceFilter)`
+
+  The minimum distance (measured in meters) a device must move horizontally before an update event is generated.
+
+  `@param {Integer} stationaryRadius (meters)
+
+When stopped, the minimum distance the device must move beyond the stationary location for aggressive background-tracking to engage.  Note, since the plugin uses iOS significant-changes API, the plugin cannot detect the exact moment the device moves out of the stationary-radius.  In normal conditions, it can take as much as 3 city-blocks to 1/2 km before staionary-region exit is detected.
 
 ## Android