diff options
author | devonh <devon.dmytro@gmail.com> | 2024-04-26 18:10:45 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-04-26 18:10:45 +0000 |
commit | 0fd6b269d32340c367a67ee34b963c32da080697 (patch) | |
tree | 0ef5d2dd240fe61aee9fd42efeafd37156f7d998 /docs/user_directory.md | |
parent | Fix filtering of rooms when supplying the `destination` query parameter to `/... (diff) | |
download | synapse-0fd6b269d32340c367a67ee34b963c32da080697.tar.xz |
Fix various typos in docs (#17114)
### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))
Diffstat (limited to 'docs/user_directory.md')
-rw-r--r-- | docs/user_directory.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/user_directory.md b/docs/user_directory.md index 1271cfb862..be8664a016 100644 --- a/docs/user_directory.md +++ b/docs/user_directory.md @@ -86,9 +86,9 @@ The search term is then split into words: * If unavailable, then runs of ASCII characters, numbers, underscores, and hyphens are considered words. -The queries for PostgreSQL and SQLite are detailed below, by their overall goal +The queries for PostgreSQL and SQLite are detailed below, but their overall goal is to find matching users, preferring users who are "real" (e.g. not bots, -not deactivated). It is assumed that real users will have an display name and +not deactivated). It is assumed that real users will have a display name and avatar set. ### PostgreSQL |