Fix content readability issues for upgrading your project section (#4171)

* Fix content readability issues for upgrading your project section

Shorten/split long sentences in the 'Upgrading your project' section of the connected upgrade guide.

JIRA: https://issues.redhat.com/browse/SAT-35663

Author: AkshayGadhaveRH

guides/common/modules/proc_upgrading-your-project-server.adoc

@@ -3,7 +3,7 @@
 [id="upgrading-your-{project-context}-server"]
 = Upgrading your {ProjectServer}
 
-Upgrading a {ProjectServer} with access to the public internet includes backing up the server, ensuring that the system and {Project} configuration is up-to-date, and running the upgrade.
+Upgrading a connected {ProjectServer} includes backing up the server, updating the system and {Project} configuration, and running the upgrade.
 
 include::snip_warning-maintain-config-noop.adoc[]
 

guides/common/modules/snip_post-upgrade-tasks.adoc

@@ -1,10 +1,11 @@
 . Perform the following post-upgrade tasks to ensure your environment is adjusted to any changes applied during the upgrade.
-.. If any of the templates you are using were created by cloning the default {Project} templates, verify whether the default templates changed during the upgrade.
-If the default templates have changed, consider updating your custom templates as well to reflect these changes.
+.. Verify whether the default templates changed during the upgrade.
+Update any custom templates that you created by cloning a default template to reflect these changes.
 +
 [NOTE]
 ====
-If the default provisioning templates changed during the upgrade and your custom code is executed before or after the provisioning process, you can use custom provisioning snippets to avoid recreating cloned templates.
+Use custom provisioning snippets to execute custom code before or after the provisioning process instead of cloning default templates.
+You can avoid recreating cloned templates if you use custom provisioning snippets.
 For more information about configuring custom provisioning snippets, see {ProvisioningDocURL}running-custom-code-during-host-provisioning[Running custom code during host provisioning] in _{ProvisioningDocTitle}_.
 ====
 .. If your {Project} shows any discovered hosts, reboot them:

guides/common/modules/snip_warning-maintain-config-noop.adoc

@@ -1,5 +1,7 @@
 [WARNING]
-If you customize configuration files, manually or using a tool such as Hiera, these changes are overwritten when the maintenance script runs during upgrading or updating.
+Note that the {foreman-installer} is executed during an upgrade or update.
+Any files managed by {foreman-installer} are overwritten.
+Check if you have any manual changes that would be overwritten by {foreman-installer}.
 You can use the `--noop` option with the {foreman-installer} to test for changes.
 ifdef::satellite[]
 For more information, see the Red Hat Knowledgebase solution https://access.redhat.com/solutions/3351311[How to use the noop option to check for changes in {Project} config files during an upgrade.]