Bug 1806755 - Clarify entitled builds doc on advantages of UBI image stream

Author: rolfedh

builds/running-entitled-builds.adoc

@@ -10,16 +10,8 @@ include::modules/builds-create-imagestreamtag.adoc[leveloffset=+1]
 
 include::modules/builds-source-secrets-entitlements.adoc[leveloffset=+1]
 
-There are two paths to pulling in the base RHEL image:
-
-* Add the pull secret to registry.redhat.io to your project.
-* Create an image stream in the `openshift` namespace for the RHEL-based
-image. This makes the image stream available across the cluster.
-
 == Running builds with Subscription Manager
 
-include::modules/builds-source-input-subman-config.adoc[leveloffset=+2]
-
 include::modules/builds-strategy-docker-entitled-subman.adoc[leveloffset=+2]
 
 == Running builds with Satellite subscriptions

modules/builds-create-imagestreamtag.adoc

@@ -3,29 +3,26 @@
 //* builds/running-entitled-builds.adoc
 
 [id="builds-create-imagestreamtag_{context}"]
-= Creating an image stream tag to the Red Hat Universal Base Image
+= Creating an image stream tag for the Red Hat Universal Base Image
 
-To use Red Hat subscriptions within a build, you should create an image stream to reference the universal base image (UBI).
+To use Red Hat subscriptions within a build, you create an image stream tag to reference the Universal Base Image (UBI).
 
-Builds that reference the UBI directly from registry.redhat.io require a pull secret.
+To make the UBI available *in every project* in the cluster, you add the image stream tag to the `openshift` namespace. Otherwise, to make it available *in a specific project*, you add the image stream tag to that project.
 
-.Prerequisites
-
-* You must create a pull secret for registry.redhat.io, and link it to a user
-project.
+The benefit of using image stream tags this way is that doing so grants access to the UBI based on the `registry.redhat.io` credentials in the install pull secret without exposing the pull secret to other users. This is more convenient than requiring each developer to install pull secrets with `registry.redhat.io` credentials in each project.
 
 .Procedure
 
-* To create an `imagestreamtag` in a single project:
+* To create an `ImageStreamTag` in the `openshift` namespace, so it is available to developers in all projects, enter:
 +
 [source,terminal]
 ----
-$ oc tag --source=docker registry.redhat.io/ubi7/ubi:latest ubi:latest
+$ oc tag --source=docker registry.redhat.io/ubi7/ubi:latest ubi:latest -n openshift
 ----
 
-* To create an `imagestreamtag` in the {product-title} namespace, making it available to developers in all projects:
+* To create an `ImageStreamTag` in a single project, enter:
 +
 [source,terminal]
 ----
-$ oc tag --source=docker registry.redhat.io/ubi7/ubi:latest ubi:latest -n openshift
+$ oc tag --source=docker registry.redhat.io/ubi7/ubi:latest ubi:latest
 ----