Skip to content

Commit 35b04bb

Browse files
Reword the Foreman (#4267)
(cherry picked from commit dceb29b)
1 parent 6978f52 commit 35b04bb

6 files changed

+6
-6
lines changed

guides/common/modules/con_installing-server.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ This argument ensures that no actual changes are made.
3131
Potential changes are written to `{installer-log-file}`.
3232

3333
Files are always backed up and so you can revert any unwanted changes.
34-
For example, in the foreman-installer logs, you can see an entry similar to the following about Filebucket:
34+
For example, in the logs of `foreman-installer`, you can see an entry similar to the following about Filebucket:
3535

3636
[options="wrap"]
3737
----

guides/common/modules/con_introduction-to-content-management.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ This provides organizations with a method to store Red Hat content and organize
3131

3232
SUSE Subscription management::
3333
This provides organizations with a method to store SUSE content and organize it in various ways.
34-
Note that this requires the Foreman SCC Manager plugin.
34+
Note that this requires the SCC Manager plugin.
3535
For more information, see xref:Managing_SUSE_Content_{context}[].
3636
endif::[]
3737

guides/common/modules/con_puma-tunings.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,5 +3,5 @@
33
[id="Puma_Tunings_{context}"]
44
= Puma tunings
55

6-
Puma is a ruby application server which is used for serving the Foreman related requests to hosts.
6+
Puma is a ruby application server which is used for serving all Foreman related requests to hosts.
77
For any {Project} configuration that is supposed to handle a large number of hosts or frequent operations, it is important for the Puma to be tuned appropriately.

guides/common/modules/proc_configuring-kerberos-authentication-for-remote-execution.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ You can use Kerberos authentication to establish an SSH connection for remote ex
99
* Enroll {ProjectServer} on the Kerberos server
1010
* Enroll the {Project} target host on the Kerberos server
1111
* Configure and initialize a Kerberos user account for remote execution
12-
* Ensure that the foreman-proxy user on {Project} has a valid Kerberos ticket granting ticket
12+
* Ensure that the `foreman-proxy` user on {Project} has a valid Kerberos ticket-granting ticket (TGT)
1313

1414
.Procedure
1515
. To install and enable Kerberos authentication for remote execution, enter the following command:

guides/common/modules/proc_installing-acd-on-smart-proxy.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
= Installing ACD on {SmartProxyServer}
55

66
.Prerequisites
7-
* {ProjectServer} with the Foreman ACD plugin installed.
7+
* {ProjectServer} with the ACD plugin installed.
88
For more information, see xref:Installing_ACD_on_Server_{context}[].
99

1010
.Procedure

guides/common/modules/proc_uninstalling-the-foreman-templates-plugin.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
[id="Uninstalling_the_Foreman_Templates_plugin_{context}"]
44
= Uninstalling the Foreman templates plugin
55

6-
Use the following procedure to avoid errors after removing the foreman_templates plugin.
6+
Use the following procedure to avoid errors after removing the Templates plugin.
77

88
.Procedure
99
. Disable the plugin using the {Project} installer:

0 commit comments

Comments
 (0)