12 files changed, 18 insertions, 18 deletions
diff --git a/examples/widgets/doc/src/addressbook-tutorial.qdoc b/examples/widgets/doc/src/addressbook-tutorial.qdoc
index 2a6358362a5..2f7884bee8f 100644
--- a/examples/widgets/doc/src/addressbook-tutorial.qdoc
+++ b/examples/widgets/doc/src/addressbook-tutorial.qdoc
@@ -200,7 +200,7 @@
     is started. We start the event loop by calling the application's
     \l{QApplication::}{exec()} function; the result returned by this function
     is used as the return value from the \c main() function. At this point,
-    it becomes apparent why we instanciated \c AddressBook on the stack: It
+    it becomes apparent why we instantiated \c AddressBook on the stack: It
     will now go out of scope. Therefore, \c AddressBook and all its child widgets
     will be deleted, thus preventing memory leaks.
 */
diff --git a/examples/widgets/doc/src/charactermap.qdoc b/examples/widgets/doc/src/charactermap.qdoc
index 639640cad92..ee6162302f8 100644
--- a/examples/widgets/doc/src/charactermap.qdoc
+++ b/examples/widgets/doc/src/charactermap.qdoc
@@ -171,7 +171,7 @@ QScrollArea provides a viewport onto the \c CharacterWidget when we set
 its widget and handles much of the work needed to provide a scrolling
 viewport.
 
-The font combo box is automatically popuplated with a list of available
+The font combo box is automatically populated with a list of available
 fonts. We list the available styles for the current font in the style
 combobox using the following function:
 
diff --git a/examples/widgets/doc/src/collidingmice-example.qdoc b/examples/widgets/doc/src/collidingmice-example.qdoc
index 1d0edd1cebd..4f6859406ea 100644
--- a/examples/widgets/doc/src/collidingmice-example.qdoc
+++ b/examples/widgets/doc/src/collidingmice-example.qdoc
@@ -137,7 +137,7 @@
 
     Because the complexity of arbitrary shape-shape intersection grows
     with an order of magnitude when the shapes are complex, this
-    operation can be noticably time consuming. An alternative approach
+    operation can be noticeably time consuming. An alternative approach
     is to reimplement the \l
     {QGraphicsItem::collidesWithItem()}{collidesWithItem()} function
     to provide your own custom item and shape collision algorithm.
diff --git a/examples/widgets/doc/src/dragdroprobot.qdoc b/examples/widgets/doc/src/dragdroprobot.qdoc
index 60977803fea..ca62bf73dfd 100644
--- a/examples/widgets/doc/src/dragdroprobot.qdoc
+++ b/examples/widgets/doc/src/dragdroprobot.qdoc
@@ -295,7 +295,7 @@
 
     This snippet has a somewhat random outcome: once in a while, a special
     image is assigned to the drag object's mime data. The pixmap is also
-    assiged as the drag object's pixmap. This will ensure that you can see the
+    assigned as the drag object's pixmap. This will ensure that you can see the
     image that is being dragged as a pixmap under the mouse cursor.
 
     \snippet graphicsview/dragdroprobot/coloritem.cpp 7
diff --git a/examples/widgets/doc/src/editabletreemodel.qdoc b/examples/widgets/doc/src/editabletreemodel.qdoc
index 347fec5db7d..9616610758d 100644
--- a/examples/widgets/doc/src/editabletreemodel.qdoc
+++ b/examples/widgets/doc/src/editabletreemodel.qdoc
@@ -84,7 +84,7 @@
     \l{TreeItem::data}{data()} function to read entries in the \c itemData
     list and a \l{TreeItem::setData}{setData()} function to allow them to
     be modified.
-    As with other functions in the item, this simplifies the implemention
+    As with other functions in the item, this simplifies the implementation
     of the model's \l{QAbstractItemModel::}{data()} and
     \l{QAbstractItemModel::}{setData()} functions.
 
diff --git a/examples/widgets/doc/src/elasticnodes.qdoc b/examples/widgets/doc/src/elasticnodes.qdoc
index fd01e36c20f..fbe506468a4 100644
--- a/examples/widgets/doc/src/elasticnodes.qdoc
+++ b/examples/widgets/doc/src/elasticnodes.qdoc
@@ -331,7 +331,7 @@
     collection of small items that all move around, it's unnecessary for
     Graphics View to waste time finding accurate update regions, so we set the
     QGraphicsView::BoundingRectViewportUpdate viewport update mode. The default
-    would work fine, but this mode is noticably faster for this example.
+    would work fine, but this mode is noticeably faster for this example.
 
     To improve rendering quality, we set QPainter::Antialiasing.
 
diff --git a/examples/widgets/doc/src/findfiles.qdoc b/examples/widgets/doc/src/findfiles.qdoc
index bb69c4d5656..bed831d14d0 100644
--- a/examples/widgets/doc/src/findfiles.qdoc
+++ b/examples/widgets/doc/src/findfiles.qdoc
@@ -218,7 +218,7 @@
     \snippet dialogs/findfiles/window.cpp 10
 
     The private \c createComboBox() function is also called from the
-    contructor. We create a QComboBox with the given text, and make it
+    constructor. We create a QComboBox with the given text, and make it
     editable.
 
     When the user enters a new string in an editable combobox, the
diff --git a/examples/widgets/doc/src/fridgemagnets.qdoc b/examples/widgets/doc/src/fridgemagnets.qdoc
index c3588e812f9..fccadd3b717 100644
--- a/examples/widgets/doc/src/fridgemagnets.qdoc
+++ b/examples/widgets/doc/src/fridgemagnets.qdoc
@@ -67,7 +67,7 @@
     constructor, or by using the \l{QPainter::}{begin()} method as we
     do in this example. The \l{QPainter::}{end()} method deactivates
     it. Note that the latter function is called automatically upon
-    destruction when the painter is actived by its constructor. The
+    destruction when the painter is activated by its constructor. The
     QPainter::Antialiasing render hint ensures that the paint engine
     will antialias the edges of primitives if possible.
 
diff --git a/examples/widgets/doc/src/frozencolumn.qdoc b/examples/widgets/doc/src/frozencolumn.qdoc
index f7796fac7cd..54040bc9e1c 100644
--- a/examples/widgets/doc/src/frozencolumn.qdoc
+++ b/examples/widgets/doc/src/frozencolumn.qdoc
@@ -10,7 +10,7 @@
     \image frozencolumn-example.png "Screenshot of the example"
 
     We use Qt's model/view framework to implement a table with its first
-    column frozen. This technique can be aplied to several columns or rows,
+    column frozen. This technique can be applied to several columns or rows,
     as long as they are on the edge of the table.
 
     The model/view framework allows for one model to be displayed in different
diff --git a/examples/widgets/doc/src/tablet.qdoc b/examples/widgets/doc/src/tablet.qdoc
index 0ec62f2eebc..efbb769e647 100644
--- a/examples/widgets/doc/src/tablet.qdoc
+++ b/examples/widgets/doc/src/tablet.qdoc
@@ -305,7 +305,7 @@
     receive tablet proximity events and forward them to \c TabletCanvas.
     The \c TabletEnterProximity and \c TabletLeaveProximity events are sent to
     the QApplication object, while other tablet events are sent to the QWidget's
-    \c event() hander, which sends them on to \l{QWidget::}{tabletEvent()}.
+    \c event() handler, which sends them on to \l{QWidget::}{tabletEvent()}.
 
 
     \section1 TabletApplication Class Implementation
diff --git a/examples/widgets/doc/src/tooltips.qdoc b/examples/widgets/doc/src/tooltips.qdoc
index e0b17d2fd9a..4712c808516 100644
--- a/examples/widgets/doc/src/tooltips.qdoc
+++ b/examples/widgets/doc/src/tooltips.qdoc
@@ -178,7 +178,7 @@
     making each shape item appear at its defined position. But
     remember to translate the coordinate system back when the item is
     drawn, otherwise the next shape item will appear at a position
-    relative to the item we drawed last.
+    relative to the item drawn last.
 
     \snippet widgets/tooltips/sortingbox.cpp 10
 
diff --git a/examples/widgets/doc/src/transformations.qdoc b/examples/widgets/doc/src/transformations.qdoc
index 3d085efbd21..aabb672b86a 100644
--- a/examples/widgets/doc/src/transformations.qdoc
+++ b/examples/widgets/doc/src/transformations.qdoc
@@ -48,8 +48,8 @@
     coordinate system around the origin (called shearing) using the
     QPainter::shear() function.
 
-    All the tranformation operations operate on QPainter's
-    tranformation matrix that you can retrieve using the
+    All the transformation operations operate on QPainter's
+    transformation matrix that you can retrieve using the
     QPainter::worldTransform() function. A matrix transforms a point in the
     plane to another point. For more information about the
     transformation matrix, see the \l {Coordinate System} and
@@ -265,11 +265,11 @@
     \snippet painting/transformations/window.cpp 1
 
     Then we create the \c RenderArea widgets that will render their
-    shapes with coordinate tranformations. By default the applied
+    shapes with coordinate transformations. By default the applied
     operation is \uicontrol {No Transformation}, i.e. the shapes are
     rendered within the default coordinate system. We create and
     initialize the associated \l {QComboBox}es with items
-    corresponding to the various transformation operations decribed by
+    corresponding to the various transformation operations described by
     the global \c Operation enum.
 
     We also connect the \l {QComboBox}es' \l
@@ -335,10 +335,10 @@
     also has good support for coordinate transformations. With the
     Transformations application you can scale, rotate and translate
     QPainter's coordinate system.  The order in which these
-    tranformations are applied is essential for the result.
+    transformations are applied is essential for the result.
 
-    All the tranformation operations operate on QPainter's
-    tranformation matrix. For more information about the
+    All the transformation operations operate on QPainter's
+    transformation matrix. For more information about the
     transformation matrix, see the \l {Coordinate System} and
     QTransform documentation.