diff --git a/xml/ay_users_groups.xml b/xml/ay_users_groups.xml
index 4ec63ce165..bd9e1f1509 100644
--- a/xml/ay_users_groups.xml
+++ b/xml/ay_users_groups.xml
@@ -116,10 +116,9 @@
        support renaming the &rootuser; account.
      </para>
      <para>
-       Usually the idea behind renaming the &rootuser; account is to hide or make it unpredictable.
+       Usually, the idea behind renaming the &rootuser; account is to hide it or make it unpredictable.
        However, <filename>/etc/passwd</filename> requires <literal>644</literal> permissions for
-       regular users, so any user of the given system is able to retrieve the login name for the
-       user ID 0.
+       regular users, so any user of the system can retrieve the login name for the user ID 0.
        <phrase os="sles;sled;osuse">For better ways to secure the &rootuser; account, refer to
          <xref linkend="sec-sec-prot-restrict-root"/> and
          <xref linkend="sec-sec-prot-restrict-root-ssh"/>.</phrase>
diff --git a/xml/deployment_yast_installer.xml b/xml/deployment_yast_installer.xml
index 8a1c5d1b6e..ba6ad23740 100644
--- a/xml/deployment_yast_installer.xml
+++ b/xml/deployment_yast_installer.xml
@@ -2108,7 +2108,7 @@ sle-live-patching 8c541494</screen>
    If you have not chosen <guimenu>Use this Password for System
    Administrator</guimenu> in the previous step, you will be prompted to enter
    a password for the system administrator &rootuser; or provide a public SSH
-   key. Otherwise this configuration step is skipped.
+   key. Otherwise, this configuration step is skipped.
   </para>
   <figure>
    <title>Authentication for the system administrator &rootuser;</title>
@@ -2128,7 +2128,7 @@ sle-live-patching 8c541494</screen>
   </figure>
    <para>
      Enter the password for the system administrator &rootuser;. For verification purposes, the
-     password for &rootuser; must be entered twice. Do not forget the password, it cannot be
+     password for &rootuser; must be entered twice. Do not forget the password as it cannot be
      retrieved later.
    </para>
   <tip>
@@ -2155,9 +2155,9 @@ sle-live-patching 8c541494</screen>
          <term>Do not forget the &rootuser; password</term>
          <listitem>
            <para>
-             Only &rootuser; has the necessary privileges to change the system configuration,
-             install programs, manage users, and set up new hardware. To carry out such tasks, the
-             &rootuser; password is required. Do not forget the password, it cannot be retrieved
+             Only &rootuser; has the privileges to change the system configuration,
+             install programs, manage users and set up new hardware. To carry out such tasks, the
+             &rootuser; password is required. Do not forget the password as it cannot be retrieved
              later.
            </para>
          </listitem>
@@ -2168,8 +2168,8 @@ sle-live-patching 8c541494</screen>
            <para>
              Logging in as &rootuser; for daily work is rather risky: Commands from &rootuser; are
              usually executed without additional confirmation, so a single mistake can lead to
-             irretrievable loss of system files. Only use the &rootuser; account for system
-             administration, maintenance, and repair.
+             an irretrievable loss of system files. Only use the &rootuser; account for system
+             administration, maintenance and repair.
            </para>
          </listitem>
        </varlistentry>
@@ -2195,10 +2195,10 @@ sle-live-patching 8c541494</screen>
              not support renaming the &rootuser; account.
            </para>
            <para>
-             Usually the idea behind renaming the &rootuser; account is to hide or make it
+             Usually, the idea behind renaming the &rootuser; account is to hide it or make it
              unpredictable. However, <filename>/etc/passwd</filename> requires
-             <literal>644</literal> permissions for regular users, so any user of the given system
-             is able to retrieve the login name for the user ID 0.
+             <literal>644</literal> permissions for regular users, so any user of the system
+             can retrieve the login name for the user ID 0.
              <phrase os="sles;sled;osuse">For better ways to secure the &rootuser; account, refer to
                <xref linkend="sec-sec-prot-restrict-root"/> and
                <xref linkend="sec-sec-prot-restrict-root-ssh"/>.</phrase>
diff --git a/xml/yast2_userman.xml b/xml/yast2_userman.xml
index a238a49c8a..f53a62e188 100644
--- a/xml/yast2_userman.xml
+++ b/xml/yast2_userman.xml
@@ -271,9 +271,9 @@
       support renaming the &rootuser; account.
     </para>
     <para>
-      Usually the idea behind renaming the &rootuser; account is to hide or make it unpredictable.
+      Usually, the idea behind renaming the &rootuser; account is to hide it or make it unpredictable.
       However, <filename>/etc/passwd</filename> requires <literal>644</literal> permissions for
-      regular users, so any user of the given system is able to retrieve the login name for the
+      regular users, so any user of the system can retrieve the login name for the
       user ID 0.
       <phrase os="sles;sled;osuse">For better ways to secure the &rootuser; account, refer to
         <xref linkend="sec-sec-prot-restrict-root"/> and