OSDOCS-7998: update config yaml path and text

Author: ShaunaDiaz

microshift_configuring/microshift-using-config-tools.adoc

@@ -12,10 +12,10 @@ include::snippets/microshift-greenboot-status-snip.adoc[leveloffset=+2]
 
 include::modules/microshift-config-yaml.adoc[leveloffset=+1]
 
-include::modules/microshift-config-nodeport-limits.adoc[leveloffset=+1]
+include::modules/microshift-config-nodeport-limits.adoc[leveloffset=+2]
 
-//[id="additional-resources_microshift-using-config-tools_{context}"]
-//[role="_additional-resources"]
-//== Additional resources
+[id="additional-resources_microshift-using-config-tools_{context}"]
+[role="_additional-resources"]
+== Additional resources
 
-//TODO:add xref to check greenboot status module after merge
+* xref:../../microshift-greenboot-checking-status.adoc#microshift-greenboot-checking-status[Checking Greenboot status]

modules/microshift-config-yaml.adoc

@@ -6,15 +6,20 @@
 [id="microshift-config-yaml_{context}"]
 = Using a YAML configuration file
 
-{product-title} searches for a configuration file in the user-specific directory, `~/.microshift/config.yaml`, then the system-wide `/etc/microshift/config.yaml` directory. You must create the configuration file and specify any settings that should override the defaults before starting {product-title}.
-
-//include admonition snippet about waiting for greenboot
+On start up, {product-title} searches the system-wide `/etc/microshift/` directory for a configuration file named `config.yaml`. To use custom configurations, you must create the configuration file and specify any settings that should override the defaults before starting {product-title}.
 
 [id="microshift-yaml-default_{context}"]
 == Default settings
-If you do not create a `config.yaml` file, the default values are used. The following example configuration shows the default settings. You must create a custom `config.yaml` file and change any settings that should override the defaults before starting {product-title}.
+If you do not create a `config.yaml` file, the default values are used. The following example shows the default configuration settings.
 
-.Default YAML values example
+* You can use the following command to see the default values:
++
+[source,terminal]
+----
+$ microshift show-config
+----
++
+.Default values example output in YAML form
 [source,yaml]
 ----
 dns:
@@ -44,21 +49,22 @@ debugging:
 <8> Subject Alternative Names for API server certificates.
 <9> Log verbosity. Valid values for this field are `Normal`, `Debug`, `Trace`, or `TraceAll`.
 
+[id="microshift-yaml-custom_{context}"]
+== Custom settings
+To create custom configurations, you must create a `config.yaml` file in the `/etc/microshift/` directory, then change any settings that should override the defaults before starting or restarting {product-title}.
+
 [IMPORTANT]
 ====
-Restart {product-title} after changing any configuration settings to have them take effect. {product-title} reads the configuration file only on start.
+Restart {product-title} after changing any configuration settings to have them take effect. The `config.yaml` file is read only when {product-title} starts.
 ====
 
-[id="microshift-yaml-custom_{context}"]
-== Custom settings
-You must change any settings that should override the defaults before starting {product-title}.
-
-advertiseAddress::
+[id="microshift-yaml-advertiseAddress_{context}"]
+=== advertiseAddress
 The `apiserver.advertiseAddress` flag specifies the IP address on which to advertise the API server to members of the cluster. This address must be reachable by the cluster. You can set a custom IP address here, but you must also add the IP address to a host interface. Customizing this parameter preempts {product-title} from adding a default IP address to the `br-ex` network interface.
-+
+
 [IMPORTANT]
 ====
 If you customize the `advertiseAddress` IP address, make sure it is reachable by the cluster when {product-title} starts by adding the IP address to a host interface.
 ====
-+
+
 If unset, the default value is `10.44.0.0/32`. It will be set to the next immediate subnet after the service network. For example, when the service network is `10.43.0.0/16`, the `advertiseAddress` is set to `10.44.0.0/32`.