Typos.
This commit is contained in:
parent
9d8fbf07b9
commit
56e12f0dba
|
@ -18,5 +18,5 @@ Django-cachalot modifies Django in place during execution to add a caching tool
|
|||
just before SQL queries are executed.
|
||||
When a SQL query reads data, we save the result in cache. If that same query is
|
||||
executed later, we fetch that result from cache.
|
||||
When we detect `CREATE`, `UPDATE` or `DELETE`, we know which tables are
|
||||
When we detect ``INSERT``, ``UPDATE`` or ``DELETE``, we know which tables are
|
||||
modified. All the previous cached queries can therefore be safely invalidated.
|
||||
|
|
|
@ -6,7 +6,7 @@ Requirements
|
|||
|
||||
- Django 1.6 or 1.7
|
||||
- Python 2.6, 2.7, 3.2, 3.3, or 3.4
|
||||
- a cache configured as `default` with one of these backends:
|
||||
- a cache configured as ``'default'`` with one of these backends:
|
||||
|
||||
- `django-redis <https://github.com/niwibe/django-redis>`_
|
||||
- `memcached <https://docs.djangoproject.com/en/1.7/topics/cache/#memcached>`_
|
||||
|
|
Loading…
Reference in New Issue