summaryrefslogtreecommitdiffstats
path: root/doc/src/declarative/focus.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/declarative/focus.qdoc')
-rw-r--r--doc/src/declarative/focus.qdoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/declarative/focus.qdoc b/doc/src/declarative/focus.qdoc
index 0310cee..c3c94c5 100644
--- a/doc/src/declarative/focus.qdoc
+++ b/doc/src/declarative/focus.qdoc
@@ -120,7 +120,7 @@ hand side of the following table shows what we would like to be able to write.
Here we create two instances of our previously defined component, and set the
second one to have focus. The intention is that when the \e A, \e B, or \e C
keys are pressed, the second of the two components receives the event and
-reponds accordingly.
+responds accordingly.
\table
\row
@@ -276,7 +276,7 @@ Focus scopes allow focus to allocation to be easily partitioned. Several
QML items use it to this effect.
\l ListView, for example, is itself a focus scope. Generally this isn't
-noticable as \l ListView doesn't usually have manually added visual children.
+noticeable as \l ListView doesn't usually have manually added visual children.
By being a focus scope, \l ListView can focus the current list item without
worrying about how that will effect the rest of the application. This allows
the current item delegate to react to key presses.