Remove the usage of deprecated qdoc macros.

QDoc now has support for Doxygen style commands for italics, bold
and list items. This change applies that change in QDoc to the
actual documentation.

Task-number: QTBUG-24578
Change-Id: I519bf9c29b14092e3ab6067612f42bf749eeedf5
Reviewed-by: Shane Kearns <shane.kearns@accenture.com>
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>

5 files changed, 9 insertions, 9 deletions

diff --git a/src/gui/math3d/qgenericmatrix.cpp b/src/gui/math3d/qgenericmatrix.cpp
index 113b767e9f..08ed0ae40f 100644
--- a/src/gui/math3d/qgenericmatrix.cpp
+++ b/src/gui/math3d/qgenericmatrix.cpp
@@ -53,9 +53,9 @@ QT_BEGIN_NAMESPACE
     The QGenericMatrix template has three parameters:
 
     \table
-    \row \i N \i Number of columns.
-    \row \i M \i Number of rows.
-    \row \i T \i Element type that is visible to users of the class.
+    \row \li N \li Number of columns.
+    \row \li M \li Number of rows.
+    \row \li T \li Element type that is visible to users of the class.
     \endtable
 
     \sa QMatrix4x4
diff --git a/src/gui/math3d/qmatrix4x4.cpp b/src/gui/math3d/qmatrix4x4.cpp
index 068b2e36f7..0eb3506779 100644
--- a/src/gui/math3d/qmatrix4x4.cpp
+++ b/src/gui/math3d/qmatrix4x4.cpp
@@ -62,11 +62,11 @@ QT_BEGIN_NAMESPACE
     Internally the data is stored as column-major format, so as to be optimal for
     passing to OpenGL functions, which expect column-major data.
 
-    When using these functions be aware that they return data in \bold{column-major}
+    When using these functions be aware that they return data in \b{column-major}
     format:
     \list
-    \o data()
-    \o constData()
+    \li data()
+    \li constData()
     \endlist
 
     \sa QVector3D, QGenericMatrix
diff --git a/src/gui/math3d/qvector2d.cpp b/src/gui/math3d/qvector2d.cpp
index 897fa356d3..3c3581f3f4 100644
--- a/src/gui/math3d/qvector2d.cpp
+++ b/src/gui/math3d/qvector2d.cpp
@@ -60,7 +60,7 @@ QT_BEGIN_NAMESPACE
     The QVector2D class can also be used to represent vertices in 2D space.
     We therefore do not need to provide a separate vertex class.
 
-    \bold{Note:} By design values in the QVector2D instance are stored as \c float.
+    \b{Note:} By design values in the QVector2D instance are stored as \c float.
     This means that on platforms where the \c qreal arguments to QVector2D
     functions are represented by \c double values, it is possible to
     lose precision.
diff --git a/src/gui/math3d/qvector3d.cpp b/src/gui/math3d/qvector3d.cpp
index 5251f9c015..adf3da4010 100644
--- a/src/gui/math3d/qvector3d.cpp
+++ b/src/gui/math3d/qvector3d.cpp
@@ -63,7 +63,7 @@ QT_BEGIN_NAMESPACE
     The QVector3D class can also be used to represent vertices in 3D space.
     We therefore do not need to provide a separate vertex class.
 
-    \bold{Note:} By design values in the QVector3D instance are stored as \c float.
+    \b{Note:} By design values in the QVector3D instance are stored as \c float.
     This means that on platforms where the \c qreal arguments to QVector3D
     functions are represented by \c double values, it is possible to
     lose precision.
diff --git a/src/gui/math3d/qvector4d.cpp b/src/gui/math3d/qvector4d.cpp
index e7ee46b88b..6b29221d92 100644
--- a/src/gui/math3d/qvector4d.cpp
+++ b/src/gui/math3d/qvector4d.cpp
@@ -59,7 +59,7 @@ QT_BEGIN_NAMESPACE
     The QVector4D class can also be used to represent vertices in 4D space.
     We therefore do not need to provide a separate vertex class.
 
-    \bold{Note:} By design values in the QVector4D instance are stored as \c float.
+    \b{Note:} By design values in the QVector4D instance are stored as \c float.
     This means that on platforms where the \c qreal arguments to QVector4D
     functions are represented by \c double values, it is possible to
     lose precision.