Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit e228ab6

Browse filesBrowse files
committed
Minor tweaks
1 parent ec396c3 commit e228ab6
Copy full SHA for e228ab6

File tree

1 file changed

+2
-2
lines changed
Filter options

1 file changed

+2
-2
lines changed

‎components/cache.rst

Copy file name to clipboardExpand all lines: components/cache.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ This method allows you to namespace cached items by transparently prefixing thei
114114

115115
In this example, the cache item uses the ``dashboard_data`` key, but it will be
116116
stored internally under a namespace based on the current user ID. This is handled
117-
automatically, so you **dont** need to manually prefix keys like ``user-27.dashboard_data``.
117+
automatically, so you **don't** need to manually prefix keys like ``user-27.dashboard_data``.
118118

119119
There are no guidelines or restrictions on how to define cache namespaces.
120120
You can make them as granular or as generic as your application requires:
@@ -130,7 +130,7 @@ You can make them as granular or as generic as your application requires:
130130

131131
.. tip::
132132

133-
You can even combine cache namespaces with :ref:`cache tags <cache-using-cache-tags>`
133+
You can combine cache namespaces with :ref:`cache tags <cache-using-cache-tags>`
134134
for more advanced needs.
135135

136136
There is no built-in way to invalidate caches by namespace. Instead, the recommended

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.