diff --git a/admin_manual/configuration_server/occ_command.rst b/admin_manual/configuration_server/occ_command.rst
index 5a2c63068..a2c336553 100644
--- a/admin_manual/configuration_server/occ_command.rst
+++ b/admin_manual/configuration_server/occ_command.rst
@@ -992,7 +992,7 @@ use the ``--force`` option to force it to check all active LDAP connections::
  sudo -u www-data php occ ldap:check-user --force robert
 
 ``ldap:check-group`` checks whether a group still exists in the LDAP directory.
-Use with ``--update`` to update group membership cache on Nextcloud side::
+Use with ``--update`` to update the group membership cache on the Nextcloud side::
 
  sudo -u www-data php occ ldap:check-group --update mygroup
 
diff --git a/admin_manual/configuration_user/user_auth_ldap.rst b/admin_manual/configuration_user/user_auth_ldap.rst
index ed8c6e4a4..6a6c70a17 100644
--- a/admin_manual/configuration_user/user_auth_ldap.rst
+++ b/admin_manual/configuration_user/user_auth_ldap.rst
@@ -796,7 +796,7 @@ in batches from all users again. Beside that they are also refreshed during a
 login for this user or can be fetched manually via the occ command 
 ``occ ldap:check-user --update USERID`` where ``USERID`` is Nextcloud's user id.
 
-For groups, a cache of memberships is stored in database to be able to fire
+For groups, a cache of memberships is stored in the database to be able to trigger
 events when a membership is added or removed. This cache is updated by a background
 job, and can be force updated using ``occ ldap:check-group --update GROUPID``.