typo fixes

Change-Id: Ia5f104bfd707bcf4e159c78ca2764c861fb0b6d9

5 files changed, 6 insertions, 6 deletions

diff --git a/framework/inc/threadhelp/fairrwlock.hxx b/framework/inc/threadhelp/fairrwlock.hxx
index 6261bab716e9..ece091b7e295 100644
--- a/framework/inc/threadhelp/fairrwlock.hxx
+++ b/framework/inc/threadhelp/fairrwlock.hxx
@@ -194,7 +194,7 @@ class FairRWLock : public  IRWLock
 
             @attention  Don't call this method if you are not a writer!
                         Results are not defined then ...
-                        An upgrade can't be implemented realy ... because acquiring new access
+                        An upgrade can't be implemented really ... because acquiring new access
                         will be the same - there no differences!
 
             @seealso    -
diff --git a/framework/inc/threadhelp/inoncopyable.h b/framework/inc/threadhelp/inoncopyable.h
index 98f263b2bb9a..e5799baca580 100644
--- a/framework/inc/threadhelp/inoncopyable.h
+++ b/framework/inc/threadhelp/inoncopyable.h
@@ -25,7 +25,7 @@ namespace framework{
 /*-************************************************************************************************************//**
     @descr          Use this as one of your base classes to disable
                     all possiblities to copy or assign one object to another one!
-                    We declare neccessary functions private to do so.
+                    We declare necessary functions private to do so.
 *//*-*************************************************************************************************************/
 class INonCopyable
 {
diff --git a/framework/inc/threadhelp/readguard.hxx b/framework/inc/threadhelp/readguard.hxx
index 2db89a63f629..afdd17316f3c 100644
--- a/framework/inc/threadhelp/readguard.hxx
+++ b/framework/inc/threadhelp/readguard.hxx
@@ -33,7 +33,7 @@ namespace framework{
     @descr          This guard should be used to set a lock for reading object internal member.
                     Nobody can control it but don't use member after successfully locking for writing!
                     We never need a own mutex to safe our internal member access - because
-                    a guard is used as function-local member only. There exist no multithreaded access to it realy ...
+                    a guard is used as function-local member only. There exist no multithreaded access to it really ...
 
     @attention      a) To prevent us against wrong using, the default ctor, copy ctor and the =operator are maked private!
                     b) Use interface "IRWLock" of set LockHelper only - because we must support a finer granularity of locking.
diff --git a/framework/inc/threadhelp/transactionguard.hxx b/framework/inc/threadhelp/transactionguard.hxx
index fae6b9d7e191..858fd9909738 100644
--- a/framework/inc/threadhelp/transactionguard.hxx
+++ b/framework/inc/threadhelp/transactionguard.hxx
@@ -54,7 +54,7 @@ class TransactionGuard : private INonCopyable
             @descr      Use these ctor methods to initialize the guard right.
                         Given reference must be valid - otherwise crashes could occur!
 
-            @attention  It's not neccessary to lock any mutex here! Because a ctor should not be called
+            @attention  It's not necessary to lock any mutex here! Because a ctor should not be called
                         from different threads at the same time ... this class use no refcount mechanism!
 
             @seealso    -
diff --git a/framework/inc/threadhelp/writeguard.hxx b/framework/inc/threadhelp/writeguard.hxx
index 696b4780ffa4..faf123086ca9 100644
--- a/framework/inc/threadhelp/writeguard.hxx
+++ b/framework/inc/threadhelp/writeguard.hxx
@@ -30,7 +30,7 @@ namespace framework{
     @short          implement a guard to set write locks
     @descr          This guard should be used to set a lock for reading AND writing object internal member.
                     We never need a own mutex to safe our internal member access - because
-                    a guard is used as function-local member only. There exist no multithreaded access to it realy ...
+                    a guard is used as function-local member only. There exist no multithreaded access to it really ...
 
     @attention      a) To prevent us against wrong using, the default ctor, copy ctor and the =operator are maked private!
                     b) Use interface "IRWLock" of set LockHelper only - because we must support a finer granularity of locking.
@@ -144,7 +144,7 @@ class WriteGuard : private INonCopyable
             {
                 case E_READLOCK     :   {
                                             // User has downgraded to a read lock before!
-                                            // => There isn't realy a write lock ...
+                                            // => There isn't really a write lock ...
                                             m_pLock->releaseReadAccess();
                                             m_eMode = E_NOLOCK;
                                         }