@@ -136,7 +136,7 @@ users need to be able to expect that merely visiting any given link
136
136
won't have implications for the security of their computer,
137
137
or for any essential aspects of their [privacy] (https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy).
138
138
139
- For example, an API which allows any website to
139
+ For example, an API that allows any website to
140
140
[detect the use of assistive technologies] (#do-not-expose-use-of-assistive-tech)
141
141
may make users of these technologies feel unsafe visiting unknown web pages,
142
142
since any web page may detect this private information.
@@ -441,7 +441,7 @@ A font picker (high level API)
441
441
over a Font Enumeration API (low level API)
442
442
as it addresses the bulk of use cases,
443
443
while preserving user privacy,
444
- as it is free from the the fingerprinting concerns that accompany
444
+ as it is free from the fingerprinting concerns that accompany
445
445
a general Font Enumeration API.
446
446
A native font picker also comes with accessibility built-in,
447
447
and provides consistency for end users.
@@ -1797,7 +1797,7 @@ geolocation.read({ signal });
1797
1797
</div>
1798
1798
1799
1799
Using `AbortSignal` consistently
1800
- as the way to cancel an asychronous operation
1800
+ as the way to cancel an asynchronous operation
1801
1801
means that authors can write less complex code.
1802
1802
1803
1803
For example, there's a pattern of using a single `AbortSignal`
@@ -2549,7 +2549,7 @@ See also:
2549
2549
Look for ways to avoid enumerating devices.
2550
2550
If you can't avoid it, expose the least information possible.
2551
2551
2552
- If an API exposes the the existence, capabilities, or identifiers of more than one device,
2552
+ If an API exposes the existence, capabilities, or identifiers of more than one device,
2553
2553
all of the risks in [[#device-ids]]
2554
2554
are multiplied by the number of devices.
2555
2555
For the same reasons,
0 commit comments