docs: fix typos

diff --git a/docs/PORTABLE_SERVICES.md b/docs/PORTABLE_SERVICES.md
index 036b46217a19f578b6e35fc02226f2ef892bfbb3..1766865fe0f1d50c38f979d73806fac4aa389224 100644 (file)
--- a/docs/PORTABLE_SERVICES.md
+++ b/docs/PORTABLE_SERVICES.md
@@ -259,7 +259,7 @@ portable services can share the same 'runtime' image (libraries, tools) without
 having to include everything each time, with the layering happening only at runtime.
 The `--extension` parameter of `portablectl` can be used to specify as many upper
 layers as desired.
-On top of the requirements listed in the previous section, the following must be also be observed:
+On top of the requirements listed in the previous section, the following must also be observed:
 
 1. The base/OS image must contain an `os-release file`, either in `/etc/os-release`
    or `/usr/lib/os-release`, in the standard format.
@@ -330,7 +330,7 @@ services copied onto the host.
 Several fields are autotmatically added to log messages generated by a portable
 service (or about a portable service, e.g.: start/stop logs from systemd).
 The `PORTABLE=` field will refer to the name of the portable image where the unit
-was loaded from. In case extensions are used, additionally there will be a `PORTABLE_ROOT=` field, referring to the name of image used as the base layer (i.e.: `RootImage=` or `RootDirectory=`), and one `PORTABLE_EXTENSION=` field per
+was loaded from. In case extensions are used, additionally there will be a `PORTABLE_ROOT=` field, referring to the name of the image used as the base layer (i.e.: `RootImage=` or `RootDirectory=`), and one `PORTABLE_EXTENSION=` field for
 each extension image used.
 
 The `os-release` file from the portable image will be parsed and added as structured metadata to the journal log entries.
@@ -339,7 +339,7 @@ The ID and version, if any, are concatenated with an underscore (`_`) as separat
 If only either one is found, it will be used by itself.
 The field will be named `PORTABLE_NAME_AND_VERSION=`.
 
-In case extensions are used, the same fields in the same order are, but prefixed by
+In case extensions are used, the same fields in the same order, but prefixed by
 `SYSEXT_`/`CONFEXT_`, are parsed from each `extension-release` file, and are appended
 to the journal as log entries, using `PORTABLE_EXTENSION_NAME_AND_VERSION=` as the field name.
 The base layer's field will be named `PORTABLE_ROOT_NAME_AND_VERSION=` instead of `PORTABLE_NAME_AND_VERSION=` in this case.