tree-wide: "<n>bit" → "<n>-bit"

[thirdparty/systemd.git] / docs / BUILDING_IMAGES.md

diff --git a/docs/BUILDING_IMAGES.md b/docs/BUILDING_IMAGES.md
index 1a96ed00834c14b0d68543e6529005f5e156892a..15ca27845e761ab05771e2285f87083eeb357c28 100644 (file)
--- a/docs/BUILDING_IMAGES.md
+++ b/docs/BUILDING_IMAGES.md
@@ -27,12 +27,12 @@ boot. For that it's essential to:
 1. Remove the
    [`/etc/machine-id`](https://www.freedesktop.org/software/systemd/man/machine-id.html)
    file or write the string `uninitialized\n` into it. This file is supposed to
-   carry a 128bit identifier unique to the system. Only when it is reset it
+   carry a 128-bit identifier unique to the system. Only when it is reset it
    will be auto-generated on first boot and thus be truly unique. If this file
    is not reset, and carries a valid ID every instance of the system will come
    up with the same ID and that will likely lead to problems sooner or later,
    as many network-visible identifiers are commonly derived from the machine
-   ID, for example IPv6 addresses or transient MAC addresses.
+   ID, for example, IPv6 addresses or transient MAC addresses.
 
 2. Remove the `/var/lib/systemd/random-seed` file (see
    [`systemd-random-seed(8)`](https://www.freedesktop.org/software/systemd/man/systemd-random-seed.service.html)),
@@ -83,7 +83,7 @@ which can be a freely chosen string to use for identifying the boot menu
 resources of the OS. If not configured explicitly it defaults to the machine
 ID. The file `/etc/kernel/entry-token` may be used to configure this string
 explicitly. Thus, golden image builders should write a suitable identifier into
-this file, for example the `IMAGE_ID=` or `ID=` field from
+this file, for example, the `IMAGE_ID=` or `ID=` field from
 [`/etc/os-release`](https://www.freedesktop.org/software/systemd/man/os-release.html)
 (also see below). It is recommended to do this before the `kernel-install`
 functionality is invoked (i.e. before the package manager is used to install
@@ -117,7 +117,7 @@ Specifically, the following mechanisms are in place:
 
 4. The
    [`systemd-sysusers(8)`](https://www.freedesktop.org/software/systemd/man/systemd-sysusers.service.html)
-   will component automatically populate `/etc/passwd` and `/etc/group` on
+   component will automatically populate `/etc/passwd` and `/etc/group` on
    first boot with further necessary system users.
 
 5. The
@@ -161,7 +161,7 @@ the OS should take possession of the backing storage as necessary, dynamically
 using available space. Specifically:
 
 1. Additional partitions should be created, that make no sense to ship
-   pre-built in the image. For example `/tmp/` or `/home/` partitions, or even
+   pre-built in the image. For example, `/tmp/` or `/home/` partitions, or even
    `/var/` or the root file system (see above).
 
 2. Additional partitions should be created that shall function as A/B