[OCPBUGS-52991] : Correcting the typo for the path in section "3.2.6. Updating mirror registry for Red Hat OpenShift from a remote host"

[gagankrmahto]

Correcting the typo for the path,
/$HOME/quay-instal/quay-postgres-backup/

It should be
/$HOME/quay-install/quay-postgres-backup/

Version(s):

4.13+

Issue:

OCPBUGS-52991

Link to docs preview:

https://90129--ocpdocs-pr.netlify.app/openshift-enterprise/latest/disconnected/mirroring/installing-mirroring-creating-registry.html

QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Wed Mar 12 02:20:14 - Prow CI generated the docs preview:

https://90129--ocpdocs-pr.netlify.app/openshift-enterprise/latest/disconnected/mirroring/installing-mirroring-creating-registry.html

[openshift-ci]

@gagankrmahto: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[gagankrmahto]

/label peer-review-needed

[xenolinux]

Changes LGTM

A general suggestion: I see that you have another PR that addresses the same change in another file. For future instances, you can include all of your changes in a single PR only.

We also need a QE approval (as the /lgtm comment on the PR) but because this is a typo-related change. You can skip that for this PR.

[gagankrmahto]

Thank you , I will make sure to create a single PR from next time

[gagankrmahto]

/label merge-review-needed

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[bergerhoffer]

The branch/enterprise-4.20 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.19. And any PR going into main must also target the latest version branch (enterprise-4.20).

If the update in your PR does NOT apply to version 4.20 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.