diff --git a/TODO b/TODO index 0df3aefc393..9712fc184ec 100644 --- a/TODO +++ b/TODO @@ -48,7 +48,7 @@ Features: * add a switch to homectl (maybe called --first-boot) where it will check if any non-system users exist, and if not prompts interactively for basic user - info, mimicing systemd-firstboot. Then, place this in a service that runs + info, mimicking systemd-firstboot. Then, place this in a service that runs after systemd-homed, but before gdm and friends, as a simple, barebones fallback logic to get a regular user created on uninitialized systems. diff --git a/man/org.freedesktop.portable1.xml b/man/org.freedesktop.portable1.xml index 46dca55745c..93b65acccad 100644 --- a/man/org.freedesktop.portable1.xml +++ b/man/org.freedesktop.portable1.xml @@ -185,7 +185,7 @@ node /org/freedesktop/portable1 { GetImageMetadataWithExtensions() retrieves metadata associated with an image. This method is a superset of GetImageMetadata() with the addition of - a list of extensions as input parameter, which were overlayed on top of the main + a list of extensions as input parameter, which were overlaid on top of the main image via AttachImageWithExtensions(). The flag parameter is currently unused and reserved for future purposes. @@ -239,7 +239,7 @@ node /org/freedesktop/portable1 { AttachImageWithExtensions() attaches a portable image to the system. This method is a superset of AttachImage() with the addition of - a list of extensions as input parameter, which will be overlayed on top of the main + a list of extensions as input parameter, which will be overlaid on top of the main image. When this method is used, detaching must be done by passing the same arguments via the DetachImageWithExtensions() method. For more details on this functionality, see the MountImages= entry on @@ -261,7 +261,7 @@ node /org/freedesktop/portable1 { DetachImageWithExtensions() detaches a portable image from the system. This method is a superset of DetachImage() with the addition of - a list of extensions as input parameter, which were overlayed on top of the main + a list of extensions as input parameter, which were overlaid on top of the main image via AttachImageWithExtensions(). The flag parameter is currently unused and reserved for future purposes. @@ -276,7 +276,7 @@ node /org/freedesktop/portable1 { ReattachImageWithExtensions() reattaches a portable image to the system. This method is a superset of ReattachImage() with the addition of - a list of extensions as input parameter, which will be overlayed on top of the main + a list of extensions as input parameter, which will be overlaid on top of the main image. For more details on this functionality, see the MountImages= entry on systemd.exec5 and systemd-sysext8. diff --git a/man/os-release.xml b/man/os-release.xml index e8462500f20..cda07793033 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -352,9 +352,9 @@ A lower-case string (no spaces or other characters outside of 0–9, a–z, ".", "_" and "-"), identifying a specific image of the operating system. This is supposed to be used for environments where OS images are prepared, built, shipped and updated as comprehensive, consistent OS - images. This field is optional and may not be implemented on all systems, in particulary not on those + images. This field is optional and may not be implemented on all systems, in particularly not on those that are not managed via images but put together and updated from individual packages and on the - local system. Examples: IMAGE_ID=vendorx-cashier-system, + local system. Examples: IMAGE_ID=vendorx-cashier-system, IMAGE_ID=netbook-image diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml index 707905f1ba9..8719ddaae9f 100644 --- a/man/systemd-coredump.xml +++ b/man/systemd-coredump.xml @@ -359,7 +359,7 @@ flags: ... If the executable contained .package metadata ELF notes, they will be parsed and attached. The package and packageVersion - of the 'main' ELF module (ie: the excutable) will be appended individually. The + of the 'main' ELF module (ie: the executable) will be appended individually. The JSON-formatted content of all modules will be appended as a single JSON object, each with the module name as the key. For more information about this metadata format and content, see the coredump metadata spec.