mirror of
https://github.com/nextcloud/documentation.git
synced 2025-10-26 11:18:02 +00:00
minor grammar corrections
Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com>
This commit is contained in:
parent
b6fb894c91
commit
fb517ae334
@ -458,7 +458,7 @@ A set of commands to create and manage addressbooks and calendars::
|
||||
dav:create-addressbook Create a dav addressbook
|
||||
dav:create-calendar Create a dav calendar
|
||||
dav:list-calendars List all calendars of a user
|
||||
dav:move-calendar Move a calendar from an user to another
|
||||
dav:move-calendar Move a calendar from a user to another
|
||||
dav:remove-invalid-shares Remove invalid dav shares
|
||||
dav:send-event-reminders Sends event reminders
|
||||
dav:sync-birthday-calendar Synchronizes the birthday calendar
|
||||
@ -478,13 +478,13 @@ This example creates a new calendar for molly::
|
||||
|
||||
Molly will immediately see these in the Calendar and Contacts apps.
|
||||
|
||||
``dav:lists-calendars [user]`` will display a table listing the calendars for an given user.
|
||||
``dav:lists-calendars [user]`` will display a table listing the calendars for a given user.
|
||||
This example will list all calendars for user annie::
|
||||
|
||||
sudo -u www-data php occ dav:list-calendars annie
|
||||
|
||||
``dav::move-calendar [name] [sourceuid] [destinationuid]`` allows the admin
|
||||
to move a calendar named ``name`` from an user ``sourceuid`` to the user
|
||||
to move a calendar named ``name`` from a user ``sourceuid`` to the user
|
||||
``destinationuid``. You can use the force option `-f` to enforce the move if there
|
||||
are conflicts with existing shares. You can also use the `--force-rename` option to
|
||||
have the system generate a new calendar name in case it already exists on the destination user.
|
||||
@ -1438,7 +1438,7 @@ Two-factor authentication
|
||||
-------------------------
|
||||
If a two-factor provider app is enabled, it is enabled for all users by default
|
||||
(though the provider can decide whether or not the user has to pass the challenge).
|
||||
In the case of an user losing access to the second factor (e.g. lost phone with
|
||||
In the case of a user losing access to the second factor (e.g. lost phone with
|
||||
two-factor SMS verification), the admin can try to disable the two-factor
|
||||
check for that user via the occ command::
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user