summaryrefslogtreecommitdiff
path: root/offapi/com/sun/star/sdb/tools/XObjectNames.idl
diff options
context:
space:
mode:
Diffstat (limited to 'offapi/com/sun/star/sdb/tools/XObjectNames.idl')
-rw-r--r--offapi/com/sun/star/sdb/tools/XObjectNames.idl8
1 files changed, 4 insertions, 4 deletions
diff --git a/offapi/com/sun/star/sdb/tools/XObjectNames.idl b/offapi/com/sun/star/sdb/tools/XObjectNames.idl
index 16b2bae93baa..e636631339af 100644
--- a/offapi/com/sun/star/sdb/tools/XObjectNames.idl
+++ b/offapi/com/sun/star/sdb/tools/XObjectNames.idl
@@ -46,12 +46,12 @@ module com { module sun { module star { module sdb { module tools {
<p>The most important task fulfilled by this instance is that it hides
different naming restrictions from you, which are caused by server-side
- or client side specialities.</p>
+ or client side specialties.</p>
<p>For instance, it can validate names against
the characters allowed in the object names of a connection. Also, it
relieves you from caring whether a database supports queries in a <code>SELECT</code>
- statment's <code>FROM</code> part (known as "queries in queries"). In such
+ statement's <code>FROM</code> part (known as "queries in queries"). In such
databases, query and table names share a common namespace, thus they must be
unique. Using this interface, you can easily ensure this uniqueness.</p>
@@ -59,7 +59,7 @@ module com { module sun { module star { module sdb { module tools {
thus it entry point for obtaining it is a <type scope="com::sun::star::sdb">Connection</type>
service.</p>
- <p>The component itself does not have life-time control mechanimns, i.e. you
+ <p>The component itself does not have life-time control mechanisms, i.e. you
cannot explicitly dispose it (<member scope="com::sun::star::lang">XComponent::dispose</member>),
and you cannot be notified when it dies.<br/>
However, if your try to access any of its methods or attributes, after the
@@ -79,7 +79,7 @@ interface XObjectNames
<p>Note that in an multi-threaded environment, the name you obtain here is not absolutely
guaranteed to be unique. It is unique at the very moment the function returns to you.
- But already when you evaluate the returned value, it might not be uniquey anymore, if
+ But already when you evaluate the returned value, it might not be unique anymore, if
another process or thread created a query or table with this name.</p>
<p>This implies that you cannot rely on the name's uniqueness, but you can use it as