From 7c0aa88e99cbc70942b07870fcb44b88e0f162dc Mon Sep 17 00:00:00 2001 From: Lawrence Gimenez Date: Wed, 17 Jul 2024 14:21:06 +0800 Subject: [PATCH] Documentation: Fixed typo at BrowsingContextsAndNavigables --- Documentation/Browser/BrowsingContextsAndNavigables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Browser/BrowsingContextsAndNavigables.md b/Documentation/Browser/BrowsingContextsAndNavigables.md index d67f8c07a94..66199c7d4ad 100644 --- a/Documentation/Browser/BrowsingContextsAndNavigables.md +++ b/Documentation/Browser/BrowsingContextsAndNavigables.md @@ -100,7 +100,7 @@ An Agent holds a stack of Execution Contexts, with the topmost entry being the r Each Execution Context holds a Realm and a specific script's context, including the current function and any state required to pause and resume the execution for that context. The Realm holds the Global Object for the Execution Context, and any ECMAScript or host-specific intrinsics required to create the -desired environment for code to run in. More loosely, an Agent is a specification artefact that somewhat +desired environment for code to run in. More loosely, an Agent is a specification artifact that somewhat maps the execution of a JavaScript script or module to a native thread of execution. But the specification does so in a way that allows a host/embedder to choose to switch out which Agent is currently executing its running execution context on that native thread, and which Realm within that Agent owns the running execution