diff options
-rw-r--r-- | sax/source/fastparser/fastparser.cxx | 2 | ||||
-rw-r--r-- | vcl/README.lifecycle | 2 | ||||
-rw-r--r-- | vcl/source/filter/jpeg/transupp.c | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/sax/source/fastparser/fastparser.cxx b/sax/source/fastparser/fastparser.cxx index 8cec8284abce..f35e56e8ab7f 100644 --- a/sax/source/fastparser/fastparser.cxx +++ b/sax/source/fastparser/fastparser.cxx @@ -467,7 +467,7 @@ void Entity::startElement( Event const *pEvent ) if( xContext.is() ) xContext->startFastElement( nElementToken, xAttr ); } - // swap the reference we own in to avoid referencing trash. + // swap the reference we own in to avoid referencing thrash. maContextStack.top().mxContext = std::move( xContext ); } catch (...) diff --git a/vcl/README.lifecycle b/vcl/README.lifecycle index 0c44fb6a14d8..a309b65ef9ea 100644 --- a/vcl/README.lifecycle +++ b/vcl/README.lifecycle @@ -42,7 +42,7 @@ to lingering pointers to freed objects. To fix this situation we now have a VclPtr - which is a smart reference-counting pointer (include/vcl/vclptr.hxx) which is designed to look and behave -very- much like a normal pointer - to reduce code-trash. VclPtr is used to wrap all OutputDevice + to reduce code-thrash. VclPtr is used to wrap all OutputDevice derived classes thus: VclPtr<Dialog> pDialog( new Dialog( ... ), SAL_NO_ACQUIRE ); diff --git a/vcl/source/filter/jpeg/transupp.c b/vcl/source/filter/jpeg/transupp.c index 318b28d790c1..d26cb9510009 100644 --- a/vcl/source/filter/jpeg/transupp.c +++ b/vcl/source/filter/jpeg/transupp.c @@ -60,7 +60,7 @@ jdiv_round_up (long a, long b) * arrays are always written in normal scan order (top to bottom) because * the virtual array manager expects this. The source arrays will be scanned * in the corresponding order, which means multiple passes through the source - * arrays for most of the transforms. That could result in much trashing + * arrays for most of the transforms. That could result in much thrashing * if the image is larger than main memory. * * If cropping or trimming is involved, the destination arrays may be smaller |