Doc: Fix link issues

Change-Id: I0e08820a6d25996fe27118f05214ff63d695d24e
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>

6 files changed, 27 insertions, 20 deletions

diff --git a/src/imports/testlib/toucheventsequence.qdoc b/src/imports/testlib/toucheventsequence.qdoc
index d7cc48c5dd..92c5836d49 100644
--- a/src/imports/testlib/toucheventsequence.qdoc
+++ b/src/imports/testlib/toucheventsequence.qdoc
@@ -51,7 +51,7 @@
 
     Events are delivered to the window which contains the item specified in touchEvent.
 
-    \sa TestCase::touchEvent(), QTest::QTouchEventSequence
+    \sa TestCase::touchEvent()
 */
 
 /*!
diff --git a/src/qmltest/doc/src/qtquicktest-index.qdoc b/src/qmltest/doc/src/qtquicktest-index.qdoc
index 48b41d4f0a..dfd15b706b 100644
--- a/src/qmltest/doc/src/qtquicktest-index.qdoc
+++ b/src/qmltest/doc/src/qtquicktest-index.qdoc
@@ -142,7 +142,7 @@
     \c QUICK_TEST_MAIN_WITH_SETUP macro can be used. This can be useful for
     setting context properties on the QML engine, amongst other things.
 
-    The macro is identical to \l QUICK_TEST_MAIN, except that it takes an
+    The macro is identical to \c QUICK_TEST_MAIN, except that it takes an
     additional \c QObject* argument. The test framework will call slots and
     invokable functions with the following names:
 
diff --git a/src/quick/handlers/qquickpointhandler.cpp b/src/quick/handlers/qquickpointhandler.cpp
index 6d6ba07f5c..30f62332ba 100644
--- a/src/quick/handlers/qquickpointhandler.cpp
+++ b/src/quick/handlers/qquickpointhandler.cpp
@@ -59,8 +59,8 @@ QT_BEGIN_NAMESPACE
     occurs within the bounds of the \l {PointerHandler::parent}, and
     no sibling PointHandler within the same \l {PointerHandler::parent}
     has yet acquired a passive grab on that point, and if the other
-    constraints such as \l[QML]{SinglePointHandler::acceptedButtons},
-    \l {PointerDeviceHandler::acceptedDevices} etc. are satisfied, it's
+    constraints such as \l {PointerDeviceHandler::acceptedButtons}{acceptedButtons}, \l {PointerDeviceHandler::acceptedDevices}{acceptedDevices} etc.
+    are satisfied, it's
     eligible, and the PointHandler then acquires a passive grab. In
     this way, the \l {PointerHandler::parent} acts like an exclusive
     group: there can be multiple instances of PointHandler, and the
diff --git a/src/quick/handlers/qquicktaphandler.cpp b/src/quick/handlers/qquicktaphandler.cpp
index 9386676b7a..41ac294df3 100644
--- a/src/quick/handlers/qquicktaphandler.cpp
+++ b/src/quick/handlers/qquicktaphandler.cpp
@@ -229,7 +229,7 @@ void QQuickTapHandler::timerEvent(QTimerEvent *event)
            will not take the exclusive grab, but merely a passive grab.
 
     \value TapHandler.WithinBounds
-           If the event point leaves the bounds of the \l parent Item, the tap
+           If the event point leaves the bounds of the \c parent Item, the tap
            gesture is canceled. The TapHandler will take the exclusive grab on
            press, but will release the grab as soon as the boundary constraint
            is no longer satisfied.
@@ -237,7 +237,7 @@ void QQuickTapHandler::timerEvent(QTimerEvent *event)
     \value TapHandler.ReleaseWithinBounds
            At the time of release (the mouse button is released or the finger
            is lifted), if the event point is outside the bounds of the
-           \l parent Item, a tap gesture is not recognized. This corresponds to
+           \c parent Item, a tap gesture is not recognized. This corresponds to
            typical behavior for button widgets: you can cancel a click by
            dragging outside the button, and you can also change your mind by
            dragging back inside the button before release. Note that it's
@@ -382,7 +382,7 @@ void QQuickTapHandler::updateTimeHeld()
 /*!
     \qmlsignal QtQuick::TapHandler::tapped
 
-    This signal is emitted each time the \l parent Item is tapped.
+    This signal is emitted each time the \c parent Item is tapped.
 
     That is, if you press and release a touchpoint or button within a time
     period less than \l longPressThreshold, while any movement does not exceed
@@ -394,7 +394,7 @@ void QQuickTapHandler::updateTimeHeld()
     \qmlsignal QtQuick::TapHandler::singleTapped
     \since 5.11
 
-    This signal is emitted when the \l parent Item is tapped once.
+    This signal is emitted when the \c parent Item is tapped once.
     After an amount of time greater than QStyleHints::mouseDoubleClickInterval,
     it can be tapped again; but if the time until the next tap is less,
     \l tapCount will increase.
@@ -404,7 +404,7 @@ void QQuickTapHandler::updateTimeHeld()
     \qmlsignal QtQuick::TapHandler::doubleTapped
     \since 5.11
 
-    This signal is emitted when the \l parent Item is tapped twice within a
+    This signal is emitted when the \c parent Item is tapped twice within a
     short span of time (QStyleHints::mouseDoubleClickInterval) and distance
     (QPlatformTheme::MouseDoubleClickDistance or
     QPlatformTheme::TouchDoubleTapDistance). This signal always occurs after
@@ -414,11 +414,18 @@ void QQuickTapHandler::updateTimeHeld()
 /*!
     \qmlsignal QtQuick::TapHandler::longPressed
 
-    This signal is emitted when the \l parent Item is pressed and held for a
+    This signal is emitted when the \c parent Item is pressed and held for a
     time period greater than \l longPressThreshold. That is, if you press and
     hold a touchpoint or button, while any movement does not exceed the drag
     threshold, then the \c longPressed signal will be emitted at the time that
     \l timeHeld exceeds \l longPressThreshold.
 */
 
+/*!
+    \qmlsignal QtQuick::TapHandler::tapCountChanged
+
+    This signal is emitted when the \c parent Item is tapped once or more (within
+    a specified time and distance span) and when the present \c tapCount differs
+    from the previous \c tapCount.
+*/
 QT_END_NAMESPACE
diff --git a/src/quick/items/qquicktableview.cpp b/src/quick/items/qquicktableview.cpp
index 9949f083b1..9cd407b0fd 100644
--- a/src/quick/items/qquicktableview.cpp
+++ b/src/quick/items/qquicktableview.cpp
@@ -133,7 +133,7 @@
     width, unless the \l columnWidthProvider property is explicitly set. Once
     the column width is found, all other items in the same column are resized
     to this width, even if new items that are flicked in later have larger
-    \c implicitWidth. Setting an explicit \l width on an item is ignored and
+    \c implicitWidth. Setting an explicit \c width on an item is ignored and
     overwritten.
 
     \note The calculated width of a column is discarded when it is flicked out
@@ -256,9 +256,10 @@
     applies to \c row and \c column. Properties of the model are also available
     depending upon the type of \l {qml-data-models}{Data Model}.
 
-    A delegate should specify its size using \l implicitWidth and \l implicitHeight.
-    The TableView lays out the items based on that information. Explicit \l width or
-    \l height settings are ignored and overwritten.
+    A delegate should specify its size using \l [QML]{Item::implicitWidth}{implicitWidth} and
+    \l [QML]{Item::implicitHeight}{implicitHeight}.
+    The TableView lays out the items based on that information. Explicit width or
+    height settings are ignored and overwritten.
 
     \note Delegates are instantiated as needed and may be destroyed at any time.
     They are also reused if the \l reuseItems property is set to \c true. You
@@ -280,7 +281,7 @@
 /*!
     \qmlproperty real QtQuick::TableView::contentWidth
 
-    This property holds the width of the \l contentView, which is also
+    This property holds the width of the \l view, which is also
     the width of the table (including margins). As a TableView cannot
     always know the exact width of the table without loading all columns
     in the model, the \c contentWidth is usually an estimated width based on
@@ -298,7 +299,7 @@
 /*!
     \qmlproperty real QtQuick::TableView::contentHeight
 
-    This property holds the height of the \l contentView, which is also
+    This property holds the height of the \l view, which is also
     the height of the table (including margins). As a TableView cannot
     always know the exact height of the table without loading all rows
     in the model, the \c contentHeight is usually an estimated height
@@ -319,7 +320,7 @@
     Responding to changes in the model are batched so that they are handled
     only once per frame. This means the TableView delays showing any changes
     while a script is being run. The same is also true when changing
-    properties such as \l rowSpacing or \l leftMargin.
+    properties such as \l rowSpacing or \l {Item::anchors.leftMargin}{leftMargin}.
 
     This method forces the TableView to immediately update the layout so
     that any recent changes take effect.
diff --git a/src/quickshapes/qquickshape.cpp b/src/quickshapes/qquickshape.cpp
index 489d1c86f7..262d0b3e9a 100644
--- a/src/quickshapes/qquickshape.cpp
+++ b/src/quickshapes/qquickshape.cpp
@@ -805,9 +805,8 @@ QQuickShape::Status QQuickShape::status() const
     \since QtQuick.Shapes 1.11
 
     This property determines the definition of \l {QQuickItem::contains()}{contains()}
-    for the Shape. It is useful in case you add
-    \l {Qt Quick Pointer Handlers QML Types}{Pointer Handlers} and you
-    want to react only when the mouse or touchpoint is fully inside the Shape.
+    for the Shape. It is useful in case you add \l {Qt Quick Input Handlers} and you want to
+    react only when the mouse or touchpoint is fully inside the Shape.
 
     \value Shape.BoundingRectContains
         The default implementation of \l QQuickItem::contains() checks only