1 files changed, 1 insertions, 1 deletions
diff --git a/34.md b/34.md
index 4989803..14c7605 100644
--- a/34.md
+++ b/34.md
@@ -53,7 +53,7 @@ An optional source of truth for the state of branches and tags in a repository.
 The `refs` tag may appear multiple times, or none.
-If no `refs` tags are present, the author is no longer tracking repository state using this event. This approach enables the author to restart tracking state at a later time unlike [NIP-09](09.md) deletion.
+If no `refs` tags are present, the author is no longer tracking repository state using this event. This approach enables the author to restart tracking state at a later time unlike [NIP-09](09.md) retraction.
 The `refs` tag can be optionally extended to enable clients to identify how many commits ahead a ref is:

diff --git a/34.md b/34.md index 4989803..14c7605 100644 --- a/34.md +++ b/34.md
@@ -53,7 +53,7 @@ An optional source of truth for the state of branches and tags in a repository.
53		53
54	The `refs` tag may appear multiple times, or none.	54	The `refs` tag may appear multiple times, or none.
55		55
56	If no `refs` tags are present, the author is no longer tracking repository state using this event. This approach enables the author to restart tracking state at a later time unlike [NIP-09](09.md) deletion.	56	If no `refs` tags are present, the author is no longer tracking repository state using this event. This approach enables the author to restart tracking state at a later time unlike [NIP-09](09.md) retraction.
57		57
58	The `refs` tag can be optionally extended to enable clients to identify how many commits ahead a ref is:	58	The `refs` tag can be optionally extended to enable clients to identify how many commits ahead a ref is:
59		59