typo fixes

Change-Id: Ia5f104bfd707bcf4e159c78ca2764c861fb0b6d9

4 files changed, 12 insertions, 12 deletions

diff --git a/unotools/source/config/cmdoptions.cxx b/unotools/source/config/cmdoptions.cxx
index 1887cb7daeae..e2da7dfa6cb8 100644
--- a/unotools/source/config/cmdoptions.cxx
+++ b/unotools/source/config/cmdoptions.cxx
@@ -77,7 +77,7 @@ class SvtCmdOptions
 
         //---------------------------------------------------------------------------------------------------------
         // convert internal list to external format
-        // for using it on right menus realy
+        // for using it on right menus really
         // Notice:   We build a property list with 4 entries and set it on result list then.
         //           The while-loop starts with pointer on internal member list lSetupEntries, change to
         //           lUserEntries then and stop after that with NULL!
diff --git a/unotools/source/config/dynamicmenuoptions.cxx b/unotools/source/config/dynamicmenuoptions.cxx
index b432996c76ae..f382cf50e89f 100644
--- a/unotools/source/config/dynamicmenuoptions.cxx
+++ b/unotools/source/config/dynamicmenuoptions.cxx
@@ -133,7 +133,7 @@ class SvtDynMenu
         }
 
         // convert internal list to external format
-        // for using it on right menus realy
+        // for using it on right menus really
         // Notice:   We build a property list with 4 entries and set it on result list then.
         //           The while-loop starts with pointer on internal member list lSetupEntries, change to
         //           lUserEntries then and stop after that with NULL!
diff --git a/unotools/source/config/moduleoptions.cxx b/unotools/source/config/moduleoptions.cxx
index 41b72b55e117..c72fff8ce216 100644
--- a/unotools/source/config/moduleoptions.cxx
+++ b/unotools/source/config/moduleoptions.cxx
@@ -40,11 +40,11 @@
 #include "itemholder1.hxx"
 
 /*-************************************************************************************************************//**
-    @descr          These values are used to define neccessary keys from our configuration management to support
+    @descr          These values are used to define necessary keys from our configuration management to support
                     all functionality of these implementation.
                     It's a fast way to make changes if some keys change his name or location!
 
-                    Property handle are neccessary to specify right position in return list of configuration
+                    Property handle are necessary to specify right position in return list of configuration
                     for asked values. We ask it with a list of properties to get his values. The returned list
                     has the same order like our given name list!
                     e.g.:
@@ -356,7 +356,7 @@ class SvtModuleOptions_Impl : public ::utl::ConfigItem
 
 /*-************************************************************************************************************//**
     @short      default ctor
-    @descr      We open our configuration here and read all neccessary values from it.
+    @descr      We open our configuration here and read all necessary values from it.
                 These values are cached till everyone call Commit(). Then we write changed ones back to cfg.
 
     @seealso    baseclass ConfigItem
@@ -453,7 +453,7 @@ void SvtModuleOptions_Impl::Notify( const css::uno::Sequence< OUString >& )
 void SvtModuleOptions_Impl::Commit()
 {
     // Reserve memory for ALL possible factory properties!
-    // Step over all factories and get her realy changed values only.
+    // Step over all factories and get her really changed values only.
     // Build list of these ones and use it for commit.
     css::uno::Sequence< css::beans::PropertyValue > lCommitProperties( FACTORYCOUNT*PROPERTYCOUNT );
     FactoryInfo*                                    pInfo            = NULL                        ;
@@ -750,7 +750,7 @@ void SvtModuleOptions_Impl::SetFactoryDefaultFilter(       SvtModuleOptions::EFa
 /*-************************************************************************************************************//**
     @short      return list of key names of ouer configuration management which represent our module tree
     @descr      You give use a list of current existing set node names .. and we expand it for all
-                well known properties which are neccessary for this implementation.
+                well known properties which are necessary for this implementation.
                 These full expanded list should be used to get values of this properties.
 
     @seealso    ctor
diff --git a/unotools/source/config/viewoptions.cxx b/unotools/source/config/viewoptions.cxx
index e95053e6ee94..43ac37df1406 100644
--- a/unotools/source/config/viewoptions.cxx
+++ b/unotools/source/config/viewoptions.cxx
@@ -91,8 +91,8 @@ sal_Int32                    SvtViewOptions::m_nRefCount_Windows         =   0
             User must decide which information are useful and which not. We are a container iztem only and doesn't
             know anything about the context.
             But; we support a feature:
-                decision between items with default values (should not realy exist in configuration!)
-                and items with real values - changed by user. So user can suppress saving of realy unused items
+                decision between items with default values (should not really exist in configuration!)
+                and items with real values - changed by user. So user can suppress saving of really unused items
                 to disk - because; defaulted items could be restored on runtime without reading from disk!!!
                 And if only items with valid information was written to cfg - we mustn't read so much and save time.
             So we start with an member m_bDefault=True and reset it to False after first set-call.
@@ -243,7 +243,7 @@ typedef ::boost::unordered_map< OUString                    ,
     @descr          Implement base data container for view options elements.
                     Every item support ALL possible configuration information.
                     But not every superclass should use them! Because some view types don't
-                    have it realy.
+                    have it really.
 
     @attention      We implement a write-througt-cache! We use it for reading - but write all changes directly to
                     configuration. (changes are made on internal cache too!). So it's easier to distinguish
@@ -343,8 +343,8 @@ SvtViewOptionsBase_Impl::SvtViewOptionsBase_Impl( const OUString& sList )
     @short          dtor
     @descr          clean up something
 
-    @attention      We implement a write through cache! So we mustn't do it realy. All changes was written to cfg directly.
-                    Commit isn't neccessary then.
+    @attention      We implement a write through cache! So we mustn't do it really. All changes was written to cfg directly.
+                    Commit isn't necessary then.
 
     @seealso        baseclass ::utl::ConfigItem
     @seealso        method IsModified()