Merge pull request #88331 from liangxia/bug50553

OCPBUGS#50553: Fix typo

Author: xenolinux

modules/containers-signature-verify-unsigned.adoc

@@ -12,7 +12,7 @@ For example, the image references lacking a verifiable signature are contained i
 .Example release info output
 [source,terminal]
 ----
-$ oc adm release info  quay.io/openshift-release-dev/ ocp-release@sha256:2309578b68c5666dad62aed696f1f9d778ae1a089ee461060ba7b9514b7ca417 -o pullspec <1>
+$ oc adm release info quay.io/openshift-release-dev/ocp-release@sha256:2309578b68c5666dad62aed696f1f9d778ae1a089ee461060ba7b9514b7ca417 -o pullspec <1>
 quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9aafb914d5d7d0dec4edd800d02f811d7383a7d49e500af548eab5d00c1bffdb <2>
 ----
 
@@ -23,4 +23,4 @@ quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9aafb914d5d7d0dec4edd800d0
 == Automated verification during updates
 Verification of signatures is automatic. The OpenShift Cluster Version Operator (CVO) verifies signatures on the release images during an {product-title} update. This is an internal process. An {product-title} installation or update fails if the automated verification fails.
 
-Verification of signatures can also be done manually using the `skopeo` command-line utility.
+Verification of signatures can also be done manually using the `skopeo` command-line utility.