Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-04-29 22:04:08 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

clarification: Correct wording in appservice docs (#2330)
Some checks failed
Spec / 🔎 Validate OpenAPI specifications (push) Has been cancelled
Details
Spec / 🔎 Check Event schema examples (push) Has been cancelled
Details
Spec / 🔎 Check OpenAPI definitions examples (push) Has been cancelled
Details
Spec / 🔎 Check JSON Schemas inline examples (push) Has been cancelled
Details
Spec / ⚙️ Calculate baseURL for later jobs (push) Has been cancelled
Details
Spec / 📢 Run towncrier for changelog (push) Has been cancelled
Details
Spell Check / Spell Check with Typos (push) Has been cancelled
Details
Spec / 🐍 Build OpenAPI definitions (push) Has been cancelled
Details
Spec / 📖 Build the spec (push) Has been cancelled
Details
Spec / 🔎 Validate generated HTML (push) Has been cancelled
Details
Spec / 📖 Build the historical backup spec (push) Has been cancelled
Details
Spec / Create release (push) Has been cancelled
Details

Browse source
This commit is contained in:
Guzio 2026-03-06 18:21:02 +01:00 committed by GitHub
parent fe5a195f4a
commit 0b5db68242
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelogs/application_service/newsfragments/2330.clarification Normal file
View file

@ -0,0 +1 @@
Fix various typos throughout the specification.

2
content/application-service-api.md
View file

@ -84,7 +84,7 @@ For the `users` namespace, application services can only register interest in
homeserver). Events affecting users on other homeservers are not sent to an application homeserver). Events affecting users on other homeservers are not sent to an application
service, even if the user happens to match the one of the `users` namespaces (unless, service, even if the user happens to match the one of the `users` namespaces (unless,
of course, the event affects a room that the application service is interested in of course, the event affects a room that the application service is interested in
for another room - for example, because there is another user in the room that the for another reason - for example, because there is another user in the room that the
application service is interested in). application service is interested in).
For the `rooms` and `aliases` namespaces, all events in a matching room will be For the `rooms` and `aliases` namespaces, all events in a matching room will be