Smaller corrections from stylecheck

SUSE · Aug 29, 2023 · 4964e73 · 4964e73
1 parent f89ce51
commit 4964e73
Show file tree

Hide file tree

Showing 3 changed files with 18 additions and 18 deletions.
diff --git a/adoc/SAP-S4HA10-setup-simplemount-sle15.adoc b/adoc/SAP-S4HA10-setup-simplemount-sle15.adoc
@@ -625,7 +625,7 @@ For the ERS and ASCS instances, edit the instance profiles
 profile directory _/usr/sap/{mySid}/SYS/profile/_.
 
 Tell the `{sapStartSrv}` service to load the HA script connector library and to
-use the connector `{s4sClConnector3}`. On the other hand, please make sure the
+use the connector `{s4sClConnector3}`. On the other hand, make sure the
 feature _Autostart_ is *not* used.
 
 [subs="attributes"]
@@ -993,7 +993,7 @@ primitive rsc_sap_{mySID}_{myInstAscs} SAPInstance \
 ================================================
 The shown SAPInstance monitor timeout is a trade-off between fast recovery of
 the ASCS vs. resilience against sporadic temporary NFS issues. You may slightly
-increase it to fit your infrastructure. Please consult your storage or NFS server
+increase it to fit your infrastructure. Consult your storage or NFS server
 documentation for appropriate timeout values.
 See also manual pages ocf_heartbeat_SAPInstance(7), ocf_heartbeat_IPAddr2(7) ocf_suse_SAPStartSrv(7)
 and nfs(5).
@@ -1048,7 +1048,7 @@ primitive rsc_sap_{mySID}_{myInstErs} SAPInstance \
 ================================================
 The shown SAPInstance monitor timeout is a trade-off between fast recovery of
 the ERS vs. resilience against sporadic temporary NFS issues. You may slightly
-increase it to fit your infrastructure. Please consult your storage or NFS server
+increase it to fit your infrastructure. Consult your storage or NFS server
 documentation for appropriate timeout values.
 See also manual pages ocf_heartbeat_SAPInstance(7), ocf_heartbeat_IPAddr2(7) ocf_suse_SAPStartSrv(7)
 and nfs(5).
@@ -2241,7 +2241,7 @@ Find below the Corosync configuration for one corosync ring. Ideally two rings w
 [subs="specialchars,attributes"]
 ----
 {my2nd1}:~ # cat /etc/corosync/corosync.conf
-# Read the corosync.conf.5 manual page
+# Please read the corosync.conf.5 manual page
 totem {
     version: 2
     secauth: on

diff --git a/adoc/SAP-S4HA10-setupguide-sle15.adoc b/adoc/SAP-S4HA10-setupguide-sle15.adoc
@@ -993,11 +993,11 @@ Verify the SBD cluster configuration and if needed, modify them as described.
 
 First, configure the resources for the file system, IP address and the {sap}
 instance. You need to adapt the parameters for your specific environment.
-The shown Filesystem and SAPInstance monitor timeouts are a trade-off between
+The shown file system and SAPInstance monitor timeouts are a trade-off between
 fast recovery vs. resilience against sporadic temporary NFS issues. You may
 slightly increase it to fit your infrastructure.
-The SAPInstance timeout needs to be higher than the Filesystem timeout.
-Please consult your storage or NFS server documentation for appropriate
+The SAPInstance timeout needs to be higher than the file system timeout.
+Consult your storage or NFS server documentation for appropriate
 timeout values.
 See also manual pages ocf_heartbeat_Filesystem(7), ocf_heartbeat_SAPInstance(7)
 and nfs(5).
@@ -1050,11 +1050,11 @@ As user _root_, type the following command:
 
 Second, configure the resources for the file system, IP address and the {sap}
 instance. You need to adapt the parameters for your specific environment.
-The shown Filesystem and SAPInstance monitor timeouts are a trade-off between
-fast recovery vs. resilience against sporadic temporary NFS issues. You may
+The shown file system and SAPInstance monitor timeouts are a trade-off between
+fast recovery versus resilience against sporadic temporary NFS issues. You may
 slightly increase it to fit your infrastructure.
-The SAPInstance timeout needs to be higher than the Filesystem timeout.
-Please consult your storage or NFS server documentation for appropriate
+The SAPInstance timeout needs to be higher than the file system timeout.
+Consult your storage or NFS server documentation for appropriate
 timeout values.
 See also manual pages ocf_heartbeat_Filesystem(7), ocf_heartbeat_SAPInstance(7)
 and nfs(5).

diff --git a/adoc/sap-nw740-sle15-setupguide.adoc b/adoc/sap-nw740-sle15-setupguide.adoc
@@ -1089,11 +1089,11 @@ _As user root_
 
 First, configure the resources for the file system, IP address and the {sap}
 instance. Make sure you adapt the parameters to your environment.
-The shown Filesystem and SAPInstance monitor timeouts are a trade-off between
+The shown file system and SAPInstance monitor timeouts are a trade-off between
 fast recovery vs. resilience against sporadic temporary NFS issues. You may
 slightly increase it to fit your infrastructure.
-The SAPInstance timeout needs to be higher than the Filesystem timeout.
-Please consult your storage or NFS server documentation for appropriate
+The SAPInstance timeout needs to be higher than the file system timeout.
+Consult your storage or NFS server documentation for appropriate
 timeout values.
 See also manual pages ocf_heartbeat_Filesystem(7), ocf_heartbeat_SAPInstance(7)
 and nfs(5).
@@ -1146,11 +1146,11 @@ _As user root_
 
 Second, configure the resources for the file system, IP address and the {sap}
 instance. Make sure you adapt the parameters to your environment.
-The shown Filesystem and SAPInstance monitor timeouts are a trade-off between
+The shown file system and SAPInstance monitor timeouts are a trade-off between
 fast recovery vs. resilience against sporadic temporary NFS issues. You may
 slightly increase it to fit your infrastructure.
-The SAPInstance timeout needs to be higher than the Filesystem timeout.
-Please consult your storage or NFS server documentation for appropriate
+The SAPInstance timeout needs to be higher than the file system timeout.
+Consult your storage or NFS server documentation for appropriate
 timeout values.
 See also manual pages ocf_heartbeat_Filesystem(7), ocf_heartbeat_SAPInstance(7)
 and nfs(5).
@@ -1764,7 +1764,7 @@ See also manual pages SAPStartsrv_basic_cluster(8) and mount.nfs(8).
 
 Find below crm configuration fragments for {sap} system {mySid}. This example
 shows the specific items for the two-node cluster with priority fencing.
-This configuration is basically the same as above, except the Filesystem
+This configuration is basically the same as above, except the file system
 resources are replaced by SAPStartSrv resources.
 
 [subs="attributes"]