doc: Fix some spelling errors

Change-Id: I22c0de2d1c5277879fe504764c15a76d1d7f198b
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>

8 files changed, 11 insertions, 11 deletions

diff --git a/doc/api/coding-style.qdoc b/doc/api/coding-style.qdoc
index 42d9c92df1..681f3e3a4d 100644
--- a/doc/api/coding-style.qdoc
+++ b/doc/api/coding-style.qdoc
@@ -435,7 +435,7 @@
         \o  Use \c{class} instead of \c{struct}. Some compilers mangle that
             difference into the symbol names and spit out warnings if a struct
             declaration is followed by a class definition. To avoid ongoing
-            changes from one to the other we declare \c{class} the prefered way.
+            changes from one to the other we declare \c{class} the preferred way.
 
     \endlist
 
@@ -782,7 +782,7 @@
             reentrant, though.
 
         \o  A \c char is signed or unsigned dependent on the architecture. Use signed
-            \c char or \c uchar if you explicitely want a signed or unsigned char.
+            \c char or \c uchar if you explicitly want a signed or unsigned char.
             The following code will break on PowerPC, for example:
 
             \code
@@ -848,7 +848,7 @@
 
         \o  No float comparisons (\c{-Wfloat-equal}). Use \c qFuzzyCompare to compare
             values with a delta. Use \c qIsNull to check whether a float is
-            binary 0, instead of comparing it to 0.0, or, prefered, move
+            binary 0, instead of comparing it to 0.0, or, preferred, move
             such code into an implementation file.
 
        \o  Do not hide virtual methods in subclasses (\{-Woverloaded-virtual}).
diff --git a/doc/src/debugger/creator-debugger-setup.qdoc b/doc/src/debugger/creator-debugger-setup.qdoc
index ea369f2800..fd450effa2 100644
--- a/doc/src/debugger/creator-debugger-setup.qdoc
+++ b/doc/src/debugger/creator-debugger-setup.qdoc
@@ -102,7 +102,7 @@
 
     \section2 Supported CDB Versions
 
-    The CDB native debugger has similar funtionality to the non-Python GDB
+    The CDB native debugger has similar functionality to the non-Python GDB
     debugger engine. Specifically, it also uses compiled C++ code for the
     debugging helper library.
 
diff --git a/doc/src/debugger/creator-debugger.qdoc b/doc/src/debugger/creator-debugger.qdoc
index 284608e9b3..c811a0a977 100644
--- a/doc/src/debugger/creator-debugger.qdoc
+++ b/doc/src/debugger/creator-debugger.qdoc
@@ -193,7 +193,7 @@
 
     While this mode does not strictly require a project to be opened in \QC,
     it is beneficial to have open one, as it makes setting breakpoints
-    and stepping throught the code easier.
+    and stepping through the code easier.
 
     You can specify breakpoints before or after attaching the
     debugger to the application.
diff --git a/doc/src/editors/creator-editors.qdoc b/doc/src/editors/creator-editors.qdoc
index 264d56c629..9a48a28deb 100644
--- a/doc/src/editors/creator-editors.qdoc
+++ b/doc/src/editors/creator-editors.qdoc
@@ -1652,7 +1652,7 @@
         \row
             \o Switch with Next/Previous Parameter
             \o Moves a parameter down or up one position in a parameter list.
-            \o Parameter in the declaration or definition of a fuction or method
+            \o Parameter in the declaration or definition of a function or method
         \row
             \o Extract Method
             \o Moves the selected code to a new method and replaces the block of
diff --git a/doc/src/howto/creator-keyboard-shortcuts.qdoc b/doc/src/howto/creator-keyboard-shortcuts.qdoc
index 3b5403f1f8..25c5b8277f 100644
--- a/doc/src/howto/creator-keyboard-shortcuts.qdoc
+++ b/doc/src/howto/creator-keyboard-shortcuts.qdoc
@@ -421,10 +421,10 @@
             \o Find previous
             \o Shift+F3
         \row
-            \o Find next occurence of selected text
+            \o Find next occurrence of selected text
             \o Ctrl+F3
         \row
-            \o Find previous occurence of selected text
+            \o Find previous occurrence of selected text
             \o Ctrl+Shift+F3
         \row
             \o Replace next
diff --git a/doc/src/howto/creator-vcs.qdoc b/doc/src/howto/creator-vcs.qdoc
index 3f371ae6b2..337a45ca77 100644
--- a/doc/src/howto/creator-vcs.qdoc
+++ b/doc/src/howto/creator-vcs.qdoc
@@ -245,7 +245,7 @@
     \section3 Reverting Changes Using Git
 
     The Git version control system has an index that is used to stage
-    changes. The index is commited on the next commit. Git allows you to revert
+    changes. The index is committed on the next commit. Git allows you to revert
     back to the state of the last commit as well as to the state staged in the
     index.
 
diff --git a/doc/src/howto/qtcreator-faq.qdoc b/doc/src/howto/qtcreator-faq.qdoc
index bcb0fe5d45..c1ce45912e 100644
--- a/doc/src/howto/qtcreator-faq.qdoc
+++ b/doc/src/howto/qtcreator-faq.qdoc
@@ -197,7 +197,7 @@
     sudo apt-get install libgl-dev libglu-dev
     \endcode
 
-    \section1 Platform Releated Questions
+    \section1 Platform Related Questions
 
     \bold {Where is application output shown in \QC?}
 
diff --git a/doc/src/projects/creator-projects-custom-wizards.qdoc b/doc/src/projects/creator-projects-custom-wizards.qdoc
index 90aa8ba8ce..aa29e9b7a3 100644
--- a/doc/src/projects/creator-projects-custom-wizards.qdoc
+++ b/doc/src/projects/creator-projects-custom-wizards.qdoc
@@ -509,7 +509,7 @@
     \endcode
 
     By default, the scripts are run in the directory corresponding to
-    \c %TargetPath%. This can be overriden by specifying the attribute
+    \c %TargetPath%. This can be overridden by specifying the attribute
     \c workingdirectory on the element \c generatorscript. For example, if the
     script creates the project directory by itself, %Path% can be specified. In
     that case, \c --dry-run should output the correct relative paths or absolute