Editorial: Clarify Agent Clusters note 4: Terminology and wording (tc…

…39#899)

spec.html

@@ -6433,7 +6433,7 @@ <h1>Agent Clusters</h1>
     <p>An embedding may deactivate (stop forward progress) or activate (resume forward progress) an agent without the agent's knowledge or cooperation.  If the embedding does so, it must not leave some agents in the cluster active while other agents in the cluster are deactivated indefinitely.</p>
 
     <emu-note>
-      <p>The purpose of the preceding restriction is to avoid a situation where an agent deadlocks or starves because another agent has been suspended.  For example, if a DOM SharedWorker shares memory with a regular worker, and the regular worker is suspended while it holds a lock (because the web page the regular worker is in is pushed into the window history), and the SharedWorker tries to acquire the lock, then the SharedWorker will be blocked until the regular worker wakes up again, if ever.  Meanwhile other workers trying to access the SharedWorker from other web pages will starve.</p>
+      <p>The purpose of the preceding restriction is to avoid a situation where an agent deadlocks or starves because another agent has been deactivated.  For example, if an HTML shared worker that has a lifetime independent of documents in any windows were allowed to share memory with the dedicated worker of such an independent document, and the document and its dedicated worker were to be deactivated while the dedicated worker holds a lock (say, the document is pushed into its window's history), and the shared worker then tries to acquire the lock, then the shared worker will be blocked until the dedicated worker is activated again, if ever.  Meanwhile other workers trying to access the shared worker from other windows will starve.</p>
 
       <p>The implication of the restriction is that it will not be possible to share memory between agents that don't belong to the same suspend/wake collective within the embedding.</p>
     </emu-note>