Doc: Fix typos that cause QDoc warnings

Change-Id: I496e4a7fb17e7d7fb93f0f50f99e332f1456a190
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc b/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc
index 555f730c9e..4736dc7ddd 100644
--- a/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc
+++ b/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc
@@ -166,7 +166,7 @@ To visualize data, bind the view's \c model property to a model and the
 
     To get finer control over which roles are accessible, and to make delegates
     more self-contained and usable outside of views,
-    \li{Required Properties}{required properties} can be used. If a delegate
+    \l{Required Properties}{required properties} can be used. If a delegate
     contains required properties, the named roles are not provided. Instead,
     the QML engine will check if the name of a required property matches that of
     a model role. If so, that property will be bound to the corresponding value
@@ -431,7 +431,7 @@ ListView {
 \note The \c edit role is equal to \l Qt::EditRole. See \l{QAbstractItemModel::}{roleNames}()
 for the built-in role names. However, real life models would usually register custom roles.
 
-\node If a model role is bound to a \li{Required Property}{required property}, assigning to
+\note If a model role is bound to a \l{Required Property}{required property}, assigning to
 that property will not modify the model. It will instead break the binding to the model (just
 like assigning to any other property breaks existing bindings). If you want to use
 required properties and change the model data, make model also a required property and assign to