mirror of https://github.com/zulip/zulip.git
api: Fix typos in doc on constructing narrows.
This commit is contained in:
parent
9a09513b4d
commit
0af7a12197
|
@ -2,9 +2,10 @@
|
||||||
|
|
||||||
A **narrow** is a set of filters for Zulip messages, that can be based
|
A **narrow** is a set of filters for Zulip messages, that can be based
|
||||||
on many different factors (like sender, stream, topic, search
|
on many different factors (like sender, stream, topic, search
|
||||||
keywords, etc.). the Zulip API (espec in the API for fetching messages).
|
keywords, etc.). Narrows are used in various places in the the Zulip
|
||||||
|
API (most importantly, in the API for fetching messages).
|
||||||
|
|
||||||
It is simplest top explain the algorithm for encoding a search as a
|
It is simplest to explain the algorithm for encoding a search as a
|
||||||
narrow using a single example. Consider the following search query
|
narrow using a single example. Consider the following search query
|
||||||
(written as it would be entered in the Zulip webapp's search box). It
|
(written as it would be entered in the Zulip webapp's search box). It
|
||||||
filters for messages sent on stream `announce`, not sent by
|
filters for messages sent on stream `announce`, not sent by
|
||||||
|
|
Loading…
Reference in New Issue