diff options
author | Jan Engelhardt <jengelh@inai.de> | 2014-08-03 07:11:12 +0200 |
---|---|---|
committer | Jan Engelhardt <jengelh@inai.de> | 2015-11-06 13:00:02 +0100 |
commit | b938cb902c3b5bca807a94b277672c64d6767886 (patch) | |
tree | 267bd1d61268865fa405b3e5a3027041f7f3a183 /man/sd_bus_message_append_array.xml | |
parent | a6bff4a7428b9539d85618e3c91fcb60be93f3fa (diff) |
doc: correct punctuation and improve typography in documentation
Diffstat (limited to 'man/sd_bus_message_append_array.xml')
-rw-r--r-- | man/sd_bus_message_append_array.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man/sd_bus_message_append_array.xml b/man/sd_bus_message_append_array.xml index 37cadb9d0f..656ad4846d 100644 --- a/man/sd_bus_message_append_array.xml +++ b/man/sd_bus_message_append_array.xml @@ -142,7 +142,7 @@ process. Not all protocol transports support passing memory file descriptors between participants, in which case this call will automatically fall back to copying. Also, as memory file - descriptor passing is inefficient for smaller amounts of data + descriptor passing is inefficient for smaller amounts of data, copying might still be enforced even where memory file descriptor passing is supported.</para> @@ -150,13 +150,13 @@ function appends an array of a trivial type to the message <parameter>m</parameter>, similar to <function>sd_bus_message_append_array()</function>. Contents of - the IO vector array <parameter>iov</parameter> are used as the + the I/O vector array <parameter>iov</parameter> are used as the contents of the array. The total size of <parameter>iov</parameter> payload (the sum of <structfield>iov_len</structfield> fields) must be a multiple of the size of the type <parameter>type</parameter>. The <parameter>iov</parameter> argument must point to - <parameter>n</parameter> IO vector structures. Each structure may + <parameter>n</parameter> I/O vector structures. Each structure may have the <structname>iov_base</structname> field set, in which case the memory pointed to will be copied into the message, or unset (set to zero), in which case a block of zeros of length @@ -173,7 +173,7 @@ <parameter>p</parameter>. The caller should subsequently write the array contents to this memory. Modifications of the memory pointed to should only occur until the next operation on the bus - message is invoked, most importantly the memory should not be + message is invoked. Most importantly, the memory should not be altered anymore when another field has been added to the message or the message has been sealed.</para> </refsect1> |