tree-wide: "human readable" → "human-readable"

Apparently, the spelling with a hyphen is better style in the English
language.

Suggested by: #36165
This commit is contained in:
Lennart Poettering
2025-07-07 11:21:25 +02:00
parent 663108304a
commit d03714e4e4
20 changed files with 32 additions and 32 deletions
+2 -2
View File
@@ -100,9 +100,9 @@ typedef struct BootEntry {
char16_t *id; /* The unique identifier for this entry (typically the filename of the file defining the entry, possibly suffixed with a profile id) */
char16_t *id_without_profile; /* same, but without any profile id suffixed */
char16_t *title_show; /* The string to actually display (this is made unique before showing) */
char16_t *title; /* The raw (human readable) title string of the entry (not necessarily unique) */
char16_t *title; /* The raw (human-readable) title string of the entry (not necessarily unique) */
char16_t *sort_key; /* The string to use as primary sort key, usually ID= from os-release, possibly suffixed */
char16_t *version; /* The raw (human readable) version string of the entry */
char16_t *version; /* The raw (human-readable) version string of the entry */
char16_t *machine_id;
EFI_HANDLE *device;
LoaderType type;
+1 -1
View File
@@ -2393,7 +2393,7 @@ static int unit_log_resources(Unit *u) {
return log_oom();
/* Invoked whenever a unit enters failed or dead state. Logs information about consumed resources if resource
* accounting was enabled for a unit. It does this in two ways: a friendly human readable string with reduced
* accounting was enabled for a unit. It does this in two ways: a friendly human-readable string with reduced
* information and the complete data in structured fields. */
(void) unit_get_cpu_usage(u, &cpu_nsec);
+3 -3
View File
@@ -17,8 +17,8 @@ bool bootspec_pick_name_version_sort_key(
const sd_char *good_name, *good_version, *good_sort_key;
/* Find the best human readable title, version string and sort key for a boot entry (using the
* os-release(5) fields). Precise is preferred over vague, and human readable over machine
/* Find the best human-readable title, version string and sort key for a boot entry (using the
* os-release(5) fields). Precise is preferred over vague, and human-readable over machine
* readable. Thus:
*
* 1. First priority gets the PRETTY_NAME field, which is the primary string intended for display,
@@ -28,7 +28,7 @@ bool bootspec_pick_name_version_sort_key(
* 2. Otherwise we go for IMAGE_ID and IMAGE_VERSION (thus we show details about the image,
* i.e. specific combination of packages and configuration), if that concept applies.
*
* 3. Otherwise we go for NAME and VERSION (i.e. human readable OS name and version)
* 3. Otherwise we go for NAME and VERSION (i.e. human-readable OS name and version)
*
* 4. Otherwise we go for ID and VERSION_ID (i.e. machine readable OS name and version)
*
+1 -1
View File
@@ -19,7 +19,7 @@ typedef enum AskPasswordFlags {
/* Encapsulates the mostly static fields of a password query */
typedef struct AskPasswordRequest {
const char *message; /* The human readable password prompt when asking interactively */
const char *message; /* The human-readable password prompt when asking interactively */
const char *keyring; /* kernel keyring key name (key of "user" type) */
const char *icon; /* freedesktop icon spec name */
const char *id; /* some identifier used for this prompt for the "ask-password" protocol */
+1 -1
View File
@@ -271,7 +271,7 @@ static int systemctl_help(void) {
" For kill, wait until service stopped\n"
" --no-block Do not wait until operation finished\n"
" --no-wall Don't send wall message before halt/power-off/reboot\n"
" --message=MESSAGE Specify human readable reason for system shutdown\n"
" --message=MESSAGE Specify human-readable reason for system shutdown\n"
" --no-reload Don't reload daemon after en-/dis-abling unit files\n"
" --legend=BOOL Enable/disable the legend (column headers and hints)\n"
" --no-pager Do not pipe output into a pager\n"
+3 -3
View File
@@ -189,9 +189,9 @@ int sd_is_mq(int fd, const char *path);
that describes the daemon state. This is free-form
and can be used for various purposes: general state
feedback, fsck-like programs could pass completion
percentages and failing programs could pass a human
readable error message. Example: "STATUS=Completed
66% of file system check..."
percentages and failing programs could pass a
human-readable error message. Example:
"STATUS=Completed 66% of file system check..."
NOTIFYACCESS=...
Reset the access to the service status notification socket.