doc: Fixed some qdoc errors.

2 files changed, 22 insertions, 22 deletions

diff --git a/doc/src/frameworks-technologies/gestures.qdoc b/doc/src/frameworks-technologies/gestures.qdoc
index 57f25ba..a0eab21 100644
--- a/doc/src/frameworks-technologies/gestures.qdoc
+++ b/doc/src/frameworks-technologies/gestures.qdoc
@@ -58,21 +58,21 @@
 
     \section1 Overview
 
-    QGesture is the central class in Qt's gesture framework, providing the API
-    used by classes that represent specific gestures, such as QPanGesture,
-    QPinchGesture, and QSwipeGesture. These standard classes are ready to use,
-    and each exposes functions and properties that give gesture-specific
-    information about the user's input. This is described in the
-    \l{#Using Standard Gestures}{Using Standard Gestures} section.
-
-    QGesture is also designed to be subclassed and extended so that support for
-    new gestures can be implemented by developers. Adding support for a new
-    gesture involves implementing code to recognize the gesture from incoming
-    events. This is described in the
-    \l{#Creating Your Own Gesture Recognizer}{Creating Your Own Gesture Recognizer}
-    section.
-
-    \section1 Using Standard Gestures with Widgets
+    QGesture is the central class in Qt's gesture framework, providing
+    the API used by classes that represent specific gestures, such as
+    QPanGesture, QPinchGesture, and QSwipeGesture. These standard
+    classes are ready to use, and each exposes functions and
+    properties that give gesture-specific information about the user's
+    input. This is described in the section \l{Using Standard Gestures
+    With Widgets}.
+
+    QGesture is also designed to be subclassed and extended so that
+    support for new gestures can be implemented by developers. Adding
+    support for a new gesture involves implementing code to recognize
+    the gesture from incoming events. This is described in the section
+    \l{Creating Your Own Gesture Recognizer}.
+
+    \section1 Using Standard Gestures With Widgets
 
     Gesture objects are applied directly to widgets and other controls that accept
     user input \mdash these are the \e{target objects}. When a gesture object is
@@ -91,10 +91,11 @@
 
     \snippet examples/gestures/imageviewer/imagewidget.cpp connect swipe gesture
 
-    Here, the \l{QGesture::}{triggered()} signal is used to inform the application
-    that a gesture was used. More precise monitoring of a gesture can be implemented
-    by connecting its \l{QGesture::}{started()}, \l{QGesture::}{canceled()} and
-    \l{QGesture::}{finished()} signals to slots.
+    Here, the \l{QGesture::} {triggered()} signal is used to inform
+    the application that a gesture was used. More precise monitoring
+    of a gesture can be implemented by connecting its \l{QGesture::}
+    {started()}, \l{QGesture::} {canceled()} and \l{QGesture::}
+    {finished()} signals to slots.
 
     Responding to a signal is simply a matter of obtaining the gesture that sent
     it and examining the information it contains.
@@ -141,7 +142,7 @@
 
     \table
     \header \o New State            \o Description              \o QGesture Actions on Entering this State
-    \row    \o Qt::NoGesture        \o Initial value            \o emit \l {QGesture::}{cancelled()}
+    \row    \o Qt::NoGesture        \o Initial value            \o emit \l {QGesture::}{canceled()}
     \row    \o Qt::GestureStarted   \o A continuous gesture has started \o emit \l{QGesture::}{started()} and emit \l{QGesture::}{triggered()}
     \row    \o Qt::GestureUpdated   \o A gesture continues      \o emit \l{QGesture::}{triggered()}
     \row    \o Qt::GestureFinished  \o A gesture has finished.  \o emit \l{QGesture::}{finished()}
diff --git a/src/gui/image/qimagereader.cpp b/src/gui/image/qimagereader.cpp
index 5cd768f..aff186b 100644
--- a/src/gui/image/qimagereader.cpp
+++ b/src/gui/image/qimagereader.cpp
@@ -696,13 +696,12 @@ bool QImageReader::autoDetectImageFormat() const
 
 
 /*!
-
     Specifies that the image reader should decide which plugin to use
     solely based on the contents in the datastream.
 
     Setting this flag means that all image plugins gets loaded. Each
     plugin will read the first bytes in the image data and decide if
-    the plugin is compatible or not.
+    the plugin is compatible or not. The flag is set to \a ignored.
 
     This also disables auto detecting image format.
 */