Skip to content

Commit

Permalink
Editorial: address a few nits (missing "the" and extraneous "}")
Browse files Browse the repository at this point in the history
  • Loading branch information
annevk authored Jul 8, 2024
1 parent a2f3730 commit 4393852
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -113,9 +113,9 @@ <h2>
</p>
<p>
Push messaging is best suited to occasions where there is not already an active
communications channel established between <a>user agent</a> and web application. Sending
<a>push messages</a> requires considerably more resources when compared with more direct
methods of communication such as the [[Fetch|Fetch API]] or [[Websockets|Web Sockets]].
communications channel established between the <a>user agent</a> and the web application.
Sending <a>push messages</a> requires considerably more resources when compared with more
direct methods of communication such as the [[Fetch|Fetch API]] or [[WebSockets]].
<a>Push messages</a> usually have higher latency than direct communications and they can
also be subject to restrictions on use. Most <a>push services</a> limit the size and
quantity of <a>push messages</a> that can be sent.
Expand Down Expand Up @@ -698,7 +698,7 @@ <h3>
<li>Return |promise| and continue the following steps asynchronously.
</li>
<li>Let |descriptor| be a new {{PermissionDescriptor}} with the
{{PermissionDescriptor/name}}} initialized to "push".
{{PermissionDescriptor/name}} initialized to "push".
</li>
<li>let |state| be the [=permission state=] of |descriptor| and the result.
</li>
Expand Down

0 comments on commit 4393852

Please sign in to comment.