BZ1405268 and PR3535-Follow-up: Made minor edits to content and formatting.

Author: bmcelvee

dev_guide/builds.adoc

@@ -1698,9 +1698,8 @@ sourceStrategy:
 ====
 
 NOTE: A platform administrator can set the default build verbosity for the entire {product-title}
-instance by configuring env/BUILD_LOGLEVEL for the `BuildDefaults` admission controller. This
-default can be overridden by specifying BUILD_LOGLEVEL in a given BuildConfig. A still higher priority
-override can be specified on the command line for non-binary builds by passing --build-loglevel to
+instance by configuring `env/BUILD_LOGLEVEL` for the `BuildDefaults` admission controller. This
+default can be overridden by specifying `BUILD_LOGLEVEL` in a given `BuildConfig`. You can specify a higher priority override on the command line for non-binary builds by passing `--build-loglevel` to
 `oc start-build`.
 
 Available log levels for Source builds are as follows:

install_config/build_defaults_overrides.adoc

@@ -155,18 +155,18 @@ admissionConfig:
 <2> Sets the HTTPS proxy to use when cloning source code from a Git repository.
 <3> Sets the list of domains for which proxying should not be performed.
 <4> Default environment variable that sets the HTTP proxy to use during the build.
-This may be used for downloading dependencies during the assemble and build
+This can be used for downloading dependencies during the assemble and build
 phases.
 <5> Default environment variable that sets the HTTPS proxy to use during the
-build. This may be used for downloading dependencies during the assemble and
+build. This can be used for downloading dependencies during the assemble and
 build phases.
 <6> Default environment variable that sets the build log level during the build.
 <7> Additional default environment variable that will be added to
 every build.
-<8> Labels to be applied to every image built. Users can override these in their `BuildConfig`.
+<8> Labels to be applied to every image built. These can be overridden in `BuildConfig`.
 <9> Build pods will only run on nodes with the `key1=value2` and `key2=value2` labels.
-    Users can define a different set of `nodeSelectors` for their builds in which case these
-    values will be ignored.
+    Users can define a different set of `nodeSelectors` for their builds, causing these
+    values to be ignored.
 <10> Build pods will have these annotations added to them.
 <11> Sets the default resources to the build pod if the `BuildConfig` does not have related resource defined.