Update typos action and fix typos (#1661)
Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
parent
560d98ba9b
commit
9fe119370b
9 changed files with 9 additions and 7 deletions
|
@ -209,7 +209,7 @@ paths:
|
|||
based on a preset.
|
||||
|
||||
If unspecified, the server should use the `visibility` to determine
|
||||
which preset to use. A visbility of `public` equates to a preset of
|
||||
which preset to use. A visibility of `public` equates to a preset of
|
||||
`public_chat` and `private` visibility equates to a preset of
|
||||
`private_chat`.
|
||||
is_direct:
|
||||
|
|
|
@ -39,7 +39,7 @@ paths:
|
|||
|
||||
In v1.7 of the specification, transmission of the generated token to an unauthenticated client is
|
||||
left as an implementation detail. Future MSCs such as [MSC3906](https://github.com/matrix-org/matrix-spec-proposals/pull/3906)
|
||||
might standarise a way to transmit the token between clients.
|
||||
might standardise a way to transmit the token between clients.
|
||||
|
||||
The generated token MUST only be valid for a single login, enforced by the server. Clients which
|
||||
intend to log in multiple devices must generate a token for each.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue