Modify key rotation request

87.md

@@ -93,7 +93,7 @@ If the admin chooses to admit the new member, they may choose one of the followi
 
 ## Key Rotation Request
 
-Any group member may request a key rotation: `26:author ?->[admin_key]`. The rumor's `content` MAY include a reason for the request, and `tags` MAY include any number of `p` tags to exclude from the key rotation. These may or may not be honored by the admin, depending on whether the author's own `p` tag is included (leaving a group), or if the author is a moderator.
+Any group member may request a key rotation: `26:author shared_key->[shared_key]`. The rumor's `content` MAY include a reason for the request, and `tags` MAY include any number of `p` tags to exclude from the key rotation. These may or may not be honored by the admin, depending on whether the author's own `p` tag is included (leaving a group), or if the author is a moderator.
 
 ```json
 {
@@ -103,6 +103,8 @@ Any group member may request a key rotation: `26:author ?->[admin_key]`. The rum
 }
 ```
 
+This event is sent to the group rather than the admin so that group members (including the sender) can optimistically update their member lists. This SHOULD be limited only to removing the author's pubkey from the group.
+
 ## Members Added Notifications
 
 When a key rotation is performed, the admin MAY publish a `27:admin_key shared_key->[shared_key]` with a `p` tag for each member in the group. The rumor MUST be addressed to the **new** shared key. This helps people build member lists and know what groups they are a part of. If the member list is very large, multiple events MAY be published with the same key, each with a subset of `p` tags.