summaryrefslogtreecommitdiff
path: root/offapi/com/sun/star/ucb/HierarchyDataSource.idl
diff options
context:
space:
mode:
Diffstat (limited to 'offapi/com/sun/star/ucb/HierarchyDataSource.idl')
-rw-r--r--offapi/com/sun/star/ucb/HierarchyDataSource.idl4
1 files changed, 2 insertions, 2 deletions
diff --git a/offapi/com/sun/star/ucb/HierarchyDataSource.idl b/offapi/com/sun/star/ucb/HierarchyDataSource.idl
index 4e920f8113fa..8f7001710a28 100644
--- a/offapi/com/sun/star/ucb/HierarchyDataSource.idl
+++ b/offapi/com/sun/star/ucb/HierarchyDataSource.idl
@@ -78,11 +78,11 @@ published service HierarchyDataSource
must accept a property named <code>nodepath</code> of type
<atom>string</atom>. This property must contain the absolute path to an
element of the data. The view that is selected consists of the named
- element and all its decendants. A path consists of segments that are
+ element and all its descendants. A path consists of segments that are
separated by a single slash ('/'). There is neither a leading nor a
trailing slash allowed. The <b>root</b> of the hierarchy data always
has an empty path. Refer to <type>HierarchyDataReadAccess</type> for
- more informtion on hierarchical names.
+ more information on hierarchical names.
<p>Other arguments can be used to control the behavior of the view.
These are different for different implementations. Whether and how they