summaryrefslogtreecommitdiff
path: root/binaryurp/README
diff options
context:
space:
mode:
authorMichael Meeks <michael.meeks@suse.com>2012-11-05 12:30:34 +0000
committerMichael Meeks <michael.meeks@suse.com>2012-11-05 12:30:34 +0000
commited7d5822c0008a7416bd9cc19d6b0c0e58a352ae (patch)
treeb585e877ec58db467209c2e049c6d115b324229a /binaryurp/README
parent4aed4f436cf8e4b0f3f034dfb1d1025b05a61f0a (diff)
cleanup README files.
Convert DOS -> unix newlines. Cleanup and clarify several files.
Diffstat (limited to 'binaryurp/README')
-rw-r--r--binaryurp/README18
1 files changed, 9 insertions, 9 deletions
diff --git a/binaryurp/README b/binaryurp/README
index 05dfc3391450..1f1e088944f6 100644
--- a/binaryurp/README
+++ b/binaryurp/README
@@ -1,9 +1,9 @@
-UNO Remote Protocol (URP). A binary protocol.
-
-UNO provides a protocol called the UNO Remote Protocol (URP) that provides
-a bridge between UNO environments. This bridge allows processes and objects
-to send method calls and to receive return values. UNO objects in different
-environments are connected by way of this interprocess bridge. The underlying
-connection is made through a socket or pipe. Remote UNO objects are connected
-by means of TCP/IP using the high-level protocol of the URP.
-
+UNO Remote Protocol (URP). A binary protocol.
+
+UNO provides a protocol called the UNO Remote Protocol (URP) that provides
+a bridge between UNO environments. This bridge allows processes and objects
+to send method calls and to receive return values. UNO objects in different
+environments are connected by way of this interprocess bridge. The underlying
+connection is made through a socket or pipe. Remote UNO objects are connected
+by means of TCP/IP using the high-level protocol of the URP.
+