Enhance the section

modules/registry-accessing-directly.adoc

@@ -101,7 +101,7 @@ endif::[]
 +
 [source,terminal]
 ----
-$ podman pull name.io/image
+sh-4.2# podman pull name.io/image
 ----
 
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
@@ -111,7 +111,7 @@ correctly place and later access the image in the registry:
 +
 [source,terminal]
 ----
-$ podman tag name.io/image image-registry.openshift-image-registry.svc:5000/openshift/image
+sh-4.2# podman tag name.io/image image-registry.openshift-image-registry.svc:5000/openshift/image
 ----
 endif::[]
 +
@@ -128,6 +128,6 @@ to push the image.
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 [source,terminal]
 ----
-$ podman push image-registry.openshift-image-registry.svc:5000/openshift/image
+sh-4.2# podman push image-registry.openshift-image-registry.svc:5000/openshift/image
 ----
 endif::[]

modules/registry-checking-the-status-of-registry-pods.adoc

@@ -11,7 +11,6 @@ As a cluster administrator, you can list the image registry pods running in the
 .Prerequisites
 
 * You have access to the cluster as a user with the `cluster-admin` role.
-* You have installed the OpenShift CLI (`oc`).
 
 .Procedure
 

registry/accessing-the-registry.adoc

@@ -14,7 +14,7 @@ endif::[]
 You can access the registry directly to invoke `podman` commands. This allows
 you to push images to or pull them from the integrated registry directly using
 operations like `podman push` or `podman pull`. To do so, you must be logged in
-to the registry using the `oc login` command. The operations you can perform
+to the registry using the `podman login` command. The operations you can perform
 depend on your user permissions, as described in the following sections.
 
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]