HCIDOCS-453: Removed a note admonition, because the issue was fixed in 4.17..

Author: johnwilkins

modules/ipi-install-setting-proxy-settings-within-install-config.adoc

@@ -6,8 +6,12 @@
 [id='ipi-install-setting-proxy-settings-within-install-config_{context}']
 = Setting proxy settings
 
-To deploy an {product-title} cluster using a proxy, make the following changes to the `install-config.yaml` file.
+To deploy an {product-title} cluster while using a proxy, make the following changes to the `install-config.yaml` file.
 
+.Procedure
+
+. Add proxy values under the `proxy` key mapping:
++
 [source,yaml]
 ----
 apiVersion: v1
@@ -17,23 +21,18 @@ proxy:
   httpsProxy: https://USERNAME:PASSWORD@proxy.example.com:PORT
   noProxy: <WILDCARD_OF_DOMAIN>,<PROVISIONING_NETWORK/CIDR>,<BMC_ADDRESS_RANGE/CIDR>
 ----
-
++
 The following is an example of `noProxy` with values.
-
++
 [source,yaml]
 ----
 noProxy: .example.com,172.22.0.0/24,10.10.0.0/24
 ----
 
-With a proxy enabled, set the appropriate values of the proxy in the corresponding key/value pair.
-
+. With a proxy enabled, set the appropriate values of the proxy in the corresponding key/value pair.
++
 Key considerations:
-
++
 * If the proxy does not have an HTTPS proxy, change the value of `httpsProxy` from `https://` to `http://`.
-* If using a provisioning network, include it in the `noProxy` setting, otherwise the installer will fail.
+* If the cluster uses a provisioning network, include it in the `noProxy` setting, otherwise the installation program fails.
 * Set all of the proxy settings as environment variables within the provisioner node. For example, `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY`.
-
-[NOTE]
-====
-When provisioning with IPv6, you cannot define a CIDR address block in the `noProxy` settings. You must define each address separately.
-====