update

files/en-us/games/anatomy/index.md

@@ -214,7 +214,7 @@ Other methods of tackling the problem exist.
 
 One common technique is to update the simulation at a constant frequency and then draw as much (or as little) of the actual frames as possible. The update method can continue looping without care about what the user sees. The draw method can view the last update and when it happened. Since draw knows when it represents, and the simulation time for the last update, it can predict a plausible frame to draw for the user. It does not matter whether this is more frequent than the official update loop (or even less frequent). The update method sets checkpoints and, as frequently as the system allows, the render method draws instants of time around them. There are many ways to separate the update method in web standards:
 
-- Draw on `requestAnimationFrame` and update on a {{domxref("Window.setInterval", "setInterval()")}} or {{domxref("setTimeout()")}}.
+- Draw on `requestAnimationFrame()` and update on a {{domxref("Window.setInterval", "setInterval()")}} or {{domxref("setTimeout()")}}.
 
   - This uses processor time even when unfocused or minimized, hogs the main thread, and is probably an artifact of traditional game loops (but it is simple.)
 

files/en-us/games/tutorials/2d_breakout_game_pure_javascript/finishing_up/index.md

@@ -67,7 +67,7 @@ drawLives();
 
 ## Improving rendering with requestAnimationFrame()
 
-Now let's work on something that is not connected to the game mechanics, but to the way it is being rendered. {{domxref("window.requestAnimationFrame", "requestAnimationFrame")}} helps the browser render the game better than the fixed frame rate we currently have implemented using {{domxref("Window.setInterval", "setInterval()")}}. Replace the following line:
+Now let's work on something that is not connected to the game mechanics, but to the way it is being rendered. {{domxref("Window.requestAnimationFrame", "requestAnimationFrame()")}} helps the browser render the game better than the fixed frame rate we currently have implemented using {{domxref("Window.setInterval", "setInterval()")}}. Replace the following line:
 
 ```js
 interval = setInterval(draw, 10);

files/en-us/games/tutorials/2d_breakout_game_pure_javascript/move_the_ball/index.md

@@ -15,7 +15,7 @@ You already know how to draw a ball from working through the previous article, s
 ## Defining a drawing loop
 
 To keep constantly updating the canvas drawing on each frame, we need to define a drawing function that will run over and over again, with a different set of variable values each time to change sprite positions, etc. You can run a function over and over again using a JavaScript timing function.
-Later on in the tutorial, we'll see how {{domxref("Window.requestAnimationFrame()", "requestAnimationFrame()")}} helps with drawing, but we'll start with {{domxref("Window.setInterval", "setInterval()")}} at first to create some looping logic.
+Later on in the tutorial, we'll see how {{domxref("Window.requestAnimationFrame", "requestAnimationFrame()")}} helps with drawing, but we'll start with {{domxref("Window.setInterval", "setInterval()")}} at first to create some looping logic.
 
 Delete all the JavaScript you currently have inside your HTML file except for the first two lines, and add the following below them. The `draw()` function will be executed within `setInterval` every 10 milliseconds:
 

files/en-us/learn/accessibility/wai-aria_basics/index.md

@@ -220,7 +220,7 @@ Let's look at a quick example — see [`aria-no-live.html`](https://github.com/m
 </section>
 ```
 
-Our JavaScript uses the {{domxref("Window/fetch", "fetch()")}} API to load a JSON file via containing a series of random quotes and their authors. Once that is done, we start up a {{domxref("Window.setInterval", "setInterval()")}} loop that loads a new random quote into the quote box every 10 seconds:
+Our JavaScript uses the {{domxref("Window.fetch", "fetch()")}} API to load a JSON file via containing a series of random quotes and their authors. Once that is done, we start up a {{domxref("Window.setInterval", "setInterval()")}} loop that loads a new random quote into the quote box every 10 seconds:
 
 ```js
 const intervalID = setInterval(showQuote, 10000);

files/en-us/web/api/canvas_api/tutorial/basic_animations/index.md

@@ -31,7 +31,7 @@ That means we need a way to execute our drawing functions over a period of time.
 
 ### Scheduled updates
 
-First there's the {{domxref("Window.setInterval", "setInterval()")}}, {{domxref("setTimeout()")}}, and {{domxref("Window.requestAnimationFrame", "requestAnimationFrame")}} functions, which can be used to call a specific function over a set period of time.
+First there's the {{domxref("Window.setInterval", "setInterval()")}}, {{domxref("setTimeout()")}}, and {{domxref("Window.requestAnimationFrame", "requestAnimationFrame()")}} functions, which can be used to call a specific function over a set period of time.
 
 - {{domxref("Window.setInterval", "setInterval()")}}
   - : Starts repeatedly executing the function specified by `function` every `delay` milliseconds.

files/en-us/web/api/cleartimeout/index.md

@@ -82,6 +82,5 @@ exception is thrown.
 ## See also
 
 - {{domxref("setTimeout()")}}
-- {{domxref("Window.setInterval", "setInterval()")}}
-- {{domxref("Window.clearInterval", "clearInterval()")}}
-- {{domxref("Window.requestAnimationFrame()")}}
+- {{domxref("Window.clearInterval()")}} and {{domxref("WorkerGlobalScope.clearInterval()")}}
+- {{domxref("Window.cancelAnimationFrame()")}} and {{domxref("DedicatedWorkerGlobalScope.cancelAnimationFrame()")}}

files/en-us/web/api/settimeout/index.md

@@ -460,8 +460,7 @@ See also the [`clearTimeout()` example](/en-US/docs/Web/API/clearTimeout#example
 ## See also
 
 - [Polyfill of `setTimeout` which allows passing arguments to the callback in `core-js`](https://github.com/zloirock/core-js#settimeout-and-setinterval)
-- {{domxref("clearTimeout")}}
-- {{domxref("Window.setInterval", "setInterval()")}}
-- {{domxref("Window.requestAnimationFrame()")}}
-- {{domxref("Window.queueMicrotask()")}}
-- {{domxref("WorkerGlobalScope.queueMicrotask()")}}
+- {{domxref("clearTimeout()")}}
+- {{domxref("Window.setInterval()")}} and {{domxref("WorkerGlobalScope.setInterval()")}}
+- {{domxref("Window.requestAnimationFrame()")}} and {{domxref("DedicatedWorkerGlobalScope.requestAnimationFrame()")}}
+- {{domxref("Window.queueMicrotask()")}} and {{domxref("WorkerGlobalScope.queueMicrotask()")}}

files/en-us/web/api/window/clearinterval/index.md

@@ -47,8 +47,7 @@ See {{domxref("Window.setInterval", "setInterval()")}} for examples.
 
 ## See also
 
-- {{domxref("setTimeout()")}}
 - {{domxref("clearTimeout()")}}
-- {{domxref("Window.setInterval()")}}
+- {{domxref("Window.setInterval()")}} and {{domxref("WorkerGlobalScope.setInterval()")}}
 - {{domxref("WorkerGlobalScope.clearInterval()")}}
-- {{domxref("Window.requestAnimationFrame()")}}
+- {{domxref("Window.cancelAnimationFrame()")}} and {{domxref("DedicatedWorkerGlobalScope.cancelAnimationFrame()")}}

files/en-us/web/api/window/setinterval/index.md

@@ -233,7 +233,6 @@ interval has completed before recursing.
 
 - [Polyfill of `setInterval` which allows passing arguments to the callback in `core-js`](https://github.com/zloirock/core-js#settimeout-and-setinterval)
 - {{domxref("setTimeout()")}}
-- {{domxref("clearTimeout()")}}
-- {{domxref("Window.clearInterval()")}}
+- {{domxref("Window.clearInterval()")}} and {{domxref("WorkerGlobalScope.clearInterval()")}}
 - {{domxref("WorkerGlobalScope.setInterval()")}}
-- {{domxref("Window.requestAnimationFrame()")}}
+- {{domxref("Window.requestAnimationFrame()")}} and {{domxref("DedicatedWorkerGlobalScope.requestAnimationFrame()")}}

files/en-us/web/api/workerglobalscope/clearinterval/index.md

@@ -47,8 +47,7 @@ See {{domxref("Window.setInterval", "setInterval()")}} for examples.
 
 ## See also
 
-- {{domxref("setTimeout()")}}
 - {{domxref("clearTimeout()")}}
+- {{domxref("Window.setInterval()")}} and {{domxref("WorkerGlobalScope.setInterval()")}}
 - {{domxref("Window.clearInterval()")}}
-- {{domxref("WorkerGlobalScope.setInterval()")}}
-- {{domxref("Window.requestAnimationFrame()")}}
+- {{domxref("Window.cancelAnimationFrame()")}} and {{domxref("DedicatedWorkerGlobalScope.cancelAnimationFrame()")}}

files/en-us/web/api/workerglobalscope/setinterval/index.md

@@ -73,7 +73,6 @@ See the same name section under {{domxref("Window.setInterval", "setInterval()")
 
 - [Polyfill of `setInterval` which allows passing arguments to the callback in `core-js`](https://github.com/zloirock/core-js#settimeout-and-setinterval)
 - {{domxref("setTimeout()")}}
-- {{domxref("clearTimeout()")}}
+- {{domxref("Window.clearInterval()")}} and {{domxref("WorkerGlobalScope.clearInterval()")}}
 - {{domxref("Window.setInterval()")}}
-- {{domxref("WorkerGlobalScope.clearInterval()")}}
-- {{domxref("Window.requestAnimationFrame()")}}
+- {{domxref("Window.requestAnimationFrame()")}} and {{domxref("DedicatedWorkerGlobalScope.requestAnimationFrame()")}}

files/en-us/web/javascript/javascript_technologies_overview/index.md

@@ -92,7 +92,7 @@ Looking for the {{domxref("Document")}} object, {{domxref("Window")}} object, an
 - [Canvas 2D Context](https://html.spec.whatwg.org/multipage//#2dcontext) is a drawing API for [`<canvas>`](/en-US/docs/Web/HTML/Element/canvas).
 - The [WebAssembly interface](https://webassembly.github.io/spec/js-api/) provides utilities for communication between JavaScript code and [WebAssembly](/en-US/docs/WebAssembly) modules.
 
-Non-browser environments (like Node.js) often do not have DOM APIs — because they don't interact with a document — but they still usually implement many web APIs, such as [`fetch()`](/en-US/docs/Web/API/Window/fetch) and [`setTimeout()`](/en-US/docs/Web/API/setTimeout).
+Non-browser environments (like Node.js) often do not have DOM APIs — because they don't interact with a document — but they still usually implement many web APIs, such as {{domxref("Window.fetch", "fetch()")}} and [`setTimeout()`](/en-US/docs/Web/API/setTimeout).
 
 ## JavaScript implementations
 

files/en-us/web/media/autoplay_guide/index.md

@@ -226,7 +226,7 @@ In the [Web Audio API](/en-US/docs/Web/API/Web_Audio_API), a website or app can
 
 ## The autoplay Permissions Policy
 
-In addition to the browser-side management and control over autoplay functionality described above, a web server can also express its willingness to allow autoplay to function. The {{Glossary("HTTP")}} {{HTTPHeader("Permissions-Policy")}} header's [`autoplay`](/en-US/docs/Web/HTTP/Headers/Permissions-Policy/autoplay) directive is used to control which domains, if any, can be used to autoplay media. By default, the `autoplay` Permissions Policy is set to `self`, indicating that autoplay is permitted as they're hosted on the same domain as the document.
+In addition to the browser-side management and control over autoplay functionality described above, a web server can also express its willingness to allow autoplay to function. The {{Glossary("HTTP")}} {{HTTPHeader("Permissions-Policy")}} header's {{httpheader("Permissions-Policy/autoplay", "autoplay")}} directive is used to control which domains, if any, can be used to autoplay media. By default, the `autoplay` Permissions Policy is set to `self`, indicating that autoplay is permitted as they're hosted on the same domain as the document.
 
 You can also specify an empty allowlist (`()`) to disable autoplay entirely, `*` to allow autoplay from all domains, or one or more specific origins from which media can be automatically played. These origins are separated by space characters.
 

files/en-us/web/performance/fundamentals/index.md

@@ -154,7 +154,7 @@ In addition, transforms give you capabilities you might not otherwise have. Not
 
 Calls to {{domxref("Window.setInterval", "setInterval()")}} run code at a presumed frame rate that may or may not be possible under current circumstances. It tells the browser to render results even while the browser isn't actually drawing; that is, while the video hardware hasn't reached the next display cycle. This wastes processor time and can even lead to reduced battery life on the user's device.
 
-Instead, you should try to use {{domxref("window.requestAnimationFrame()")}}. This waits until the browser is actually ready to start building the next frame of your animation, and won't bother if the hardware isn't going to actually draw anything. Another benefit to this API is that animations won't run while your app isn't visible on the screen (such as if it's in the background and some other task is operating). This will save battery life and prevent users from cursing your name into the night sky.
+Instead, you should try to use {{domxref("Window.requestAnimationFrame()")}}. This waits until the browser is actually ready to start building the next frame of your animation, and won't bother if the hardware isn't going to actually draw anything. Another benefit to this API is that animations won't run while your app isn't visible on the screen (such as if it's in the background and some other task is operating). This will save battery life and prevent users from cursing your name into the night sky.
 
 #### Make events immediate