diff --git a/63.md b/63.md
index a9c673a4..1494aab9 100644
--- a/63.md
+++ b/63.md
@@ -20,7 +20,7 @@ Because normal relays won't care about these tags it's enough for the _content-c
 
 ### Membership Event
 
-Membership events must be sent directly to the relays that will implement the paywall. By default relays should not serve these events to anyone, only to the _content-creator_ directly. Because of this, these lists can be kept reasonably private as long as the _content-creator_ is discrete in their publishing, but can also be made public by being published to other relays.
+Membership events must be sent directly to the relays that will implement the paywall. By default relays should not serve these events to anyone, only to the _content-creator_ directly. Because of this, these lists can be kept reasonably private as long as the _content-creator_ is discreet in his publishing, but can also be made public by being published to other relays.
 
 The lists are constituted of one event for each _premium-reader_, and their removal/update must be done with a [NIP-09](09.md) deletion request.
 
@@ -77,6 +77,6 @@ This NIP is payment agnostic, but that doesn't mean one shouldn't use zaps or nu
 ### Future additions
 
 - more private list membership: perhaps doing an HMAC with the public key of the reader and a key that is shared with the relays will be enough for this.
-- tiered membership: custom tiers for fine-grained content access control can be added by adding more tags to the `kind:1163` event and more items to the `["nip63"]` tag.
-- teaser events: perhaps a `["nip63", "teaser"]` special tag could cause an event to be displayed only to those that do not have access to its premium counterpart, this would also be managed by the relay.
+- tiered membership: custom tiers for fine-grained content access control can be added by adding a tag like `["tier", "a"]` to the `kind:1163` event and using a `["nip63", "a"]` tag in the events, for example.
+- teaser events: perhaps a `["nip63", "", "-"]` (negative) tag could cause an event to be displayed only to those that do not have access to its premium counterpart, this would also be managed by the relay.
 - relays for premium content different from the outbox relays?