3 files changed, 22 insertions, 7 deletions

diff --git a/05.md b/05.md
index a67f530..992983f 100644
--- a/05.md
+++ b/05.md
@@ -50,7 +50,7 @@ or with the **optional** `"relays"` attribute:
 
 If the pubkey matches the one given in `"names"` (as in the example above) that means the association is right and the `"nip05"` identifier is valid and can be displayed.
 
-The optional `"relays"` attribute may contain an object with public keys as properties and arrays of relay URLs as values. When present, that can be used to help clients learn in which relays a that user may be found. Web servers which serve `/.well-known/nostr.json` files dynamically based on the query string SHOULD also serve the relays data for any name they serve in the same reply when that is available.
+The optional `"relays"` attribute may contain an object with public keys as properties and arrays of relay URLs as values. When present, that can be used to help clients learn in which relays that user may be found. Web servers which serve `/.well-known/nostr.json` files dynamically based on the query string SHOULD also serve the relays data for any name they serve in the same reply when that is available.
 
 ## Finding users from their NIP-05 identifier
 
diff --git a/26.md b/26.md
index 955a043..0f8f64a 100644
--- a/26.md
+++ b/26.md
@@ -38,20 +38,34 @@ The following fields and operators are supported in the above query string:
 *Fields*:
 1. `kind`
    -  *Operators*:
-      -  `=${KIND_NUMBER}` - delegatee may only sign events of this kind
+      -  `=${KIND_NUMBERS}` - delegatee may only sign events of listed kind(s) (comma-separated)
 2. `created_at`
    -  *Operators*:
-      -  `<${TIMESTAMP}` - delegatee may only sign events created ***before*** the specified timestamp
-      -  `>${TIMESTAMP}` - delegatee may only sign events created ***after*** the specified timestamp
+      -  `<${TIMESTAMP}` - delegatee may only sign events whose `created_at` is ***before*** the specified timestamp
+      -  `>${TIMESTAMP}` - delegatee may only sign events whose `created_at` is ***after*** the specified timestamp
 
-In order to create a single condition, you must use a supported field and operator. Multiple conditions can be used in a single query string, including on the same field. Conditions must be combined with `&`.
+Multiple conditions can be used in a single query string, including on the same field. Conditions must be combined with `&`.
 
-For example, the following condition strings are valid:
+Multiple conditions should be treated as `AND` requirements; all conditions must be true for the delegated event to be valid.
+
+Multiple comma-separated `kind` values should be interpreted as:
+```
+# kind=0,1,3000
+... AND (kind == 0 OR kind == 1 OR kind == 3000) AND ...
+```
 
+For example, the following condition strings are valid:
+- `kind=1`
+- `created_at<1675721813`
 - `kind=1&created_at<1675721813`
-- `kind=0&kind=1&created_at>1675721813`
+- `kind=0,1,3000&created_at>1675721813`
 - `kind=1&created_at>1674777689&created_at<1675721813`
 
+However, specifying multiple _separate_ `kind` conditions is impossible to satisfy:
+- `kind=1&kind=5`
+
+There is no way for an event to satisfy the `AND` requirement of being both `kind`s simultaneously.
+
 For the vast majority of use-cases, it is advisable that query strings should include a `created_at` ***after*** condition reflecting the current time, to prevent the delegatee from publishing historic notes on the delegator's behalf.
 
 #### Example
diff --git a/README.md b/README.md
index e7ab5ec..24ade62 100644
--- a/README.md
+++ b/README.md
@@ -50,6 +50,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
 | 45-49       | Public Chat Reserved        | [28](28.md)            |
 | 10002       | Relay List Metadata         | [65](65.md)            |
 | 22242       | Client Authentication       | [42](42.md)            |
+| 1000-9999   | Regular Events Reserved     | [16](16.md)            |
 | 10000-19999 | Replaceable Events Reserved | [16](16.md)            |
 | 20000-29999 | Ephemeral Events Reserved   | [16](16.md)            |
 | 30000-39999 | Param. Repl. Events Reserved| [33](33.md)            |