Fix some typos in documentation.

Fix some spelling and grammatical errors in comments that show up in Qt documentation. No changes to code.

Change-Id: I2d91518900c9b60ee8e8a8f549c88a1d50632b3d
Reviewed-by: Nico Vertriest <nico.vertriest@digia.com>
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Reviewed-by: Martin Smith <martin.smith@digia.com>

4 files changed, 4 insertions, 4 deletions

diff --git a/examples/quick/views/listview/highlightranges.qml b/examples/quick/views/listview/highlightranges.qml
index 6c4190dada..8b4eed7400 100644
--- a/examples/quick/views/listview/highlightranges.qml
+++ b/examples/quick/views/listview/highlightranges.qml
@@ -89,7 +89,7 @@ Rectangle {
     // item visible.
     //
     // The second ListView sets a highlight range which attempts to keep the
-    // current item within the the bounds of the range. However,
+    // current item within the bounds of the range. However,
     // items will not scroll beyond the beginning or end of the view,
     // forcing the highlight to move outside the range at the ends.
     //
diff --git a/src/particles/qquickgroupgoal.cpp b/src/particles/qquickgroupgoal.cpp
index 5ef09c4185..8a487ae4c5 100644
--- a/src/particles/qquickgroupgoal.cpp
+++ b/src/particles/qquickgroupgoal.cpp
@@ -70,7 +70,7 @@ QT_BEGIN_NAMESPACE
     \qmlproperty bool QtQuick.Particles::GroupGoal::jump
 
     If true, affected particles will jump directly to the target group instead of taking the
-    the shortest valid path to get there. They will also not finish their current state,
+    shortest valid path to get there. They will also not finish their current state,
     but immediately move to the beginning of the goal state.
 
     Default is false.
diff --git a/src/particles/qquickspritegoal.cpp b/src/particles/qquickspritegoal.cpp
index c31ef46326..08c57f3d45 100644
--- a/src/particles/qquickspritegoal.cpp
+++ b/src/particles/qquickspritegoal.cpp
@@ -70,7 +70,7 @@ QT_BEGIN_NAMESPACE
     \qmlproperty bool QtQuick.Particles::SpriteGoal::jump
 
     If true, affected sprites will jump directly to the goal state instead of taking the
-    the shortest valid path to get there. They will also not finish their current state,
+    shortest valid path to get there. They will also not finish their current state,
     but immediately move to the beginning of the goal state.
 
     Default is false.
diff --git a/src/qml/doc/src/qmllanguageref/syntax/propertybinding.qdoc b/src/qml/doc/src/qmllanguageref/syntax/propertybinding.qdoc
index 6803901efd..653fe2391e 100644
--- a/src/qml/doc/src/qmllanguageref/syntax/propertybinding.qdoc
+++ b/src/qml/doc/src/qmllanguageref/syntax/propertybinding.qdoc
@@ -30,7 +30,7 @@
 \title Property Binding
 \brief binding object properties
 
-To make the fullest use of QML and its built-in support for implementing dynamic object behavioral changes, most QML objects will use \e {property binding}. This is a core feature of QML that allows objects to automatically update their properties in response to changing attributes in other objects or the occurence of some external event.
+To make the fullest use of QML and its built-in support for implementing dynamic object behavioral changes, most QML objects will use \e {property binding}. This is a core feature of QML that allows objects to automatically update their properties in response to changing attributes in other objects or the occurrence of some external event.
 
 When an object's property is assigned a value, it can either be assigned a static value, or \e bound to a JavaScript expression. In the first case, the property's value will not change unless a new value is assigned to the property. In the latter case, a \e {property binding} is created and the property's value is automatically updated by the QML engine whenever the value of the evaluated expression changes.