summaryrefslogtreecommitdiffstats
path: root/examples/corelib/tools/doc/src/contiguouscache.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'examples/corelib/tools/doc/src/contiguouscache.qdoc')
-rw-r--r--examples/corelib/tools/doc/src/contiguouscache.qdoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/corelib/tools/doc/src/contiguouscache.qdoc b/examples/corelib/tools/doc/src/contiguouscache.qdoc
index c2c686b237..0d06036cd1 100644
--- a/examples/corelib/tools/doc/src/contiguouscache.qdoc
+++ b/examples/corelib/tools/doc/src/contiguouscache.qdoc
@@ -34,7 +34,7 @@
isn't, users still dislike an application using excessive memory.
Using QContiguousCache to manage a list, rather than loading
the entire list into memory, allows the application to limit the amount
- of memory it uses, regardless of the size of the data set it accesses
+ of memory it uses, regardless of the size of the data set it accesses.
The simplest way to use QContiguousCache is to cache as items are requested. When
a view requests an item at row N it is also likely to ask for items at rows near