updated docs

README.md

@@ -77,17 +77,16 @@ article.submit(by=some_user) # StateLog.by will be some_user
 
 ### Advanced Usage
 You can change the behaviour of this app by turning on caching for StateLog records.
-Simply add `DJANGO_FSM_LOG_USE_CACHE = True` to your project's settings file. By
-default your project's `'default'` cache backend will be used to store this data. If you wish to
-use a different cache backend, add `DJANGO_FSM_LOG_CACHE_BACKEND = 'custom_backend'` to your settings file.
+Simply add `DJANGO_FSM_LOG_CACHE_BACKEND = 'backend_name'` to your project's settings file. This
+will store any pending StateLog records in the cache using the cache backend you specified.
 
-When caching is on, you can access the StateLog record before the transition takes place,
-and before it has been persisted to the database.
+This is useful if you need to verify whether or not the StateLog has been written to the database.
+Access to the pending StateLog record is available via the `pending_objects` manager
 
 ```python
 from django_fsm_log.models import StateLog
 article = Article.objects.get(...)
-pending_state_log = StateLog.objects.get_pending_for_object(article)
+pending_state_log = StateLog.pending_objects.get_for_object(article)
 ```
 
 This pending StateLog object is available after the `django_fsm.signals.pre_transition`