PR13875 follow-up

Author: bmcelvee

builds/build-strategies.adoc

@@ -30,7 +30,6 @@ include::modules/builds-strategy-s2i-buildconfig-environment.adoc[leveloffset=+3
 include::modules/builds-strategy-s2i-ignore-source-files.adoc[leveloffset=+2]
 include::modules/builds-strategy-custom-build.adoc[leveloffset=+1]
 include::modules/builds-strategy-custom-from-image.adoc[leveloffset=+2]
-include::modules/builds-strategy-custom-expose-docker-socket.adoc[leveloffset=+2]
 include::modules/builds-strategy-custom-secrets.adoc[leveloffset=+2]
 include::modules/builds-strategy-custom-environment-variables.adoc[leveloffset=+2]
 include::modules/builds-strategy-pipeline-build.adoc[leveloffset=+1]

modules/builds-strategy-custom-build.adoc

@@ -12,7 +12,12 @@ you to customize your build process.
 A Custom builder image is a plain Docker-formatted container image embedded with
 build process logic, for example for building RPMs or base images.
 
-Custom builds run with a very high level of privilege and are not available to users
-by default.  Only users who can be trusted with cluster administration permissions
-should be granted access to run custom builds.  See <securing builds> for instructions
-on how to grant access to the this build type to a user.
+Custom builds run with a very high level of privilege and are not available to
+users by default. Only users who can be trusted with cluster administration
+permissions should be granted access to run custom builds.
+
+.Additional resources
+
+* See xref:../builds/securing-builds-by-strategy.adoc#securing-builds-by-strategy[Securing
+builds by strategy] for instructions on how to grant access to the this build
+type to a user.