1 files changed, 2 insertions, 2 deletions
diff --git a/89.md b/89.md
index 24aa3c5..dff4ea1 100644
--- a/89.md
+++ b/89.md
@@ -47,7 +47,7 @@ Multiple `a` tags can appear on the same `kind:31989`.
 The second value of the tag SHOULD be a relay hint.
 The third value of the tag SHOULD be the platform where this recommendation might apply.
-## Handler information
+### Handler information
 ```jsonc
 {
  "kind": 31990,
@@ -76,7 +76,7 @@ Multiple tags might be registered by the app, following NIP-19 nomenclature as t
 A tag without a second value in the array SHOULD be considered a generic handler for any NIP-19 entity that is not handled by a different tag.
-# Client tag
+## Client tag
 When publishing events, clients MAY include a `client` tag. Identifying the client that published the note. This tag is a tuple of `name`, `address` identifying a handler event and, a relay `hint` for finding the handler event. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this tag.
 ```jsonc

diff --git a/89.md b/89.md index 24aa3c5..dff4ea1 100644 --- a/89.md +++ b/89.md
@@ -47,7 +47,7 @@ Multiple `a` tags can appear on the same `kind:31989`.
47	The second value of the tag SHOULD be a relay hint.	47	The second value of the tag SHOULD be a relay hint.
48	The third value of the tag SHOULD be the platform where this recommendation might apply.	48	The third value of the tag SHOULD be the platform where this recommendation might apply.
49		49
50	## Handler information	50	### Handler information
51	```jsonc	51	```jsonc
52	{	52	{
53	"kind": 31990,	53	"kind": 31990,
@@ -76,7 +76,7 @@ Multiple tags might be registered by the app, following NIP-19 nomenclature as t
76		76
77	A tag without a second value in the array SHOULD be considered a generic handler for any NIP-19 entity that is not handled by a different tag.	77	A tag without a second value in the array SHOULD be considered a generic handler for any NIP-19 entity that is not handled by a different tag.
78		78
79	# Client tag	79	## Client tag
80	When publishing events, clients MAY include a `client` tag. Identifying the client that published the note. This tag is a tuple of `name`, `address` identifying a handler event and, a relay `hint` for finding the handler event. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this tag.	80	When publishing events, clients MAY include a `client` tag. Identifying the client that published the note. This tag is a tuple of `name`, `address` identifying a handler event and, a relay `hint` for finding the handler event. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this tag.
81		81
82	```jsonc	82	```jsonc