Doc task

OSC 1.4.0 has incorrect "complete YAML manifest" link in 2 sections:

• 3.2.2.2. Creating an AWS VM image (AMI) using the web console. Correct link: https://github.com/openshift/sandboxed-containers-operator/blob/main/hack/aws-image-job.yaml
• 3.2.3.2. Creating an Azure VM image using the web console. Correct link: https://github.com/openshift/sandboxed-containers-operator/blob/main/hack/azure-image-job.yaml

OSC 1.5.0 does not have these sections.

Original description:

Description

I have a cluster and am trying to create the podvm in it.  

I have used the official docs https://docs.openshift.com/container-platform/4.13/sandboxed_containers/sandboxed-containers-moved.html for 1.4.0 just released.

The docs creating the job using the web console has the wrong image in the yaml that is pasted (3.2.2.2 and 3.2.3.2)

In the CLI, the URL oc apply -f https://raw.githubusercontent.com/openshift/sandboxed-containers-operator/peer-pods-tech-preview/hack/aws-image-job.yaml  (3.3.2.2) and  oc apply -f https://raw.githubusercontent.com/openshift/sandboxed-container-soperator/peer-pods-tech-preview/hack/azure-image-job.yaml
(3.3.3.2) both have the wrong image: 

The docs we have for preGA, https://docs.google.com/document/d/1NTTVUWYSwvXNyn3UnyhZI8kQuFHPV120wHhyf_N3Cz0 and https://docs.google.com/document/d/1Oro4cNOy7lB_Haum7c-xWGac8vBmIxaFh1oqD13LFog  both have URLs that point to the peer-pods-tech-preview branch which has the wrong image.

Changing the URL to use main instead of peer-pods-tech-preview branch results in a error: unable to read URL

Steps to reproduce

<What actions did you take to hit the bug?>
1.
2.
3.

Expected result

<What did you expect to happen?>

Actual result

<What actually happened?>

Impact

<How badly does this interfere with using the software?>

Env

<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>

Additional helpful info

<logs, screenshot, doc links, etc.>