summaryrefslogtreecommitdiffstats
path: root/framework/source/inc/loadenv/loadenv.hxx
diff options
context:
space:
mode:
Diffstat (limited to 'framework/source/inc/loadenv/loadenv.hxx')
-rw-r--r--framework/source/inc/loadenv/loadenv.hxx4
1 files changed, 2 insertions, 2 deletions
diff --git a/framework/source/inc/loadenv/loadenv.hxx b/framework/source/inc/loadenv/loadenv.hxx
index 277f75a7779a..87743974ae51 100644
--- a/framework/source/inc/loadenv/loadenv.hxx
+++ b/framework/source/inc/loadenv/loadenv.hxx
@@ -276,7 +276,7 @@ public:
of a "non visible component" only an information about a successfully start
can be provided.
Further it can't be guaranteed, that the internal process runs synchronous.
- Thats why we preferr using of specialized methods afterwards e.g. to:
+ that's why we prefer using of specialized methods afterwards e.g. to:
- wait till the internal job will be finished
and get the results
- or to let it run without any further control from outside.
@@ -478,7 +478,7 @@ private:
<li>and(!) this target must not be already used by any other load request.</li>
</ul>
- If a suitable target is located it will be locked. Thats why the last rule
+ If a suitable target is located it will be locked. That's why the last rule
exists! If this method returns a valid frame reference, it was locked to be useable
for this load request only. (Don't forget to reset this state later!)
Concurrent LoadEnv instances can synchronize her work be using such locks :-) HOPEFULLY