Changing headers to sentence case theforeman#4

apinnick · Feb 1, 2024 · 0bac4e5 · 0bac4e5
1 parent 3bcb146
commit 0bac4e5
Show file tree

Hide file tree

Showing 22 changed files with 22 additions and 22 deletions.
diff --git a/guides/common/modules/proc_managing-and-monitoring-hosts-using-cockpit.adoc b/guides/common/modules/proc_managing-and-monitoring-hosts-using-cockpit.adoc
@@ -1,5 +1,5 @@
 [id="Managing_and_Monitoring_Hosts_Using_Cockpit_{context}"]
-= Managing and Monitoring Hosts Using {CockpitTitle}
+= Managing and monitoring hosts using {CockpitTitle}
 
 You can access the {Cockpit} web UI through the {ProjectWebUI} and use the functionality to manage and monitor hosts in {Project}.
 

diff --git a/guides/common/modules/proc_managing-container-name-patterns.adoc b/guides/common/modules/proc_managing-container-name-patterns.adoc
@@ -1,5 +1,5 @@
 [id="Managing_Container_Name_Patterns_{context}"]
-= Managing Container Name Patterns
+= Managing container name patterns
 
 When you use {Project} to create and manage your containers, as the container moves through Content View versions and different stages of the {Project} lifecycle environment, the container name changes at each stage.
 For example, if you synchronize a container image with the name `ssh` from an upstream repository, when you add it to a {Project} product and organization and then publish as part of a Content View, the container image can have the following name: `my_organization_production-custom_spin-my_product-custom_ssh`.

diff --git a/guides/common/modules/proc_managing-container-registry-authentication.adoc b/guides/common/modules/proc_managing-container-registry-authentication.adoc
@@ -1,5 +1,5 @@
 [id="Managing_Container_Registry_Authentication_{context}"]
-= Managing Container Registry Authentication
+= Managing container registry authentication
 
 You can manage the authentication settings for accessing containers images from {Project}.
 By default, users must authenticate to access containers images in {Project}.

diff --git a/guides/common/modules/proc_managing-ostree-content-with-content-views.adoc b/guides/common/modules/proc_managing-ostree-content-with-content-views.adoc
@@ -1,5 +1,5 @@
 [id="managing-ostree-content-with-content-views_{context}"]
-= Managing OSTree Content with Content Views
+= Managing OSTree content with Content Views
 
 Use Content Views to manage OSTree branches across the application lifecycle.
 This process uses the same publication and promotion method as RPMs or Puppet modules.

diff --git a/guides/common/modules/proc_managing-packages-on-the-base-operating-system.adoc b/guides/common/modules/proc_managing-packages-on-the-base-operating-system.adoc
@@ -1,5 +1,5 @@
 [id="Managing_Packages_on_the_Base_Operating_System_{context}"]
-= Managing Packages on the Base Operating System of {ProjectServer} or {SmartProxyServerTitle}
+= Managing packages on the base operating system of {ProjectServer} or {SmartProxyServerTitle}
 
 To install and update packages on the {ProjectServer} or {SmartProxyServer} base operating system, you must enter the `{foreman-maintain} packages` command.
 {Project} prevents users from installing and updating packages with `yum` because `yum` might also update the packages related to {ProjectServer} or {SmartProxyServer} and result in system inconsistency.

diff --git a/guides/common/modules/proc_managing-puppet-modules-with-r10k.adoc b/guides/common/modules/proc_managing-puppet-modules-with-r10k.adoc
@@ -1,5 +1,5 @@
 [id="puppet_guide_managing_puppet_modules_with_r10k_{context}"]
-= Managing Puppet Modules with r10k
+= Managing Puppet modules with r10k
 
 You can manage Puppet modules and environments using https://github.com/puppetlabs/r10k[r10k].
 r10k uses a list of Puppet roles from a `Puppetfile` to download Puppet modules from the Puppet Forge or git repositories.

diff --git a/guides/common/modules/proc_managing-ssh-keys-for-a-user.adoc b/guides/common/modules/proc_managing-ssh-keys-for-a-user.adoc
@@ -1,5 +1,5 @@
 [id="Managing_SSH_Keys_for_a_User_{context}"]
-= Managing SSH Keys for a User
+= Managing SSH keys for a user
 
 Use this procedure to add or remove SSH keys for a user.
 To use the CLI instead of the {ProjectWebUI}, see the xref:cli-managing-ssh-keys-for-a-user_{context}[].

diff --git a/guides/common/modules/proc_managing-tasks.adoc b/guides/common/modules/proc_managing-tasks.adoc
@@ -1,5 +1,5 @@
 [id="Managing_Tasks_{context}"]
-= Managing Tasks
+= Managing tasks
 
 {ProjectName} keeps a complete log of all planned or performed tasks, such as repositories synchronised, errata applied, and Content Views published.
 To review the log, navigate to *Monitor* > *{Project} Tasks* > *Tasks*.

diff --git a/guides/common/modules/proc_managing-the-lifecycle-of-the-content-view.adoc b/guides/common/modules/proc_managing-the-lifecycle-of-the-content-view.adoc
@@ -1,5 +1,5 @@
 [id="Managing_the_Lifecycle_of_the_Content_View_{context}"]
-= Managing the Lifecycle of the Content View
+= Managing the lifecycle of the Content View
 
 The default location of any new Content View is in the Library Environment.
 Optionally, you can add a new environment and promote your Content View to it.

diff --git a/guides/common/modules/proc_migrating-a-host-from-one-server-to-another-server.adoc b/guides/common/modules/proc_migrating-a-host-from-one-server-to-another-server.adoc
@@ -1,5 +1,5 @@
 [id="Migration_a_Host_From_One_Server_to_another_Server_{context}"]
-= Migrating a Host From One {Project} to Another {Project}
+= Migrating a host from one {Project} to another {Project}
 
 Use the script with `--force` to remove the `katello-ca-consumer-{asterisk}` packages from the old {Project} and install the `katello-ca-consumer-{asterisk}` packages on the new {Project}.
 

diff --git a/guides/common/modules/proc_migrating-a-host-from-red-hat-network.adoc b/guides/common/modules/proc_migrating-a-host-from-red-hat-network.adoc
@@ -1,5 +1,5 @@
 [id="Migrating_a_Host_from_Red_Hat_Network_{context}"]
-= Migrating a Host from Red Hat Network (RHN) or Satellite 5 to {Project}
+= Migrating a host from Red Hat Network (RHN) or Satellite 5 to {Project}
 
 The bootstrap script detects the presence of `/etc/syconfig/rhn/systemid` and a valid connection to RHN as an indicator that the system is registered to a legacy platform.
 The script then calls `rhn-classic-migrate-to-rhsm` to migrate the system from RHN.

diff --git a/guides/common/modules/proc_migrating-to-external-databases.adoc b/guides/common/modules/proc_migrating-to-external-databases.adoc
@@ -1,5 +1,5 @@
 [id="migrating-to-external-databases_{context}"]
-= Migrating to External Databases
+= Migrating to external databases
 
 Back up and transfer existing data, then use the `{foreman-installer}` command to configure {Project} to connect to an external PostgreSQL database server.
 

diff --git a/guides/common/modules/proc_monitoring-remote-jobs.adoc b/guides/common/modules/proc_monitoring-remote-jobs.adoc
@@ -1,5 +1,5 @@
 [id="Monitoring_Jobs_{context}"]
-= Monitoring Jobs
+= Monitoring jobs
 
 You can monitor the progress of a job while it is running.
 This can help in any troubleshooting that may be required.

diff --git a/guides/common/modules/proc_monitoring-services.adoc b/guides/common/modules/proc_monitoring-services.adoc
@@ -1,5 +1,5 @@
 [id="Monitoring_Services_{context}"]
-= Monitoring Services
+= Monitoring services
 
 In the {ProjectWebUI}, navigate to *Infrastructure* > *{SmartProxies}* and click the name of the selected {SmartProxy}.
 At the *Services* tab, you can find basic information on {SmartProxy} services, such as the list of DNS domains, or the number of Pulp workers.

diff --git a/guides/common/modules/proc_overriding-a-smart-class-parameter-for-a-location.adoc b/guides/common/modules/proc_overriding-a-smart-class-parameter-for-a-location.adoc
@@ -1,5 +1,5 @@
 [id="Overriding_Smart_Class_Parameter_for_Location_{context}"]
-= Overriding a Smart Class Parameter for a Location
+= Overriding a smart class parameter for a location
 
 You can use groups of hosts to override Puppet parameters for multiple hosts at once.
 The following examples chooses the _location_ context to illustrate setting context based parameters.

diff --git a/...common/modules/proc_overriding-a-smart-class-parameter-for-an-organization.adoc b/...common/modules/proc_overriding-a-smart-class-parameter-for-an-organization.adoc
@@ -1,5 +1,5 @@
 [id="Overriding_Smart_Class_Parameter_for_Organization_{context}"]
-= Overriding a Smart Class Parameter for an Organization
+= Overriding a smart class parameter for an organization
 
 You can use groups of hosts to override Puppet parameters for multiple hosts at once.
 The following example chooses the _organization_ context to illustrate setting context based parameters.

diff --git a/guides/common/modules/proc_overriding-a-smart-class-parameter-globally.adoc b/guides/common/modules/proc_overriding-a-smart-class-parameter-globally.adoc
@@ -1,5 +1,5 @@
 [id="Overriding_Smart_Class_Parameter_Globally_{context}"]
-= Overriding a Smart Class Parameter Globally
+= Overriding a smart class parameter globally
 
 You can configure a Puppet class after you have imported it to {ProjectServer}.
 This example overrides the default list of ntp servers.

diff --git a/...mmon/modules/proc_overriding-a-smart-class-parameter-on-an-individual-host.adoc b/...mmon/modules/proc_overriding-a-smart-class-parameter-on-an-individual-host.adoc
@@ -1,5 +1,5 @@
 [id="Overriding_Smart_Class_Parameter_Individual_Host_{context}"]
-= Overriding a Smart Class Parameter on an Individual Host
+= Overriding a smart class parameter on an individual host
 
 You can override parameters on individual hosts.
 This is recommended if you have multiple hosts and only want to make changes to a single one.

diff --git a/guides/common/modules/proc_overriding-ansible-variables-in-project.adoc b/guides/common/modules/proc_overriding-ansible-variables-in-project.adoc
@@ -1,5 +1,5 @@
 [id="Overriding_Ansible_Variables_in_{project-context}_{context}"]
-= Overriding Ansible Variables in {Project}
+= Overriding Ansible variables in {Project}
 
 If you run Ansible roles in {Project}, you can use {Project} to override Ansible variables for those roles.
 

diff --git a/guides/common/modules/proc_overriding-out-of-sync-interval-for-a-host-group.adoc b/guides/common/modules/proc_overriding-out-of-sync-interval-for-a-host-group.adoc
@@ -1,5 +1,5 @@
 [id="overriding-out-of-sync-interval-for-a-host-group_{context}"]
-= Overriding Out-of-Sync Interval for a Host Group
+= Overriding out-of-sync interval for a host group
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Configure > Host Groups*.

diff --git a/...common/modules/proc_overriding-out-of-sync-interval-for-an-individual-host.adoc b/...common/modules/proc_overriding-out-of-sync-interval-for-an-individual-host.adoc
@@ -1,5 +1,5 @@
 [id="overriding-out-of-sync-interval-for-an-individual-host_{context}"]
-= Overriding Out-of-Sync Interval for an Individual Host
+= Overriding out-of-sync interval for an individual host
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Hosts > All Hosts*.

diff --git a/.../modules/proc_overwriting-ansible-group-variables-in-application-instances.adoc b/.../modules/proc_overwriting-ansible-group-variables-in-application-instances.adoc
@@ -1,5 +1,5 @@
 [id="Overwriting_Ansible_Group_Variables_in_Application_Instances_{context}"]
-= Overwriting Ansible Group Variables in Application Instances
+= Overwriting Ansible group variables in application instances
 
 You can overwrite Ansible group variables in application instances unless the parameters are locked by the application definition.