cleanup NIP-52.

1 files changed, 1 insertions, 13 deletions

diff --git a/52.md b/52.md
index 4ec6836..daaf3ad 100644
--- a/52.md
+++ b/52.md
@@ -35,9 +35,6 @@ The list of tags are as follows:
 * `t` (optional, repeated) hashtag to categorize calendar event
 * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
 
-The following tags are deprecated:
-* `name` name of the calendar event. Use only if `title` is not available.
-
 ```json
 {
   "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
@@ -96,9 +93,6 @@ The list of tags are as follows:
 * `t` (optional, repeated) hashtag to categorize calendar event
 * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
 
-The following tags are deprecated:
-* `name` name of the calendar event. Use only if `title` is not available.
-
 ```json
 {
   "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
@@ -210,13 +204,7 @@ The list of tags are as follows:
 }
 ```
 
-## Unsolved Limitations
-
-* No private events
-
-## Intentionally Unsupported Scenarios
-
-### Recurring Calendar Events
+## Recurring Calendar Events
 
 Recurring calendar events come with a lot of complexity, making it difficult for software and humans to deal with. This complexity includes time zone differences between invitees, daylight savings, leap years, multiple calendar systems, one-off changes in schedule or other metadata, etc.