summaryrefslogtreecommitdiffstats
path: root/doc/src/declarative/behaviors-and-states.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/declarative/behaviors-and-states.qdoc')
-rw-r--r--doc/src/declarative/behaviors-and-states.qdoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/declarative/behaviors-and-states.qdoc b/doc/src/declarative/behaviors-and-states.qdoc
index 7b6ed1dd..9de42302 100644
--- a/doc/src/declarative/behaviors-and-states.qdoc
+++ b/doc/src/declarative/behaviors-and-states.qdoc
@@ -77,8 +77,8 @@ problem occurs because we have used a Behavior to animate the change in color, a
To state the problem more formally, using States and Behaviors together can cause unexpected behavior when:
\list
-\o a Behavior is used to animate a property change, specifically when moving from an explicitly defined state back to the implicit base state; and
-\o this Behavior can be interrupted to (re-)enter an explicitly defined state.
+\li a Behavior is used to animate a property change, specifically when moving from an explicitly defined state back to the implicit base state; and
+\li this Behavior can be interrupted to (re-)enter an explicitly defined state.
\endlist
The problem occurs because of the way the base state is defined for QML: as the "snapshot" state of the application just prior to entering an explicitly defined state. In this case, if we are in the process of animating from green back