Man pages: refactor common options: --pod

Only between podman-create and -run; the other meanings
of --pod are too different. This almost didn't feel worth
refactoring, except the podman-run version fixed a word
and added a possibly important note about infra containers.
I went with the podman-run version.

Signed-off-by: Ed Santiago <santiago@redhat.com>

docs/source/markdown/options/pod.run.md

@@ -0,0 +1,5 @@
+#### **--pod**=*name*
+
+Run container in an existing pod. If you want Podman to make the pod for you, prefix the pod name with **new:**.
+To make a pod with more granular options, use the **podman pod create** command before creating a container.
+If a container is run with a pod, and the pod has an infra-container, the infra-container will be started before the container is.

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

@@ -276,10 +276,7 @@ This option conflicts with **--add-host**.
 
 @@option platform
 
-#### **--pod**=*name*
+@@option pod.run
-
-Run container in an existing pod. If you want Podman to make the pod for you, preference the pod name with `new:`.
-To make a pod with more granular options, use the `podman pod create` command before creating a container.
 
 @@option pod-id-file.container
 

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

@@ -302,11 +302,7 @@ This is used to override the Podman provided user setup in favor of entrypoint c
 
 @@option platform
 
-#### **--pod**=*name*
+@@option pod.run
-
-Run container in an existing pod. If you want Podman to make the pod for you, prefix the pod name with **new:**.
-To make a pod with more granular options, use the **podman pod create** command before creating a container.
-If a container is run with a pod, and the pod has an infra-container, the infra-container will be started before the container is.
 
 @@option pod-id-file.container