From 0af7a12197e281879aa2ba3ec732e3b352a84acf Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Mon, 27 Aug 2018 17:37:37 -0700 Subject: [PATCH] api: Fix typos in doc on constructing narrows. --- templates/zerver/api/construct-narrow.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/templates/zerver/api/construct-narrow.md b/templates/zerver/api/construct-narrow.md index 37048b0340..4f43904b49 100644 --- a/templates/zerver/api/construct-narrow.md +++ b/templates/zerver/api/construct-narrow.md @@ -2,9 +2,10 @@ A **narrow** is a set of filters for Zulip messages, that can be based 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 (written as it would be entered in the Zulip webapp's search box). It filters for messages sent on stream `announce`, not sent by