Merge pull request #14311 from mburke5678/BZ-1691863

Incorrect explanation in point 5 at POD Object Definition (YAML)

Author: mburke5678

modules/nodes-pods-using-example.adoc

@@ -53,16 +53,16 @@ spec:
           drop:
             - MKNOD
         procMount: Default
-      ports:                    <5>
+      ports:
         - containerPort: 8080
           protocol: TCP
       imagePullPolicy: Always
-      volumeMounts:             <6>
+      volumeMounts:             <5>
         - name: default-token-wbqsl
           readOnly: true
           mountPath: /var/run/secrets/kubernetes.io/serviceaccount
       terminationMessagePolicy: File
-      image: openshift/hello-openshift
+      image: quay.io/openshift/origin-logging-eventrouter:latest <6>
   serviceAccount: default     <7>
   volumes:                    <8>
     - name: default-token-wbqsl
@@ -118,11 +118,11 @@ privileged Containers, run as a user of their choice, and more. The default cont
 but administrators can modify this as needed.
 <4> `*containers*` specifies an array of Container definitions; in this case (as
 with most), just one.
-<5> Each Container in the pod is instantiated from its own Container image.
-<6> The Container specifies where external storage volumes should be mounted
+<5> The Container specifies where external storage volumes should be mounted
 within the Container. In this case, there is a volume for storing the registry's
 data, and one for access to credentials the registry needs for making requests
 against the {product-title} API.
+<6> Each Container in the pod is instantiated from its own Container image.
 <7> Pods making requests against the {product-title} API is a common enough pattern
 that there is a `*serviceAccount*` field for specifying which service account user the pod should
 authenticate as when making the requests. This enables fine-grained access