Clarify applying custom Puppet config

guides/common/modules/con_applying-custom-configuration.adoc

@@ -1,37 +1,47 @@
 [id="applying-custom-configuration_{context}"]
 = Applying custom configuration to {ProjectName}
 
-When you install and configure {Project} for the first time by using `{foreman-installer}`, you can specify that the DNS and DHCP configuration files are not to be managed by Puppet by using the installer flags `--foreman-proxy-dns-managed=false` and `--foreman-proxy-dhcp-managed=false`.
-If these flags are not specified during the initial installer run, rerunning of the installer overwrites all manual changes, for example, rerun for upgrade purposes.
-If changes are overwritten, you must run the restore procedure to restore the manual changes.
-For more information, see {InstallingServerDocURL}restoring-manual-changes-overwritten-by-a-puppet-run_{project-context}[Restoring Manual Changes Overwritten by a Puppet Run].
+[IMPORTANT]
+====
+Applying custom configuration to {Project} can have unintended consequences that affect performance or functionality.
+Before applying the custom configuration to your production environment, test your changes in a staging environment or run `{foreman-installer}` with the `--noop` and `--verbose` options.
+If the custom configuration causes problems, remove the offending lines from `/etc/foreman-installer/custom-hiera.yaml` and rerun the `{foreman-installer}`.
 
-To view all installer flags available for custom configuration, run `{installer-scenario} --full-help`.
-Some Puppet classes are not exposed to the {Project} installer.
-To manage them manually and prevent the installer from overwriting their values, specify the configuration values by adding entries to configuration file `/etc/foreman-installer/custom-hiera.yaml`.
-This configuration file is in YAML format, consisting of one entry per line in the format of `<puppet class>::<parameter name>: <value>`.
-Configuration values specified in this file persist across installer reruns.
+ifdef::satellite[]
+If you have concerns about whether a particular value is safe to alter, contact Red{nbsp}Hat support.
+endif::[]
+====
 
-Common examples include:
+The `{installer-scenario} --full-help` command displays all `{foreman-installer}` flags available for custom configuration.
+Additionally, some Puppet classes are not exposed to `{foreman-installer}`.
+You can manage these Puppet classes manually by specifying configuration values in the `/etc/foreman-installer/custom-hiera.yaml` file. 
+Values specified in this file persist when you rerun `{foreman-installer}`.
 
-* For Apache, to set the ServerTokens directive to return only the product name:
-+
+The `/etc/foreman-installer/custom-hiera.yaml` file accepts entries in the following format:
+
+[source, yaml, options="nowrap", subs="+quotes,attributes"]
+----
+_Puppet_Module_::__Parameter_Name__: _Parameter_Value_
+----
+
+For a list of available Puppet modules, see the contents of the `/usr/share/foreman-installer/modules/` directory.
+For a list of classes, parameters, and values available for a module, see the `.pp` files in the directory for that module, such as `_Module_Name_/manifests/_Example_PP_File_.pp`.
+
+.Example `/etc/foreman-installer/custom-hiera.yaml` entries
+[options="header"]
+|====
+|Entry|Explanation
+a|[source, yaml, options="nowrap", subs="+quotes,attributes"]
 ----
 apache::server_tokens: Prod
 ----
-+
-* To turn off the Apache server signature entirely:
-+
+|Sets the `ServerTokens` directive to return only the product name.
+a|[source, yaml, options="nowrap", subs="+quotes,attributes"]
 ----
 apache::server_signature: Off
 ----
+|Disables the Apache server signature.
+|====
 
-The Puppet modules for the {Project} installer are stored under `/usr/share/foreman-installer/modules`.
-Check the `.pp` files (for example: _moduleName_/manifests/_example_.pp) to look up the classes, parameters, and values.
-Alternatively, use the `grep` command to do keyword searches.
-
-Setting some values may have unintended consequences that affect the performance or functionality of {ProjectName}.
-Consider the impact of the changes before you apply them, and test the changes in a non-production environment first.
-If you do not have a non-production {Project} environment, run the {Project} installer with the `--noop` and `--verbose` options.
-If your changes cause problems, remove the offending lines from `custom-hiera.yaml` and rerun the {Project} installer.
-If you have any specific questions about whether a particular value is safe to alter, contact Red Hat support.
+.Additional resources
+* The `/etc/foreman-installer/custom-hiera.yaml` file on your {ProjectServer}

guides/common/modules/proc_restoring-manual-changes-overwritten-by-a-puppet-run.adoc

@@ -2,6 +2,9 @@
 = Restoring manual changes overwritten by a Puppet run
 
 If your manual configuration has been overwritten by a Puppet run, you can restore the files to the previous state.
+
+For example, when you install and configure {Project} for the first time by using `{foreman-installer}`, you can use the `--foreman-proxy-dns-managed=false` and `--foreman-proxy-dhcp-managed=false` options to specify that the DNS and DHCP configuration files are not to be managed by Puppet.
+If you do not use these options during the initial `{foreman-installer}` run, rerunning `{foreman-installer}` overwrites all manual changes.
 The following example shows you how to restore a DHCP configuration file overwritten by a Puppet run.
 
 .Procedure