Rephrase following command

maximiliankolb · maximiliankolb · commit 9253491ca972 · 2025-09-23T16:37:12.000+02:00
Extends PR theforeman#4283 Part of theforeman#3672 on GitHub
diff --git a/guides/common/modules/proc_adding-kvm-connection.adoc b/guides/common/modules/proc_adding-kvm-connection.adoc
@@ -21,7 +21,7 @@ For example:
 ----
 . From the *Display type* list, select either *VNC* or *Spice*.
 . Optional: To secure console access for new hosts with a randomly generated password, select the *Set a randomly generated password on the display connection* checkbox.
-You can retrieve the password for the VNC console to access the guest virtual machine console from the output of the following command executed on the KVM server:
+You can retrieve the password for the VNC console to access the guest virtual machine console on your KVM server:
 +
 [options="nowrap" subs="+quotes"]
 ----
diff --git a/guides/common/modules/proc_creating-a-host-collection.adoc b/guides/common/modules/proc_creating-a-host-collection.adoc
@@ -14,7 +14,7 @@ The following procedure shows how to create host collections.
 . Click *Save*.
 
 .CLI procedure
-* To create a host collection, enter the following command:
+* Create a host collection:
 +
 [options="nowrap", subs="+quotes,attributes"]
 ----
diff --git a/guides/common/modules/proc_creating-a-lifecycle-environment-path.adoc b/guides/common/modules/proc_creating-a-lifecycle-environment-path.adoc
@@ -15,7 +15,7 @@ Then optionally add additional environments to the environment paths.
 . Optional: To add an environment to the environment path, click *Add New Environment*, complete the *Name* and *Description* fields, and select the prior environment from the *Prior Environment* list.
 
 .CLI procedure
-. To create an environment path, enter the `hammer lifecycle-environment create` command and specify the Library environment with the `--prior` option:
+. Create a lifecycle environment path:
 +
 [options="nowrap" subs="+quotes"]
 ----
@@ -25,7 +25,7 @@ $ hammer lifecycle-environment create \
 --prior "Library" \
 --organization "_My_Organization_"
 ----
-. Optional: To add an environment to the environment path, enter the `hammer lifecycle-environment create` command and specify the parent environment with the `--prior` option:
+. Optional: Add an environment to the environment path:
 +
 [options="nowrap" subs="+quotes"]
 ----
@@ -35,7 +35,7 @@ $ hammer lifecycle-environment create \
 --prior "_My First Lifecycle Environment_" \
 --organization "_My_Organization_"
 ----
-. To view the chain of the lifecycle environment path, enter the following command:
+. View the chain of the lifecycle environment path:
 +
 [options="nowrap" subs="+quotes"]
 ----
diff --git a/guides/common/modules/proc_deleting-report-records.adoc b/guides/common/modules/proc_deleting-report-records.adoc
@@ -10,7 +10,7 @@ You can also use a cron job to schedule report record deletions at the set inter
 By default, using the `foreman-rake reports:expire` command removes report records that are older than 90 days.
 You can specify the number of days to keep the report records by adding the *days* option and add the number of days.
 
-For example, if you want to delete report records that are older than seven days, enter the following command:
+For example, you can delete report records that are older than seven days:
 
 ----
 # foreman-rake reports:expire days=7
diff --git a/guides/common/modules/proc_deleting-task-records.adoc b/guides/common/modules/proc_deleting-task-records.adoc
@@ -7,7 +7,7 @@ Task records are created automatically in {Project}.
 You can use the `foreman-rake foreman_tasks:cleanup` command to remove tasks at any time.
 You can also use a cron job to schedule Task record deletions at the set interval that you want.
 
-For example, if you want to delete task records from successful repository synchronizations, enter the following command:
+For example, you can delete task records from successful repository synchronizations:
 
 ----
 # foreman-rake foreman_tasks:cleanup TASK_SEARCH='label = Actions::Katello::Repository::Sync' STATES='stopped'
diff --git a/guides/common/modules/proc_disabling-cockpit-on-project.adoc b/guides/common/modules/proc_disabling-cockpit-on-project.adoc
@@ -16,7 +16,8 @@ Perform the following procedure if you want to disable {the-Cockpit} on {Project
 [IMPORTANT]
 ====
 You can enable or disable {Cockpit} integration independently on {SmartProxyServers}.
-To prevent enabling {Cockpit} integration on a {SmartProxyServer}, enter the following command after completing the procedure:
+After completing the procedure on your {ProjectServer}, you can disable {Cockpit} integration on your {SmartProxyServers}:
+
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
 # {foreman-installer} --foreman-proxy-plugin-remote-execution-script-cockpit-integration false
diff --git a/guides/common/modules/proc_enabling-red-hat-repositories.adoc b/guides/common/modules/proc_enabling-red-hat-repositories.adoc
@@ -17,7 +17,7 @@ For an overview of required repositories, see xref:required-red-hat-repositories
 . Click the *Enable* icon next to the base architecture and release version that you want.
 
 .CLI procedure
-. To search for your product, enter the following command:
+. Search for your product:
 +
 [options="nowrap" subs="+quotes"]
 ----
diff --git a/guides/common/modules/proc_identifying-available-metrics.adoc b/guides/common/modules/proc_identifying-available-metrics.adoc
@@ -3,24 +3,24 @@
 [id=identifying-available-metrics_{context}]
 = Identifying available metrics
 
-* To list all metrics available through PCP, enter the following command:
+* List all metrics available through PCP:
 +
 ----
 # pminfo
 ----
-* To list all {Project} metrics and their descriptions, enter the following command:
+* List all {Project} metrics and their descriptions:
 +
 ----
 # foreman-rake telemetry:metrics
 ----
-* To list the archived metrics, enter the following command:
+* List the archived metrics:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----
 # less /var/log/pcp/pmlogger/_{foreman-example-com}_/pmlogger.log
 ----
 * The `pmlogger` daemon archives data as received, according to its configuration.
-To retrieve the name of the active log file, enter the following command:
+Retrieve the name of the active log file:
 +
 ----
 # pcp | grep logger
diff --git a/guides/common/modules/proc_importing-templates.adoc b/guides/common/modules/proc_importing-templates.adoc
@@ -53,7 +53,7 @@ The status is not persistent; if you leave the status page, you cannot return to
 
 [id="cli_Importing_Templates_{context}"]
 .CLI procedure
-* To import a template from a repository, enter the following command:
+* Import a template from a repository:
 +
 [options="nowrap", subs="+quotes,attributes"]
 ----
diff --git a/guides/common/modules/proc_monitoring-server.adoc b/guides/common/modules/proc_monitoring-server.adoc
@@ -8,7 +8,7 @@ This information can be used for maintenance and troubleshooting.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Monitor* > *Audits* to view the audit records.
-. To obtain a list of all the audit attributes, use the following command:
+. Obtain a list of all audit attributes:
 +
 [options="nowrap"]
 ----
diff --git a/guides/common/modules/proc_performing-an-incremental-backup.adoc b/guides/common/modules/proc_performing-an-incremental-backup.adoc
@@ -21,19 +21,19 @@ For more information, see xref:Estimating_the_Size_of_a_Backup_{context}[].
 endif::[]
 
 .Procedure
-. To perform a full offline backup, enter the following command:
+. Perform a full offline backup:
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
 # {foreman-maintain} backup offline _/var/backup_directory_
 ----
-. To create a directory within your backup directory to store the first incremental back up, enter the `{foreman-maintain} backup` command with the `--incremental` option:
+. Create a directory within your backup directory to store the first incremental backup:
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
 # {foreman-maintain} backup offline --incremental _/var/backup_directory/full_backup_ _/var/backup_directory_
 ----
-. To create the second incremental backup, enter the `{foreman-maintain} backup` command with the `--incremental` option and include the path to the first incremental backup to indicate the starting point for the next increment.
+. Create the second incremental backup by including the path to the first incremental backup to indicate the starting point for the next increment.
 This creates a directory for the second incremental backup in your backup directory:
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]
diff --git a/guides/common/modules/proc_retrieving-archived-metrics.adoc b/guides/common/modules/proc_retrieving-archived-metrics.adoc
@@ -6,26 +6,26 @@
 You can use the PCP CLI tools to retrieve metrics from an archive file.
 
 .Examples
-* To list all metrics that were enabled when the archive file was created, enter the following command:
+* List all metrics that were enabled when the archive file was created:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----
 # pminfo --archive _archive_file_
 ----
-* To view the host and time period covered by an archive file, enter the following command:
+* View the host and time period covered by an archive file:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----
 # pmdumplog -l _archive_file_
 ----
-* To list disk writes for each partition, over the time period covered by the archive file:
+* List disk writes for each partition, over the time period covered by the archive file:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----
 # pmval --archive /var/log/pcp/pmlogger/_{foreman-example-com}_/_20230831.00.10_ \
   -f 1 disk.partitions.write
 ----
-* To list disk write operations per partition, with a 2-second interval, over the time period between 14:00 and 14:15:
+* List disk write operations per partition, with a 2-second interval, over the time period between 14:00 and 14:15:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----
@@ -34,7 +34,7 @@ You can use the PCP CLI tools to retrieve metrics from an archive file.
   -f 3 disk.partitions.write \
   -S @14:00 -T @14:15
 ----
-* To list average values of all performance metrics, including the time and value of the minimum/maximum, over the time period between 14:00 and 14:30, and format the values as a table:
+* List average values of all performance metrics, including the time and value of the minimum/maximum, over the time period between 14:00 and 14:30, and format the values as a table:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----
@@ -45,7 +45,7 @@ You can use the PCP CLI tools to retrieve metrics from an archive file.
   disk.partitions.write \
   mem.freemem
 ----
-* To display system metrics stored in an archive, starting from 14:00, in an interactive manner similar to the `top` tool:
+* Display system metrics stored in an archive, starting from 14:00, in an interactive manner similar to the `top` tool:
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]
 ----

Original file line number	Diff line number	Diff line change
`@@ -21,7 +21,7 @@ For example:`
`21`	`21`	`----`
`22`	`22`	`. From the Display type list, select either VNC or Spice.`
`23`	`23`	`. Optional: To secure console access for new hosts with a randomly generated password, select the Set a randomly generated password on the display connection checkbox.`
`24`		`-You can retrieve the password for the VNC console to access the guest virtual machine console from the output of the following command executed on the KVM server:`
	`24`	`+You can retrieve the password for the VNC console to access the guest virtual machine console on your KVM server:`
`25`	`25`	`+`
`26`	`26`	`[options="nowrap" subs="+quotes"]`
`27`	`27`	`----`
Original file line number	Diff line number	Diff line change
`@@ -14,7 +14,7 @@ The following procedure shows how to create host collections.`
`14`	`14`	`. Click Save.`
`15`	`15`
`16`	`16`	`.CLI procedure`
`17`		`-* To create a host collection, enter the following command:`
	`17`	`+* Create a host collection:`
`18`	`18`	`+`
`19`	`19`	`[options="nowrap", subs="+quotes,attributes"]`
`20`	`20`	`----`
Original file line number	Diff line number	Diff line change
`@@ -17,7 +17,7 @@ For an overview of required repositories, see xref:required-red-hat-repositories`
`17`	`17`	`. Click the Enable icon next to the base architecture and release version that you want.`
`18`	`18`
`19`	`19`	`.CLI procedure`
`20`		`-. To search for your product, enter the following command:`
	`20`	`+. Search for your product:`
`21`	`21`	`+`
`22`	`22`	`[options="nowrap" subs="+quotes"]`
`23`	`23`	`----`
Original file line number	Diff line number	Diff line change
`@@ -53,7 +53,7 @@ The status is not persistent; if you leave the status page, you cannot return to`
`53`	`53`
`54`	`54`	`[id="cli_Importing_Templates_{context}"]`
`55`	`55`	`.CLI procedure`
`56`		`-* To import a template from a repository, enter the following command:`
	`56`	`+* Import a template from a repository:`
`57`	`57`	`+`
`58`	`58`	`[options="nowrap", subs="+quotes,attributes"]`
`59`	`59`	`----`
Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@ This information can be used for maintenance and troubleshooting.`
`8`	`8`
`9`	`9`	`.Procedure`
`10`	`10`	`. In the {ProjectWebUI}, navigate to Monitor > Audits to view the audit records.`
`11`		`-. To obtain a list of all the audit attributes, use the following command:`
	`11`	`+. Obtain a list of all audit attributes:`
`12`	`12`	`+`
`13`	`13`	`[options="nowrap"]`
`14`	`14`	`----`