mirror of
https://github.com/zulip/zulip.git
synced 2025-11-02 13:03:29 +00:00
docs: Correct “login” as a verb to “log in”.
Signed-off-by: Anders Kaseorg <anders@zulip.com>
This commit is contained in:
committed by
Tim Abbott
parent
64b2212c23
commit
6dea085187
@@ -35,7 +35,7 @@ announcement).
|
||||
* Zulip requires CSRF tokens in all interactions with the web API to
|
||||
prevent CSRF attacks.
|
||||
|
||||
* The preferred way to login to Zulip is using an SSO solution like
|
||||
* The preferred way to log in to Zulip is using an SSO solution like
|
||||
Google Auth, LDAP, or similar, but Zulip also supports password
|
||||
authentication. See
|
||||
[the authentication methods documentation](../production/authentication-methods.md)
|
||||
@@ -184,7 +184,7 @@ strength allowed is controlled by two settings in
|
||||
* Incoming webhook bots can only send messages into Zulip.
|
||||
* Outgoing webhook bots and Generic bots can essentially do anything a
|
||||
non-administrator user can, with a few exceptions (e.g. a bot cannot
|
||||
login to the web application, register for mobile push
|
||||
log in to the web application, register for mobile push
|
||||
notifications, or create other bots).
|
||||
* API super user bots can send messages that appear to have been sent by
|
||||
another user. They also have the ability to see the names of all
|
||||
|
||||
Reference in New Issue
Block a user