|author||Caolán McNamara <firstname.lastname@example.org>||2019-05-10 09:34:10 +0100|
|committer||Caolán McNamara <email@example.com>||2019-05-10 14:50:59 +0200|
an uno -> a uno
Change-Id: I538db88f8477dd2d2ad25c372928fec6c11d979d Reviewed-on: https://gerrit.libreoffice.org/72105 Tested-by: Jenkins Reviewed-by: Caolán McNamara <firstname.lastname@example.org> Tested-by: Caolán McNamara <email@example.com>
Diffstat (limited to 'winaccessibility')
1 files changed, 1 insertions, 1 deletions
diff --git a/winaccessibility/README b/winaccessibility/README
index a7a8e7a9a8a6..2f507beacc64 100644
@@ -30,7 +30,7 @@ Threading
It's possible that the UNO components are called from threads other
than the main thread, so they have to be synchronized. It would be nice
-to put the component into an UNO apartment (and the COM components into STA)
+to put the component into a UNO apartment (and the COM components into STA)
but UNO would spawn a new thread for it so it's not possible.
The COM components also call into the same global AccObjectWinManager
as the UNO components do so both have to be synchronized in the same way.