source code comments and docs: fix typos, language, Markdown layout

- fix a/an before noun
- fix loose -> lose
- fix "the the"
- fix lets -> let's
- fix Markdown layout
- fix a few typos
- remove unnecessary text in troubleshooting.md

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

docs/source/markdown/options/secret.md

@@ -21,7 +21,7 @@ Secret Options
 
 - `type=mount|env`    : How the secret is exposed to the container.
                         `mount` mounts the secret into the container as a file.
-                        `env` exposes the secret as a environment variable.
+                        `env` exposes the secret as an environment variable.
                         Defaults to `mount`.
 - `target=target`     : Target of secret.
                         For mounted secrets, this is the path to the secret inside the container.

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

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

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

@@ -146,7 +146,7 @@ $ podman network create --subnet 192.168.33.0/24 --gateway 192.168.33.3 newnet
 newnet
 ```
 
-Create a network that uses a *192.168.55.0/24** subnet and has an IP address range of *192.168.55.129 - 192.168.55.254*.
+Create a network that uses a *192.168.55.0/24* subnet and has an IP address range of *192.168.55.129 - 192.168.55.254*.
 ```
 $ podman network create --subnet 192.168.55.0/24 --ip-range 192.168.55.128/25
 podman5

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

@@ -12,7 +12,7 @@ The network command manages networks for Podman.
 Podman supports two network backends [Netavark](https://github.com/containers/netavark)
 and [CNI](https://www.cni.dev/). Netavark is the default network backend and was added in Podman v4.0. CNI will be deprecated in the future in preference of
 Netavark. To configure
-the network backend use the `network_backend`key under the `[Network]` in
+the network backend use the `network_backend` key under the `[Network]` in
 **[containers.conf(5)](https://github.com/containers/common/blob/main/docs/containers.conf.5.md)**.
 New systems use netavark by default, to check what backend is used run
 `podman info --format {{.Host.NetworkBackend}}`.

docs/source/markdown/podman-systemd.unit.5.md

@@ -358,7 +358,7 @@ By default, Podman is run in such a way that the systemd startup notify command
 the container runtime. In other words, the service is deemed started when the container runtime
 starts the child in the container. However, if the container application supports
 [sd_notify](https://www.freedesktop.org/software/systemd/man/sd_notify.html), then setting
-`Notify`to true passes the notification details to the container allowing it to notify
+`Notify` to true passes the notification details to the container allowing it to notify
 of startup on its own.
 
 ### `PodmanArgs=`

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

@@ -84,7 +84,7 @@ $ podman volume create --label foo=bar myvol
 
 ## QUOTAS
 
-podman volume create uses `XFS project quota controls` for controlling the size and the number of inodes of builtin volumes. The directory used to store the volumes must be an`XFS` file system and be mounted with the `pquota` option.
+podman volume create uses `XFS project quota controls` for controlling the size and the number of inodes of builtin volumes. The directory used to store the volumes must be an `XFS` file system and be mounted with the `pquota` option.
 
 Example /etc/fstab entry:
 ```