should -> ought to

source

@@ -91314,9 +91314,9 @@ scheduleWork(); // queues a task to do lots of work</pre>
   browser's <span>event loop</span>, as would be the case when using, for example, <code
   data-x="dom-setTimeout">setTimeout(<var>f</var>,&nbsp;0)</code>.</p>
 
-  <p>Authors should be aware that scheduling a lot of microtasks has the same performance downsides
-  as running a lot of synchronous code. Both will prevent the browser from doing its own work, such
-  as rendering or scrolling. In many cases, <code
+  <p>Authors ought to be aware that scheduling a lot of microtasks has the same performance
+  downsides as running a lot of synchronous code. Both will prevent the browser from doing its own
+  work, such as rendering or scrolling. In many cases, <code
   data-x="dom-window-requestAnimationFrame">requestAnimationFrame()</code> or
   <code>requestIdleCallback()</code> is a better choice. In particular, if the goal is to run code
   before the next rendering cycle, that is the purpose of <code