Add information about --latest support on man pages

On Mac and Windows systems the --latest option is not supported
this PR mentions this fact in the examples section of the man page.
Also added documentation and consistency to the man pages examples
sections.

Signed-off-by: Daniel J Walsh <[email protected]>

Author: rhatdan

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

@@ -31,7 +31,7 @@ Attach to a container called "foobar".
 $ podman attach foobar
 ```
 
-Attach to the latest created container.
+Attach to the latest created container. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
 ```
 $ podman attach --latest
 ```

docs/source/markdown/podman-container-inspect.1.md.in

@@ -74,6 +74,7 @@ In addition to normal output, display the total file size if the type is a conta
 
 ## EXAMPLE
 
+Inspect the specified container and print its information in json format.
 ```
 $ podman container inspect foobar
 [
@@ -305,16 +306,19 @@ $ podman container inspect foobar
 ]
 ```
 
+Inspect the specified container for the Image Name it is based on.
 ```
 $ podman container inspect nervous_fermi --format "{{.ImageName}}"
 registry.access.redhat.com/ubi8:latest
 ```
 
+Inspect the specified container for the GraphDriver Name it is running with.
 ```
 $ podman container inspect foobar --format "{{.GraphDriver.Name}}"
 overlay
 ```
 
+Inspect the latest container created for its EffectiveCaps field. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
 ```
 $ podman container inspect --latest --format {{.EffectiveCaps}}
 [CAP_CHOWN CAP_DAC_OVERRIDE CAP_FOWNER CAP_FSETID CAP_KILL CAP_NET_BIND_SERVICE CAP_SETFCAP CAP_SETGID CAP_SETPCAP CAP_SETUID]

docs/source/markdown/podman-init.1.md.in

@@ -26,17 +26,17 @@ Initialize all containers. Containers that have already initialized (including c
 
 ## EXAMPLE
 
-Initialize container with a given ID
+Initialize specified container with a given ID.
 ```
 podman init 35480fc9d568
 ```
 
-Initialize container with a given name
+Initialize specified container with a given name.
 ```
 podman init test1
 ```
 
-Initialize the latest container created by Podman
+Initialize the latest container. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
 ```
 podman init --latest
 ```

docs/source/markdown/podman-inspect.1.md.in

@@ -35,11 +35,12 @@ In addition to normal output, display the total file size if the type is a conta
 
 #### **--type**, **-t**=*type*
 
-Return JSON for the specified type.  Type can be 'container', 'image', 'volume', 'network', 'pod', or 'all' (default: all)
+Return JSON for the specified type. Type can be 'container', 'image', 'volume', 'network', 'pod', or 'all' (default: all)
 (Only meaningful when invoked as *podman inspect*)
 
 ## EXAMPLE
 
+Inspect the fedora image
 ```
 # podman inspect fedora
 [
@@ -121,35 +122,43 @@ Return JSON for the specified type.  Type can be 'container', 'image', 'volume',
 ]
 ```
 
+Inspect the specified image for Image Name.
 ```
 # podman inspect a04 --format "{{.ImageName}}"
 fedora
 ```
 
+Inspect the specified image for GraphDriver Name.
 ```
 # podman inspect a04 --format "{{.GraphDriver.Name}}"
 overlay
 ```
 
+Inspect the specified image for its Size field.
 ```
 # podman image inspect --format "size: {{.Size}}" alpine
 size:   4405240
 ```
 
+Inspect the latest container created for its EffectiveCaps field. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
 ```
 podman container inspect --latest --format {{.EffectiveCaps}}
 [CAP_CHOWN CAP_DAC_OVERRIDE CAP_FSETID CAP_FOWNER CAP_SETGID CAP_SETUID CAP_SETFCAP CAP_SETPCAP CAP_NET_BIND_SERVICE CAP_KILL]
 ```
 
+Inspect the specified pod for the Name field.
 ```
 # podman inspect myPod --type pod --format "{{.Name}}"
 myPod
 ```
+
+Inspect the specified volume for the Name field.
 ```
 # podman inspect myVolume --type volume --format "{{.Name}}"
 myVolume
 ```
 
+Inspect the specified network for the Name field.
 ```
 # podman inspect nyNetwork --type network --format "{{.name}}"
 myNetwork

docs/source/markdown/podman-kill.1.md.in

@@ -39,7 +39,8 @@ Terminate container by sending `TERM` signal
 podman kill --signal TERM 860a4b23
 ```
 
-Kill the latest container created by Podman
+Kill the latest container. (This option is not available with the remote Podman client, including Mac and Windows
+(excluding WSL2) machines)
 ```
 podman kill --latest
 ```

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

@@ -63,7 +63,7 @@ The Kubernetes kind to generate in the YAML file. Currently, the only supported
 
 ## EXAMPLES
 
-Create Kubernetes Pod YAML for a container called `some-mariadb`.
+Create Kubernetes Pod YAML for the specified container.
 ```
 $ podman kube generate some-mariadb
 # Save the output of this file and use kubectl create -f to import
@@ -103,7 +103,7 @@ spec:
       claimName: mariadb_data
 ```
 
-Create Kubernetes Deployment YAML with 3 replicas for a container called `dep-ctr`
+Create Kubernetes Deployment YAML with 3 replicas for the specified container.
 ```
 $ podman kube generate --type deployment --replicas 3 dep-ct
 r
@@ -140,7 +140,7 @@ spec:
 ```
 
 
-Create Kubernetes Pod YAML for a container with the directory `/home/user/my-data` on the host bind-mounted in the container to `/volume`.
+Create Kubernetes Pod YAML for the specified container with the host directory `/home/user/my-data` bind-mounted onto the container path `/volume`.
 ```
 $ podman kube generate my-container-with-bind-mounted-data
 # Save the output of this file and use kubectl create -f to import
@@ -171,7 +171,7 @@ spec:
     name: home-user-my-data-host
 ```
 
-Create Kubernetes Pod YAML for a container with the named volume `priceless-data` mounted in the container at `/volume`.
+Create Kubernetes Pod YAML for the specified container with named volume `priceless-data` mounted onto the container path `/volume`.
 ```
 $ podman kube generate my-container-using-priceless-data
 # Save the output of this file and use kubectl create -f to import
@@ -201,7 +201,7 @@ spec:
       claimName: priceless-data
 ```
 
-Create Kubernetes Pod YAML for a pod called `demoweb` and include a service.
+Create Kubernetes Pod YAML for the specified pod and include a service.
 ```
 $ sudo podman kube generate -s demoweb
 # Save the output of this file and use kubectl create -f to import

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

@@ -14,7 +14,7 @@ Using the `--down` command line option, it is also capable of tearing down the p
 
 Using the `--replace` command line option, it tears down the pods(if any) created by a previous run of `podman kube play` and recreate the pods with the Kubernetes YAML file.
 
-Ideally the input file is created by Podman (see podman-kube-generate(1)).  This guarantees a smooth import and expected results.
+Ideally the input file is created by the Podman command (see podman-kube-generate(1)).  This guarantees a smooth import and expected results.
 
 Currently, the supported Kubernetes kinds are:
 
@@ -270,19 +270,19 @@ upon exit.
 
 ## EXAMPLES
 
-Recreate the pod and containers as described in a file called `demo.yml`
+Recreate the pod and containers described in the specified host YAML file.
 ```
 $ podman kube play demo.yml
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
 ```
 
-Recreate the pod and containers as described in a file `demo.yml` sent to stdin
+Recreate the pod and containers specified in a YAML file sent to stdin.
 ```
 $ cat demo.yml | podman kube play -
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
-
 ```
-Teardown the pod and containers as described in a file `demo.yml`
+
+Teardown the pod and containers as described in the specified YAML file.
 ```
 $  podman kube play --down demo.yml
 Pods stopped:
@@ -291,7 +291,7 @@ Pods removed:
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
 ```
 
-Provide `configmap-foo.yml` and `configmap-bar.yml` as sources for environment variables within the containers.
+Provide multiple configmaps files as sources for environment variables within the specified pods and containers.
 ```
 $ podman kube play demo.yml --configmap configmap-foo.yml,configmap-bar.yml
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
@@ -300,14 +300,14 @@ $ podman kube play demo.yml --configmap configmap-foo.yml --configmap configmap-
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
 ```
 
-Create a pod connected to two networks (called net1 and net2) with a static ip
+Create a pod connected to two networks with a static ip.
 ```
 $ podman kube play demo.yml --network net1:ip=10.89.1.5 --network net2:ip=10.89.10.10
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
 ```
 Please take into account that networks must be created first using podman-network-create(1).
 
-Create and teardown from a URL pointing to a YAML file
+Create and teardown from a URL pointing to a YAML file.
 ```
 $ podman kube play https://podman.io/demo.yml
 52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6

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

@@ -44,14 +44,17 @@ Suppress the progress output
 
 ## EXAMPLES
 
+Create an image from a compressed tar file, without showing progress.
 ```
 $ podman load --quiet -i fedora.tar.gz
 ```
 
+Create an image from the archive.tar file pulled from a URL, without showing progress.
 ```
 $ podman load -q -i https://server.com/archive.tar
 ```
 
+Create an image from stdin using bash redirection from a tar file.
 ```
 $ podman load < fedora.tar
 Getting image source signatures
@@ -64,6 +67,7 @@ Storing signatures
 Loaded image:  registry.fedoraproject.org/fedora:latest
 ```
 
+Create an image from stdin using a piped.
 ```
 $ cat fedora.tar | podman load
 Getting image source signatures

docs/source/markdown/podman-login.1.md.in

@@ -69,52 +69,61 @@ print detailed information about credential store
 
 ## EXAMPLES
 
+Add login credentials for specified registry to the default authorization file.
 ```
 $ podman login docker.io
 Username: umohnani
 Password:
 Login Succeeded!
 ```
 
+Add login credentials using specified username and password for local registry to the default authorization file.
 ```
 $ podman login -u testuser -p testpassword localhost:5000
 Login Succeeded!
 ```
 
+Add login credentials for alternate authfile path for the specified registry.
 ```
-$ podman login --authfile authdir/myauths.json docker.io
+$ podman login --authfile authdir/myauths.json quay.io
 Username: umohnani
 Password:
 Login Succeeded!
 ```
 
+Add login credentials as a Podman Secret for the specified registry to the default authorization file.
 ```
 $ echo -n MySecret! | podman secret create secretname -
 a0ad54df3c97cf89d5ca6193c
 $ podman login --secret secretname -u testuser quay.io
 Login Succeeded!
 ```
 
+Add login credentials for user test with password test to localhost:5000 registry disabling tls verification requirement.
 ```
 $ podman login --tls-verify=false -u test -p test localhost:5000
 Login Succeeded!
 ```
 
+Add login credentials for user foo with password bar to localhost:5000 registry using the certificate directory /etc/containers/certs.d.
 ```
 $ podman login --cert-dir /etc/containers/certs.d/ -u foo -p bar localhost:5000
 Login Succeeded!
 ```
 
+Add login credentials for docker.io into the default authorization file for user testuser with password information provided via stdin from a file on disk.
 ```
 $ podman login -u testuser  --password-stdin < testpassword.txt docker.io
 Login Succeeded!
 ```
 
+Add login credentials for docker.io into the default authorization file for user testuser with password information provided via stdin from a pipe.
 ```
 $ echo $testpassword | podman login -u testuser --password-stdin docker.io
 Login Succeeded!
 ```
 
+Add login credentials for the quay.io registry in verbose mode default authorization file.
 ```
 $ podman login quay.io --verbose
 Username: myusername

docs/source/markdown/podman-logout.1.md.in

@@ -37,19 +37,19 @@ Print usage statement
 
 ## EXAMPLES
 
+Remove login credentials for the docker.io registry from the authorization file
 ```
 $ podman logout docker.io
-Remove login credentials for https://registry-1.docker.io/v2/
 ```
 
+Remove login credentials for the docker.io registry from the authdir/myauths.json file.
 ```
 $ podman logout --authfile authdir/myauths.json docker.io
-Remove login credentials for https://registry-1.docker.io/v2/
 ```
 
+Remove login credentials for all registries.
 ```
 $ podman logout --all
-Remove login credentials for all registries
 ```
 
 ## SEE ALSO

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

@@ -28,6 +28,7 @@ Print usage statement.
 
 ## EXAMPLES
 
+Display default Podman machine info.
 ```
 $ podman machine info
 Host:
@@ -52,6 +53,7 @@ Version:
   Version: 4.4.0
 ```
 
+Display default Podman machine info formatted as json.
 ```
 $ podman machine info --format json
 {
@@ -80,6 +82,7 @@ $ podman machine info --format json
 }
 ```
 
+Display default Podman machine Host.Arch field.
 ```
 $ podman machine info --format "{{ .Host.Arch }}"
 amd64