[CI:DOCS] Fix typos and improve language

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>

docs/source/markdown/podman-attach.1.md

@@ -10,7 +10,7 @@ podman\-attach - Attach to a running container
 
 ## DESCRIPTION
 **podman attach** attaches to a running *container* using the *container's name* or *ID*, to either view its ongoing output or to control it interactively.\
-The *container* can detached from (and leave it running) using a configurable key sequence. The default sequence is `ctrl-p,ctrl-q`. Configure the keys sequence using the **--detach-keys** OPTION, or specifying it in the `containers.conf` file: see **[containers.conf(5)](https://github.com/containers/common/blob/master/docs/containers.conf.5.md)** for more information.
+The *container* can be detached from (and leave it running) using a configurable key sequence. The default sequence is `ctrl-p,ctrl-q`. Configure the keys sequence using the **--detach-keys** OPTION, or specifying it in the `containers.conf` file: see **[containers.conf(5)](https://github.com/containers/common/blob/master/docs/containers.conf.5.md)** for more information.
 
 ## OPTIONS
 #### **--detach-keys**=**sequence**

docs/source/markdown/podman-build.1.md

@@ -29,7 +29,7 @@ still be used by other tools when manually preprocessing them via `cpp -E`.
 When the URL is an archive, the contents of the URL is downloaded to a temporary
 location and extracted before execution.
 
-When the URL is an Containerfile, the Containerfile is downloaded to a temporary
+When the URL is a Containerfile, the Containerfile is downloaded to a temporary
 location.
 
 When a Git repository is set as the URL, the repository is cloned locally and
@@ -364,7 +364,7 @@ Add an image *label* (e.g. label=*value*) to the image metadata. Can be used
 multiple times.
 
 Users can set a special LABEL **io.containers.capabilities=CAP1,CAP2,CAP3** in
-a Containerfile that specified the list of Linux capabilities required for the
+a Containerfile that specifies the list of Linux capabilities required for the
 container to run properly. This label specified in a container image tells
 Podman to run the container with just these capabilities. Podman launches the
 container with just the specified capabilities, as long as this list of
@@ -711,7 +711,7 @@ than being relative to the host as it would be when run rootfull.
 
 #### **--uts**=*how*
 
-Sets the configuration for UTS namespaces when the handling `RUN` instructions.
+Sets the configuration for UTS namespaces when handling `RUN` instructions.
 The configured value can be "" (the empty string) or "container" to indicate
 that a new UTS namespace should be created, or it can be "host" to indicate
 that the UTS namespace in which `podman` itself is being run should be reused,

docs/source/markdown/podman-container-exists.1.md

@@ -23,21 +23,21 @@ The default is **false**.
 
 ## EXAMPLES
 
-Check if an container called "webclient" exists in local storage. Here, the container does exist.
+Check if a container called "webclient" exists in local storage. Here, the container does exist.
 ```
 $ podman container exists webclient
 $ echo $?
 0
 ```
 
-Check if an container called "webbackend" exists in local storage. Here, the container does not exist.
+Check if a container called "webbackend" exists in local storage. Here, the container does not exist.
 ```
 $ podman container exists webbackend
 $ echo $?
 1
 ```
 
-Check if an container called "ubi8-working-container" created via Buildah exists in local storage. Here, the container does not exist.
+Check if a container called "ubi8-working-container" created via Buildah exists in local storage. Here, the container does not exist.
 ```
 $ podman container exists --external ubi8-working-container
 $ echo $?

docs/source/markdown/podman-create.1.md

@@ -127,7 +127,7 @@ If the host uses cgroups v1, the default is set to **host**. On cgroups v2 the d
 #### **--cgroups**=*mode*
 
 Determines whether the container will create CGroups.
-Valid values are *enabled*, *disabled*, *no-conmon*, *split*, which the default being *enabled*.
+Valid values are *enabled*, *disabled*, *no-conmon*, *split*, with the default being *enabled*.
 
 The *enabled* option will create a new cgroup under the cgroup-parent.
 The *disabled* option will force the container to not create CGroups, and thus conflicts with CGroup options (**--cgroupns** and **--cgroup-parent**).
@@ -308,7 +308,7 @@ Set custom DNS servers. Invalid if using **--dns** and **--network** that is set
 This option can be used to override the DNS
 configuration passed to the container. Typically this is necessary when the
 host DNS configuration is invalid for the container (e.g., 127.0.0.1). When this
-is the case the **--dns** flags is necessary for every run.
+is the case the **--dns** flag is necessary for every run.
 
 The special value **none** can be specified to disable creation of **/etc/resolv.conf** in the container by Podman.
 The **/etc/resolv.conf** file in the image will be used without changes.
@@ -695,7 +695,7 @@ Valid _mode_ values are:
   - **alias=name**: Add network-scoped alias for the container.
   - **ip=IPv4**: Specify a static ipv4 address for this container.
   - **ip=IPv6**: Specify a static ipv6 address for this container.
-  - **mac=MAC**: Specify a static mac address address for this container.
+  - **mac=MAC**: Specify a static mac address for this container.
   - **interface_name**: Specify a name for the created network interface inside the container.
 
   For example to set a static ipv4 address and a static mac address, use `--network bridge:ip=10.88.0.10,mac=44:33:22:11:00:99`.
@@ -715,7 +715,7 @@ Valid _mode_ values are:
   - **outbound_addr6=INTERFACE**: Specify the outbound interface slirp should bind to (ipv6 traffic only).
   - **outbound_addr6=IPv6**: Specify the outbound ipv6 address slirp should bind to.
   - **port_handler=rootlesskit**: Use rootlesskit for port forwarding. Default.
-  Note: Rootlesskit changes the source IP address of incoming packets to a IP address in the container network namespace, usually `10.0.2.100`. If your application requires the real source IP address, e.g. web server logs, use the slirp4netns port handler. The rootlesskit port handler is also used for rootless containers when connected to user-defined networks.
+  Note: Rootlesskit changes the source IP address of incoming packets to an IP address in the container network namespace, usually `10.0.2.100`. If your application requires the real source IP address, e.g. web server logs, use the slirp4netns port handler. The rootlesskit port handler is also used for rootless containers when connected to user-defined networks.
   - **port_handler=slirp4netns**: Use the slirp4netns port forwarding, it is slower than rootlesskit but preserves the correct source IP address. This port handler cannot be used for user-defined networks.
 
 #### **--network-alias**=*alias*
@@ -1028,7 +1028,7 @@ Podman will setup tmpfs mount points in the following directories:
 
 It will also set the default stop signal to SIGRTMIN+3.
 
-This allow systemd to run in a confined container without any modifications.
+This allows systemd to run in a confined container without any modifications.
 
 Note: On `SELinux` systems, systemd attempts to write to the cgroup
 file system. Containers writing to the cgroup file system are denied by default.
@@ -1307,7 +1307,7 @@ Only the current container can use a private volume.
 
 Note: Do not relabel system files and directories. Relabeling system content
 might cause other confined services on your machine to fail.  For these types
-of containers we recommend that disable SELinux separation.  The option
+of containers we recommend disabling SELinux separation.  The option
 `--security-opt label=disable` disables SELinux separation for containers used in the build.
 For example if a user wanted to volume mount their entire home directory into a
 container, they need to disable SELinux separation.
@@ -1372,7 +1372,7 @@ the volume will not be able to change their privilege. By default volumes
 are mounted with `nosuid`.
 
 Mounting the volume with the noexec option means that no executables on the
-volume will be able to executed within the container.
+volume will be able to be executed within the container.
 
 Mounting the volume with the nodev option means that no devices on the volume
 will be able to be used by processes within the container. By default volumes
@@ -1540,7 +1540,7 @@ $ podman create --network net1:ip=10.89.1.5 --network net2:ip=10.89.10.10 alpine
 
 ### Rootless Containers
 
-Podman runs as a non root user on most systems. This feature requires that a new enough version of shadow-utils
+Podman runs as a non-root user on most systems. This feature requires that a new enough version of shadow-utils
 be installed. The shadow-utils package must include the newuidmap and newgidmap executables.
 
 Note: RHEL7 and Centos 7 will not have this feature until RHEL7.7 is released.

docs/source/markdown/podman-generate-kube.1.md

@@ -6,7 +6,7 @@ podman-generate-kube - Generate Kubernetes YAML based on containers, pods or vol
 **podman generate kube** [*options*] *container...* | *pod...* | *volume...*
 
 ## DESCRIPTION
-**podman generate kube** will generate Kubernetes YAML (v1 specification) from Podman containers, pods or volumes. Whether
+**podman generate kube** will generate Kubernetes YAML (v1 specification) from Podman containers, pods or volumes. Regardless of whether
 the input is for containers or pods, Podman will always generate the specification as a Pod. The input may be in the form
 of one or more containers, pods or volumes names or IDs.
 

docs/source/markdown/podman-image-sign.1.md

@@ -56,7 +56,7 @@ The write (and read) location for signatures is defined in YAML-based
 configuration files in /etc/containers/registries.d/ for root,
 or $HOME/.config/containers/registries.d for non-root users.  When you sign
 an image, Podman will use those configuration files to determine
-where to write the signature based on the the name of the originating
+where to write the signature based on the name of the originating
 registry or a default storage value unless overridden with the --directory
 option. For example, consider the following configuration file.
 

docs/source/markdown/podman-logs.1.md

@@ -20,7 +20,7 @@ any logs at the time you execute podman logs).
 Follow log output.  Default is false.
 
 Note: If you are following a container which is removed `podman container rm`
-or removed on exit `podman run --rm ...`, then there is a chance the the log
+or removed on exit `podman run --rm ...`, then there is a chance that the log
 file will be removed before `podman logs` reads the final content.
 
 #### **--latest**, **-l**

docs/source/markdown/podman-machine-list.1.md

@@ -39,7 +39,7 @@ Valid placeholders for the Go template are listed below:
 | .VMType         | VM type                         |
 | .Port           | SSH Port to use to connect to VM|
 | .RemoteUsername | VM Username for rootless Podman |
-| .IdentityPath   | Path to ssh identify file       |
+| .IdentityPath   | Path to ssh identity file       |
 
 #### **--help**
 

docs/source/markdown/podman-manifest-push.1.md

@@ -78,22 +78,22 @@ Require HTTPS and verify certificates when talking to container registries. (def
   **dir:**_path_
   An existing local directory _path_ storing the manifest, layer tarballs and signatures as individual files. This is a non-standardized format, primarily useful for debugging or noninvasive container inspection.
 
-    $ podman manfiest push mylist:v1.11 dir:/tmp/mylist
+    $ podman manifest push mylist:v1.11 dir:/tmp/mylist
 
   **docker://**_docker-reference_
   An image in a registry implementing the "Docker Registry HTTP API V2". By default, uses the authorization state in `$XDG_RUNTIME_DIR/containers/auth.json`, which is set using `(podman login)`. If the authorization state is not found there, `$HOME/.docker/config.json` is checked, which is set using `(docker login)`.
 
-    $ podman manfiest push mylist:v1.11 docker://registry.example.org/mylist:v1.11
+    $ podman manifest push mylist:v1.11 docker://registry.example.org/mylist:v1.11
 
   **docker-archive:**_path_[**:**_docker-reference_]
   An image is stored in the `docker save` formatted file.  _docker-reference_ is only used when creating such a file, and it must not contain a digest.
 
-    $ podman manfiest push mylist:v1.11 docker-archive:/tmp/mylist
+    $ podman manifest push mylist:v1.11 docker-archive:/tmp/mylist
 
   **docker-daemon:**_docker-reference_
   An image in _docker-reference_ format stored in the docker daemon internal storage. _docker-reference_ must contain a tag.
 
-    $ podman manfiest push mylist:v1.11 docker-daemon:registry.example.org/mylist:v1.11
+    $ podman manifest push mylist:v1.11 docker-daemon:registry.example.org/mylist:v1.11
 
   **oci-archive:**_path_**:**_tag_
   An image _tag_ in a directory compliant with "Open Container Image Layout Specification" at _path_.

docs/source/markdown/podman-mount.1.md

@@ -14,7 +14,7 @@ accessed from the host, and returns its location.
 
 If you execute the command without any arguments, Podman will list all of the
 currently mounted containers, including external containers. External containers are
-containers in container/storage by tools other then Podman. For example Buildah and
+containers in container/storage by tools other than Podman. For example Buildah and
 CRI-O.
 
 Rootless mode only supports mounting VFS driver, unless you enter the user namespace

docs/source/markdown/podman-network-create.1.md

@@ -39,7 +39,7 @@ Additionally the `bridge` driver supports the following option:
 
 The `macvlan` and `ipvlan` driver support the following options:
 - `parent`: The host device which should be used for the macvlan interface. Defaults to the default route interface.
-- `mode`: This options sets the specified ip/macvlan mode on the interface.
+- `mode`: This option sets the specified ip/macvlan mode on the interface.
   - Supported values for `macvlan` are `bridge`, `private`, `vepa`, `passthru`. Defaults to `bridge`.
   - Supported values for `ipvlan` are `l2`, `l3`, `l3s`. Defaults to `l2`.
 

docs/source/markdown/podman-network-exists.1.md

@@ -29,7 +29,7 @@ $ echo $?
 $
 ```
 
-Check if an network called `webbackend` exists (the network does not actually exist).
+Check if a network called `webbackend` exists (the network does not actually exist).
 ```
 $ podman network exists webbackend
 $ echo $?

docs/source/markdown/podman-play-kube.1.md

@@ -179,7 +179,7 @@ Valid _mode_ values are:
   - **alias=name**: Add network-scoped alias for the container.
   - **ip=IPv4**: Specify a static ipv4 address for this container.
   - **ip=IPv6**: Specify a static ipv6 address for this container.
-  - **mac=MAC**: Specify a static mac address address for this container.
+  - **mac=MAC**: Specify a static mac address for this container.
   - **interface_name**: Specify a name for the created network interface inside the container.
 
   For example to set a static ipv4 address and a static mac address, use `--network bridge:ip=10.88.0.10,mac=44:33:22:11:00:99`.
@@ -198,7 +198,7 @@ Valid _mode_ values are:
   - **outbound_addr6=INTERFACE**: Specify the outbound interface slirp should bind to (ipv6 traffic only).
   - **outbound_addr6=IPv6**: Specify the outbound ipv6 address slirp should bind to.
   - **port_handler=rootlesskit**: Use rootlesskit for port forwarding. Default.
-  Note: Rootlesskit changes the source IP address of incoming packets to a IP address in the container network namespace, usually `10.0.2.100`. If your application requires the real source IP address, e.g. web server logs, use the slirp4netns port handler. The rootlesskit port handler is also used for rootless containers when connected to user-defined networks.
+  Note: Rootlesskit changes the source IP address of incoming packets to an IP address in the container network namespace, usually `10.0.2.100`. If your application requires the real source IP address, e.g. web server logs, use the slirp4netns port handler. The rootlesskit port handler is also used for rootless containers when connected to user-defined networks.
   - **port_handler=slirp4netns**: Use the slirp4netns port forwarding, it is slower than rootlesskit but preserves the correct source IP address. This port handler cannot be used for user-defined networks.
 
 #### **--no-hosts**

docs/source/markdown/podman-pod-logs.1.md

@@ -22,7 +22,7 @@ By default `podman pod logs` retrieves logs for all the containers available wit
 Follow log output.  Default is false.
 
 Note: If you are following a pod which is removed `podman pod rm`, then there is a
-chance the the log file will be removed before `podman pod logs` reads the final content.
+chance that the log file will be removed before `podman pod logs` reads the final content.
 
 #### **--latest**, **-l**
 

docs/source/markdown/podman-pull.1.md

@@ -17,7 +17,7 @@ podman pull copies an image from a registry onto the local machine. The command
 *IMPORTANT: Images are stored in local image storage.*
 
 ## SOURCE
-SOURCE is the location from the container image is pulled from. It supports all transports from **[containers-transports(5)](https://github.com/containers/image/blob/main/docs/containers-transports.5.md)**. If no transport is specified, the input is subject to short-name resolution and the `docker` (i.e., container registry) transport is used.  For remote clients, `docker` is the only supported transport.
+SOURCE is the location from which the container image is pulled from. It supports all transports from **[containers-transports(5)](https://github.com/containers/image/blob/main/docs/containers-transports.5.md)**. If no transport is specified, the input is subject to short-name resolution and the `docker` (i.e., container registry) transport is used.  For remote clients, `docker` is the only supported transport.
 
 ```
 # Pull from a container registry