summaryrefslogtreecommitdiffstats
path: root/examples/sql/doc/src/cachedtable.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'examples/sql/doc/src/cachedtable.qdoc')
-rw-r--r--examples/sql/doc/src/cachedtable.qdoc7
1 files changed, 4 insertions, 3 deletions
diff --git a/examples/sql/doc/src/cachedtable.qdoc b/examples/sql/doc/src/cachedtable.qdoc
index ff04fb114a..ff60f7b1b7 100644
--- a/examples/sql/doc/src/cachedtable.qdoc
+++ b/examples/sql/doc/src/cachedtable.qdoc
@@ -3,8 +3,9 @@
/*!
\example cachedtable
- \title Cached Table Example
+ \title Cached SQL Table
\ingroup sql_examples
+ \examplecategory {Data Processing & I/O}
\brief The Cached Table example shows how a table view can be used to access a database,
caching any changes to the data until the user explicitly submits them using a
@@ -14,7 +15,7 @@
The example consists of a single class, \c TableEditor, which is a
custom dialog widget that allows the user to modify data stored in
- a database. We will first review the class definiton and how to
+ a database. We will first review the class definition and how to
use the class, then we will take a look at the implementation.
\section1 TableEditor Class Definition
@@ -40,7 +41,7 @@
We are also going to show how a table view can be used to cache
any changes to the data until the user explicitly requests to
submit them. For that reason we need to declare a \c submit() slot
- in additon to the model and the editor's buttons.
+ in addition to the model and the editor's buttons.
\table 100%
\header \li Connecting to a Database