Resync to trunk, windows non-pro buildaoo/aw080

1 files changed, 8 insertions, 8 deletions

diff --git a/unotools/source/config/viewoptions.cxx b/unotools/source/config/viewoptions.cxx
index 5cb1579b1516..fc9854cd81a2 100644
--- a/unotools/source/config/viewoptions.cxx
+++ b/unotools/source/config/viewoptions.cxx
@@ -122,15 +122,15 @@ sal_Int32                    SvtViewOptions::m_nRefCount_Windows         =   0
 /*-************************************************************************************************************//**
     @descr  declare one configuration item
             These struct hold information about one view item. But not all member are used for all entries!
-            User must decide which information are usefull and which not. We are a container iztem only and doesnt
+            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.
-            Deficiencies of these solution - we cant allow direct read/write access to our member. We must
+            Deficiencies of these solution - we can't allow direct read/write access to our member. We must
             support it by set/get-methods ...
 *//*-*************************************************************************************************************/
 class IMPL_TViewData
@@ -277,7 +277,7 @@ typedef ::std::hash_map< ::rtl::OUString                    ,
     @descr          Implement base data container for view options elements.
                     Every item support ALL possible configuration informations.
                     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
@@ -377,8 +377,8 @@ SvtViewOptionsBase_Impl::SvtViewOptionsBase_Impl( const ::rtl::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()
@@ -394,7 +394,7 @@ SvtViewOptionsBase_Impl::~SvtViewOptionsBase_Impl()
 {
     // dont flush configuration changes here to m_xRoot.
     // That must be done inside every SetXXX() method already !
-    // Here its to late - DisposedExceptions from used configuration access can occure otherwise.
+    // Here its to late - DisposedExceptions from used configuration access can occur otherwise.
 
     m_xRoot.clear();
     m_xSet.clear();