1 files changed, 3 insertions, 3 deletions
diff --git a/45.md b/45.md
index f0267f6..21dc123 100644
--- a/45.md
+++ b/45.md
@@ -6,15 +6,15 @@ Event Counts
 `draft` `optional` `author:staab`
-Relays may support the `COUNT` verb, which provides a mechanism for obtaining event counts.
+Relays may support the verb `COUNT`, which provides a mechanism for obtaining event counts.
 ## Motivation
-Some queries a client may want to execute against connected relays are prohibitively expensive, for example, in order to retrieve follower counts for a given pubkey, a client must query all kind-3 events referring to a given pubkey and count them. The result may be cached, either by a client or by a separate indexing server as an alternative, but both options erode the decentralization of the network by creating a second-layer protocol on top of Nostr.
+Some queries a client may want to execute against connected relays are prohibitively expensive, for example, in order to retrieve follower counts for a given pubkey, a client must query all kind-3 events referring to a given pubkey only to count them. The result may be cached, either by a client or by a separate indexing server as an alternative, but both options erode the decentralization of the network by creating a second-layer protocol on top of Nostr.
 ## Filters and return values
-This NIP defines the verb `COUNT`, which accepts a subscription id and filters as specified in [NIP 01](01.md).
+This NIP defines the verb `COUNT`, which accepts a subscription id and filters as specified in [NIP 01](01.md) for the verb `REQ`.
 ```
 ["COUNT", <subscription_id>, <filters JSON>...]

diff --git a/45.md b/45.md index f0267f6..21dc123 100644 --- a/45.md +++ b/45.md
@@ -6,15 +6,15 @@ Event Counts
6		6
7	`draft` `optional` `author:staab`	7	`draft` `optional` `author:staab`
8		8
9	Relays may support the `COUNT` verb, which provides a mechanism for obtaining event counts.	9	Relays may support the verb `COUNT`, which provides a mechanism for obtaining event counts.
10		10
11	## Motivation	11	## Motivation
12		12
13	Some queries a client may want to execute against connected relays are prohibitively expensive, for example, in order to retrieve follower counts for a given pubkey, a client must query all kind-3 events referring to a given pubkey and count them. The result may be cached, either by a client or by a separate indexing server as an alternative, but both options erode the decentralization of the network by creating a second-layer protocol on top of Nostr.	13	Some queries a client may want to execute against connected relays are prohibitively expensive, for example, in order to retrieve follower counts for a given pubkey, a client must query all kind-3 events referring to a given pubkey only to count them. The result may be cached, either by a client or by a separate indexing server as an alternative, but both options erode the decentralization of the network by creating a second-layer protocol on top of Nostr.
14		14
15	## Filters and return values	15	## Filters and return values
16		16
17	This NIP defines the verb `COUNT`, which accepts a subscription id and filters as specified in [NIP 01](01.md).	17	This NIP defines the verb `COUNT`, which accepts a subscription id and filters as specified in [NIP 01](01.md) for the verb `REQ`.
18		18
19	```	19	```
20	["COUNT", <subscription_id>, <filters JSON>...]	20	["COUNT", <subscription_id>, <filters JSON>...]