typo

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/src/declarative/qmlformat.qdoc b/doc/src/declarative/qmlformat.qdoc
index 5013ee7..f16adca 100644
--- a/doc/src/declarative/qmlformat.qdoc
+++ b/doc/src/declarative/qmlformat.qdoc
@@ -91,8 +91,8 @@ The blue rectangle in the diagram represents a property binding.  Associated wit
 binding is the QML context to which it belongs, the object property to which it is bound and a
 \e {scope object}.  The scope object is usually, but not always, the object to which the bound 
 property belongs.  The context properties, context default objects and the scope object are all 
-involved when resolving a variable name in a binding.  The following psuedo code describes the 
-alogithm used:
+involved when resolving a variable name in a binding.  The following pseudo code describes the
+algorithm used:
 
 \table
 \row
@@ -139,7 +139,7 @@ To the QML engine, a composite type is just another QML document.  When a compos
 used the engine instantiates it just as it would any other document - by creating a new implicit
 QML context and the object tree described by the document.  The diagram below shows the 
 \c SquareImage composite type used from within another QML document.  When instantiated, the
-\c SquareImage object is created in its own QML context.  Any property bindings sepecified in the
+\c SquareImage object is created in its own QML context.  Any property bindings specified in the
 \c SquareImage composite type document are associated with this context.  Property bindings created
 in the outer document, however, are associated with its context, even those that are applied to the
 created \c SquareImage object.  That is, the \c size, \c source, \c width and \c height property