diff options
| author | vivganes <vivek@vivekganesan.com> | 2023-04-07 17:38:03 +0530 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-04-07 11:45:06 -0300 |
| commit | 3cec80d99ebbee6b72aae31f1856181d04971244 (patch) | |
| tree | 9cbcfcc020dd370a17f5c96aa163736026a68266 /40.md | |
| parent | e219ec64701d89e6b2c3f3ca8fd426d0aefdcb9c (diff) | |
fix grammar and typos
Diffstat (limited to '40.md')
| -rw-r--r-- | 40.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -43,7 +43,7 @@ Clients SHOULD ignore events that have expired. | |||
| 43 | Relay Behavior | 43 | Relay Behavior |
| 44 | -------------- | 44 | -------------- |
| 45 | 45 | ||
| 46 | Relays MAY NOT delete an expired message immediately on expiration and MAY persist them indefinitely. | 46 | Relays MAY NOT delete expired messages immediately on expiration and MAY persist them indefinitely. |
| 47 | Relays SHOULD NOT send expired events to clients, even if they are stored. | 47 | Relays SHOULD NOT send expired events to clients, even if they are stored. |
| 48 | Relays SHOULD drop any events that are published to them if they are expired. | 48 | Relays SHOULD drop any events that are published to them if they are expired. |
| 49 | An expiration timestamp does not affect storage of ephemeral events. | 49 | An expiration timestamp does not affect storage of ephemeral events. |