From d9f87277a63ebc4e194eae84e700d7e9bfe80763 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Tue, 12 Jun 2018 16:19:21 +0200 Subject: [PATCH] doc: more spelling fixes --- man/portablectl.xml | 8 ++++---- man/sd_bus_request_name.xml | 2 +- man/sd_bus_slot_set_floating.xml | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/man/portablectl.xml b/man/portablectl.xml index 1ed57e861..91c048e00 100644 --- a/man/portablectl.xml +++ b/man/portablectl.xml @@ -196,7 +196,7 @@ By default all unit files whose names start with a prefix generated from the image's file name are copied out. Specifically, the prefix is determined from the image file name with any suffix such as - .raw removed, truncated at the first occurence of and underscore character + .raw removed, truncated at the first occurrence of and underscore character (_), if there is one. The underscore logic is supposed to be used to versioning so that the an image file foobar_47.11.raw will result in a unit file matching prefix of foobar. This prefix is then compared with all unit files names contained in the image in @@ -269,7 +269,7 @@ - Like , but the the unit files have been made available transiently only, i.e. the attach command has been invoked with the option. + Like , but the unit files have been made available transiently only, i.e. the attach command has been invoked with the option. @@ -306,12 +306,12 @@ remove IMAGE… Removes one or more portable service images. Note that this command will only remove the - specified image path itself — it it refers to a symbolic link then the symbolic link is removed and not the + specified image path itself — it refers to a symbolic link then the symbolic link is removed and not the image it points to. - set-limit [NAME] BYTES + set-limit [IMAGE] BYTES Sets the maximum size in bytes that a specific portable service image, or all images, may grow up to on disk (disk quota). Takes either one or two parameters. The first, optional parameter refers to a diff --git a/man/sd_bus_request_name.xml b/man/sd_bus_request_name.xml index 5da6e2e62..1b76fe133 100644 --- a/man/sd_bus_request_name.xml +++ b/man/sd_bus_request_name.xml @@ -111,7 +111,7 @@ sd_bus_request_name() operates in a synchronous fashion: a message requesting the name is sent to the bus broker, and the call waits until the broker responds. - sd_bus_request_name_async() is an asynchronous version of of + sd_bus_request_name_async() is an asynchronous version of sd_bus_release_name(). Instead of waiting for the request to complete, the request message is enqueued. The specified callback will be called when the broker's response is received. If the parameter is specified as NULL a default implementation is used instead which will diff --git a/man/sd_bus_slot_set_floating.xml b/man/sd_bus_slot_set_floating.xml index ae733e95d..a2a134e9f 100644 --- a/man/sd_bus_slot_set_floating.xml +++ b/man/sd_bus_slot_set_floating.xml @@ -50,7 +50,7 @@ itself and is freed automatically when the bus object is freed. Regular (i.e. non-floating) bus slot objects keep the bus referenced, hence the bus object remains allocated at least as long as there remains at least one referenced bus slot object around. The floating state hence controls the direction of referencing between the bus - object and the bus slot objects: if floating the bus pins the the bus slot, and otherwise the bus slot pins the bus + object and the bus slot objects: if floating the bus pins the bus slot, and otherwise the bus slot pins the bus objects. Use sd_bus_slot_set_floating() to switch between both modes: if the b parameter is zero, the slot object is considered floating, otherwise it is made a regular (non-floating) slot object. -- 2.30.2