diff --git a/index.html b/index.html
index 2eeaf06..295228c 100644
--- a/index.html
+++ b/index.html
@@ -978,7 +978,7 @@
};
- PushMessageData objects have an associated bytes (a [=byte sequence=]),
+ {{PushMessageData}} objects have an associated bytes (a [=byte sequence=]),
which is set on creation.
@@ -1123,32 +1123,29 @@
Let |subscription| be the active push subscription for |registration|.
- Initialize |data| to a value of `null`.
+ Let |bytes| be null.
- If the push message contains a payload, perform the following steps:
+ If the push message contains a payload:
- - Decrypt the push message using the private key from the key pair
- associated with |subscription| and the process described in [[RFC8291]]. This
- produces the plain text of the message.
+
- Decrypt the push message payload using the private key from the key pair
+ associated with |subscription| and the process described in [[RFC8291]]. Set |bytes|
+ to the resulting [=/byte sequence=].
- - If the push message could not be decrypted for any reason, perform the
- following steps:
+
- If the push message payload could not be decrypted for any reason:
- Acknowledge the receipt of the push message according to [[RFC8030]].
Though the message was not successfully received and processed, this prevents the
push service from attempting to retransmit the message; a badly encrypted message
is not recoverable.
- - Discard the push message.
+
- Abort these steps.
- - Terminate this process.
-
-
A `push` event MUST NOT be fired for a push message that was not
- successfully decrypted using the key pair associated with the push
- subscription.
-
- - Let |data| be a new PushMessageData instance with the decrypted plain text
- of the push message.
+
+
+ A `push` event will not be fired for a push message that was not
+ successfully decrypted using the key pair associated with the push
+ subscription.
+
@@ -1162,7 +1159,7 @@
`data`
- |data|
+ A new {{PushMessageData}} object whose [=bytes=] is |bytes|.