Document behavior of CBL Replicator as it relates to App Life Cycle

Please include a section under Replication for  "Replicator and App Life Cycle" for each of the platforms 

1) iOS 

Continuous and One Shot : 

Please include this awesome diagram  from Jay Vavachan  that I slightly modified and have attached

replicator-state-2.pptx

Best Practice : Since we do not control the state of the replicator when the app is in the background (i.e. the app could have been terminated by the OS), it is recommended that the app do a null check to ensure that the database and replicator instance are still valid when brought to the foreground 

2) Android 

System does not do anything to the replication.  It will continue running as long as the remote system does not terminate the connection and the app does not terminate.

Best Practice : ??

3) .NET

System does not do anything to the replication.  It will continue running as long as the remote system does not terminate the replication and the app does not terminate.

Best Practice : ?? 

CC Jay Vavachan, Pasin Suriyentrakorn, Jim Borden, Blake Meike please chime in ..this is our chance to fix docs on this topic