Reword/drop “must"s in dev view of Workers section

Author: sideshowbarker

source

@@ -96833,10 +96833,10 @@ interface <dfn>DedicatedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span>
 
   <p><code>DedicatedWorkerGlobalScope</code> objects act as if they had an implicit
   <code>MessagePort</code> associated with them. This port is part of a channel that is set up when
-  the worker is created, but it is not exposed. This object must never be garbage collected before
-  the <code>DedicatedWorkerGlobalScope</code> object.</p>
+  the worker is created, but it is not exposed.<span w-nodev> This object must never be garbage
+  collected before the <code>DedicatedWorkerGlobalScope</code> object.</span></p>
 
-  <p>All messages received by that port must immediately be retargeted at the
+  <p w-nodev>All messages received by that port must immediately be retargeted at the
   <code>DedicatedWorkerGlobalScope</code> object.</p>
 
   <dl class="domintro">
@@ -96988,15 +96988,15 @@ interface <dfn>SharedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span> {
 
   <p>Each <code>WorkerGlobalScope</code> object also has a <dfn
   data-x="dom-WorkerGlobalScope-closing" data-export="" data-dfn-type="dfn"
-  data-dfn-for="WorkerGlobalScope">closing</dfn> flag, which must initially be false, but which can
-  get set to true <span w-nodev>by the algorithms in the processing model section below</span><span
-  w-nohtml>when the worker is requested to close</span>.</p>
+  data-dfn-for="WorkerGlobalScope">closing</dfn> flag, <span w-nodev>which must be</span> initially
+  false, but which can get set to true <span w-nodev>by the algorithms in the processing model
+  section below</span><span w-nohtml>when the worker is requested to close</span>.</p>
 
   <p>Once the <code>WorkerGlobalScope</code>'s <span
   data-x="dom-WorkerGlobalScope-closing">closing</span> flag is set to true, the <span>event
-  loop</span>'s <span data-x="task queue">task queues</span> must discard any further <span
-  data-x="concept-task">tasks</span> that would be added to them (tasks already on the queue are
-  unaffected except where otherwise specified). Effectively, once the <span
+  loop</span>'s <span data-x="task queue">task queues</span> <span w-nodev>must</span> discard any
+  further <span data-x="concept-task">tasks</span> that would be added to them (tasks already on the
+  queue are unaffected except where otherwise specified). Effectively, once the <span
   data-x="dom-WorkerGlobalScope-closing">closing</span> flag is true, timers stop firing,
   notifications for all pending background operations are dropped, etc.</p>
 
@@ -97346,24 +97346,25 @@ interface <dfn>SharedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span> {
   <h4>Runtime script errors</h4>
 
   <p>Whenever an uncaught runtime script error occurs in one of the worker's scripts, if the error
-  did not occur while handling a previous script error, the user agent must <span>report the
-  error</span> for that <span data-x="concept-script">script</span>, with the position (line number
-  and column number) where the error occurred, using the <code>WorkerGlobalScope</code> object as
-  the target.</p>
+  did not occur while handling a previous script error, the user agent <span w-nodev>must</span>
+  <span w-nohtml>will</span> <span>report the error</span> for that <span
+  data-x="concept-script">script</span>, with the position (line number and column number) where the
+  error occurred, using the <code>WorkerGlobalScope</code> object as the target.</p>
 
   <p>For shared workers, if the error is still <i data-x="concept-error-nothandled">not handled</i>
   afterwards, the error may be reported to a developer console.</p>
 
   <p>For dedicated workers, if the error is still <i data-x="concept-error-nothandled">not
-  handled</i> afterwards, the user agent <span w-nodev>must <span>queue a task</span> to run these
-  steps:</span><span w-nohtml>will fire an <code data-x="event-error">error</code> event at the
-  <code>Worker</code> object.</span></p>
+  handled</i> afterwards, <span w-nohtml>the error report propagates to the <code>Worker</code>
+  object, then to any containing workers in the same fashion, eventually reaching the
+  <code>Window</code> if it was never handled along the way.</span><span w-nodev>the user agent must
+  <span>queue a task</span> to run these steps:</span></p>
 
   <div w-nodev>
 
   <ol>
    <li><p>Let <var>notHandled</var> be the result of <span data-x="concept-event-fire">firing an
-   event</span> named <code data-x="event-error">error</code> at <code>Worker</code> object
+   event</span> named <code data-x="event-error">error</code> at the <code>Worker</code> object
    associated with the worker, using <code>ErrorEvent</code>, with the <code
    data-x="dom-Event-cancelable">cancelable</code> attribute initialized to true, the <code
    data-x="dom-ErrorEvent-message">message</code>, <code
@@ -97383,14 +97384,14 @@ interface <dfn>SharedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span> {
   if that worker's <code data-x="handler-WorkerGlobalScope-onerror">onerror</code> attribute was
   null, but must otherwise act as described above.</p>
 
-  <p class="note">Thus, error reports propagate up to the chain of dedicated workers up to the
-  original <code>Document</code>, even if some of the workers along this chain have been terminated
-  and garbage collected.</p>
+  </div>
 
-  <p>The <span>task source</span> for the task mentioned above is the <span>DOM manipulation task
-  source</span>.</p>
+  <p class="note"><span w-nodev>Thus, error</span><span w-nohtml>Error</span> reports propagate up
+  to the chain of dedicated workers up to the original <code>Document</code>, even if some of the
+  workers along this chain have been terminated and garbage collected.</p>
 
-  </div>
+  <p w-nodev>The <span>task source</span> for the task mentioned above is the <span>DOM manipulation
+  task source</span>.</p>
 
 
   <h4>Creating workers</h4>