summaryrefslogtreecommitdiff
path: root/offapi
diff options
context:
space:
mode:
authorJulien Nabet <serval2412@yahoo.fr>2014-02-06 21:22:42 +0100
committerJulien Nabet <serval2412@yahoo.fr>2014-02-06 21:22:42 +0100
commit6f0e7c36e436c66ed267ea446b7d640033bc3742 (patch)
tree88006cc5def5e5dfefe7c005438173fddfa0f8d9 /offapi
parent668fefcea085f39a6fa610b93a712c5e250ccf1a (diff)
Typo: seam(s) -> seem(s)
Change-Id: I840d120644760b61a39ad88b4095056f0f753bb7
Diffstat (limited to 'offapi')
-rw-r--r--offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl2
-rw-r--r--offapi/com/sun/star/document/FilterFactory.idl2
-rw-r--r--offapi/com/sun/star/document/TypeDetection.idl2
-rw-r--r--offapi/com/sun/star/frame/ProtocolHandler.idl2
4 files changed, 4 insertions, 4 deletions
diff --git a/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl b/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
index 949f425f12c9..4f9b7c61fa36 100644
--- a/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
+++ b/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
@@ -109,7 +109,7 @@ published service ExtendedTypeDetectionFactory
<p>
Because the complexness of such configuration set can be very high,
- it seams not very useful to update the underlying configuration layer
+ it seems not very useful to update the underlying configuration layer
on every container change request immediately. Another strategy can be to
make all changes (adding/changing/removing of items) and call flush at the end.
That will validate the whole container and reject inconsistent data sets.
diff --git a/offapi/com/sun/star/document/FilterFactory.idl b/offapi/com/sun/star/document/FilterFactory.idl
index 240ff08304b4..59a17ed98c16 100644
--- a/offapi/com/sun/star/document/FilterFactory.idl
+++ b/offapi/com/sun/star/document/FilterFactory.idl
@@ -206,7 +206,7 @@ published service FilterFactory
<p>
Because the complexness of such configuration set can be very high,
- it seams not very useful to update the underlying configuration layer
+ it seems not very useful to update the underlying configuration layer
on every container change request immediately. Another strategy can be to
make all changes (adding/changing/removing of items) and call flush at the end.
That will validate the whole container and reject inconsistent data sets.
diff --git a/offapi/com/sun/star/document/TypeDetection.idl b/offapi/com/sun/star/document/TypeDetection.idl
index 1fd3eac9fa3f..de5e9c43743f 100644
--- a/offapi/com/sun/star/document/TypeDetection.idl
+++ b/offapi/com/sun/star/document/TypeDetection.idl
@@ -153,7 +153,7 @@ published service TypeDetection
<p>
Because the complexness of such configuration set can be very high,
- it seams not very useful to update the underlying configuration layer
+ it seems not very useful to update the underlying configuration layer
on every container change request immediately. Another strategy can be to
make all changes (adding/changing/removing of items) and call flush at the end.
That will validate the whole container and reject inconsistent data sets.
diff --git a/offapi/com/sun/star/frame/ProtocolHandler.idl b/offapi/com/sun/star/frame/ProtocolHandler.idl
index 59dccd9f68aa..ffdaa315537a 100644
--- a/offapi/com/sun/star/frame/ProtocolHandler.idl
+++ b/offapi/com/sun/star/frame/ProtocolHandler.idl
@@ -66,7 +66,7 @@ published service ProtocolHandler
</p>
<p>
- Please note: if this mechanism is used it seams not useful (nor possible) to implement a ProtocolHandler
+ Please note: if this mechanism is used it seems not useful (nor possible) to implement a ProtocolHandler
as a singleton. Otherwise the implementation can't distinguish between different environments
and her corresponding dispatch requests.
</p>