summaryrefslogtreecommitdiff
path: root/offapi/com/sun/star/accessibility/XAccessible.idl
diff options
context:
space:
mode:
Diffstat (limited to 'offapi/com/sun/star/accessibility/XAccessible.idl')
-rw-r--r--offapi/com/sun/star/accessibility/XAccessible.idl4
1 files changed, 2 insertions, 2 deletions
diff --git a/offapi/com/sun/star/accessibility/XAccessible.idl b/offapi/com/sun/star/accessibility/XAccessible.idl
index 889edeccc9b7..edfce5e85dcb 100644
--- a/offapi/com/sun/star/accessibility/XAccessible.idl
+++ b/offapi/com/sun/star/accessibility/XAccessible.idl
@@ -43,7 +43,7 @@ module com { module sun { module star { module accessibility {
<type>XAccessibleContext</type> makes it possible to split up the
implementation of the
class that is made accessible and the actual accessibility code into two
- (mostly) independant parts. The only necessary dependance is the
+ (mostly) independent parts. The only necessary dependence is the
<member scope="XAccessible">getAccessibleContext()</member> function
that returns the accessible context. This one-way link has to be
persistant in some sense: As long as there is at least one reference to
@@ -63,7 +63,7 @@ published interface XAccessible : ::com::sun::star::uno::XInterface
<p>The idea to let this interface only return an
<type>XAccessibleContext</type> instead of directly supporting its
- functions is to allow the seperation of the implementation of the
+ functions is to allow the separation of the implementation of the
functions that make a class accessible from the implementation of
that class. You may, of course, implement <type>XAccessible</type>
and <type>XAccessibleContext</type> in one class.</p>