deploy: 1c02656

Author: plinss

index.html

@@ -8,7 +8,7 @@
   <meta content="Bikeshed version ac5ea272d, updated Fri Dec 6 15:45:15 2024 -0800" name="generator">
   <link href="https://www.w3.org/TR/design-principles/" rel="canonical">
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
-  <meta content="abcaba654bb1eb64b4f180d70e06c03f81e5a32d" name="revision">
+  <meta content="1c02656afb5d6202ac16356bf1f68a3ebd673b14" name="revision">
   <meta content="dark light" name="color-scheme">
   <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
 <style>
@@ -3096,9 +3096,9 @@ <h3 class="heading settled" data-level="9.3" id="usecase-oriented-apis"><span cl
 the exact lifecycle and data structures of the underlying native APIs.
 When possible, consider flexibility for new hardware.</p>
    <p>This means newly proposed APIs should be designed
-with careful consideration on how they are intended to be used
+with regard to how they are intended to be used
 rather than how the underlying hardware, device, or native API
-available today.</p>
+happens to operate today.</p>
    <h3 class="heading settled" data-level="9.4" id="hardware-is-scary"><span class="secno">9.4. </span><span class="content">Be proactive about safety</span><a class="self-link" href="#hardware-is-scary"></a></h3>
    <p>When bringing native capabilities to the web platform,
 try to design defensively.</p>