Merge branch 'main' into css/color-interpolation-filters

Author: meyerweb

.markdownlint.jsonc

@@ -212,6 +212,19 @@
         "searchPattern": "/(\\[[^\\]]*?\\]\\(([^\\)\\n]|\\([^\\)\\n]\\)|\\s[\"'])+?)(\\n|\\s|[,:][\\s\\n])/gm",
         "searchScope": "text",
       },
+      {
+        "name": "text-code-fence",
+        "message": "Use 'plain' tag",
+        "searchPattern": "/(^ *`{3,})(text|none|unix)/gm",
+        "replace": "$1plain",
+        "searchScope": "text",
+      },
+      {
+        "name": "gfm-blockquote",
+        "message": "Use the GFM syntax: https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN#notes_warnings_and_callouts",
+        "searchPattern": "/^ *> \\*\\*(Note|Warning|Callout):\\*\\*(?! [[{`_*])/gm",
+        "searchScope": "text",
+      },
     ],
   },
 }

files/en-us/_redirects.txt

@@ -3603,6 +3603,7 @@
 /en-US/docs/Glossary/Rendering_engine	/en-US/docs/Glossary/Engine/Rendering
 /en-US/docs/Glossary/Responsive_design	/en-US/docs/Glossary/Responsive_web_design
 /en-US/docs/Glossary/Round_Trip_Time_(RTT)	/en-US/docs/Glossary/Round_Trip_Time
+/en-US/docs/Glossary/Routers	/en-US/docs/Glossary/Router
 /en-US/docs/Glossary/SRTP	/en-US/docs/Glossary/RTP
 /en-US/docs/Glossary/SSL_Glossary	/en-US/docs/Glossary/SSL
 /en-US/docs/Glossary/Scrollport	/en-US/docs/Glossary/Scroll_container
@@ -3973,7 +3974,6 @@
 /en-US/docs/HTMLSpanElement	/en-US/docs/Web/API/HTMLSpanElement
 /en-US/docs/HTMLSpanElement_interface	/en-US/docs/Web/API/HTMLSpanElement
 /en-US/docs/HTML_Intro2	/en-US/docs/Learn/HTML/Introduction_to_HTML
-/en-US/docs/HTML_Santizer_API	/en-US/docs/Web/API/HTML_Sanitizer_API
 /en-US/docs/HTML_in_XMLHttpRequest	/en-US/docs/Web/API/XMLHttpRequest_API/HTML_in_XMLHttpRequest
 /en-US/docs/HTML_intro	/en-US/docs/Learn/HTML/Introduction_to_HTML
 /en-US/docs/HTTP	/en-US/docs/Web/HTTP
@@ -8628,7 +8628,6 @@
 /en-US/docs/Web/API/HTMLVideoElement/onleavepictureinpicture	/en-US/docs/Web/API/HTMLVideoElement/leavepictureinpicture_event
 /en-US/docs/Web/API/HTMLVideoElement/requestPictureInPicture()	/en-US/docs/Web/API/HTMLVideoElement/requestPictureInPicture
 /en-US/docs/Web/API/HTML_DOM	/en-US/docs/Web/API/HTML_DOM_API
-/en-US/docs/Web/API/HTML_Santizer_API	/en-US/docs/Web/API/HTML_Sanitizer_API
 /en-US/docs/Web/API/HashChangeEvent/HashChangeEvent.oldURL	/en-US/docs/Web/API/HashChangeEvent/oldURL
 /en-US/docs/Web/API/Headers/getAll	/en-US/docs/Web/API/Headers/get
 /en-US/docs/Web/API/History.length	/en-US/docs/Web/API/History/length
@@ -9650,7 +9649,6 @@
 /en-US/docs/Web/API/SVGPathElement/pathLength	/en-US/docs/Web/API/SVGGeometryElement/pathLength
 /en-US/docs/Web/API/SVGStylable	/en-US/docs/Web/API/SVGElement
 /en-US/docs/Web/API/SVGURIReference	/en-US/docs/Web/SVG/Attribute/href
-/en-US/docs/Web/API/Sanitizer/sanitizeFor	/en-US/docs/Web/API/Sanitizer
 /en-US/docs/Web/API/Screen.availHeight	/en-US/docs/Web/API/Screen/availHeight
 /en-US/docs/Web/API/Screen.availLeft	/en-US/docs/Web/API/ScreenDetailed/availLeft
 /en-US/docs/Web/API/Screen.availTop	/en-US/docs/Web/API/ScreenDetailed/availTop

files/en-us/_wikihistory.json

@@ -41778,10 +41778,6 @@
       "Enn"
     ]
   },
-  "Web/API/HTML_Sanitizer_API": {
-    "modified": "2020-12-13T12:18:13.088Z",
-    "contributors": ["Rumyra"]
-  },
   "Web/API/HashChangeEvent": {
     "modified": "2020-10-15T21:29:11.207Z",
     "contributors": [
@@ -57386,18 +57382,6 @@
       "Jeremie"
     ]
   },
-  "Web/API/Sanitizer": {
-    "modified": "2020-12-13T12:17:05.573Z",
-    "contributors": ["Rumyra"]
-  },
-  "Web/API/Sanitizer/Sanitizer": {
-    "modified": "2020-12-13T12:21:15.482Z",
-    "contributors": ["Rumyra"]
-  },
-  "Web/API/Sanitizer/sanitize": {
-    "modified": "2020-12-13T12:25:31.511Z",
-    "contributors": ["Rumyra"]
-  },
   "Web/API/Screen": {
     "modified": "2020-10-15T21:29:41.001Z",
     "contributors": [

files/en-us/games/publishing_games/game_distribution/index.md

@@ -93,7 +93,7 @@ After you've covered Steam, there's plenty of buzz around initiatives like [Humb
 
 ## Packaging games
 
-The web is the first and the best choice for HTML games, but if you want to reach a broader audience and distribute your game in a closed ecosystem, you still can do that by packaging it. The good thing is that you don't need a few separate teams working on the same game for different platforms — you can build it once and use tools like [Phonegap](https://phonegap.com/) or [CocoonIO](http://cocoon.io/) to package the game for native stores. The resulting packages are usually pretty reliable, but you should still test them and be on the lookout for small issues or bugs to fix.
+The web is the first and the best choice for HTML games, but if you want to reach a broader audience and distribute your game in a closed ecosystem, you still can do that by packaging it. The good thing is that you don't need a few separate teams working on the same game for different platforms — you can build it once and use tools like [Phonegap](https://phonegap.com/) to package the game for native stores. The resulting packages are usually pretty reliable, but you should still test them and be on the lookout for small issues or bugs to fix.
 
 ### Available tools
 

files/en-us/games/techniques/3d_on_the_web/building_up_a_basic_demo_with_playcanvas/editor/index.md

@@ -4,6 +4,8 @@ slug: Games/Techniques/3D_on_the_web/Building_up_a_basic_demo_with_PlayCanvas/ed
 page-type: guide
 ---
 
+{{GamesSidebar}}
+
 Instead of coding everything from scratch you can also use the online **PlayCanvas editor**. This can be a more pleasant working environment if you are not someone who likes to code.
 
 ## Creating an account

files/en-us/games/techniques/control_mechanisms/desktop_with_mouse_and_keyboard/index.md

@@ -13,7 +13,7 @@ Now, when we have our mobile controls in place and the game is playable on touch
 It's also easier to test control-independent features like gameplay on desktop if you develop it there, so you don't have to push the files to a mobile device every time you make a change in the source code.
 
 > [!NOTE]
-> the [Captain Rogers: Battle at Andromeda](https://rogers2.enclavegames.com/demo/) is built with Phaser and managing the controls is Phaser-based, but it could also be done in pure JavaScript. The good thing about using Phaser is that it offers helper variables and functions for easier and faster development, but it's totally up to you which approach you chose.
+> The [Captain Rogers: Battle at Andromeda](https://rogers2.enclavegames.com/demo/) is built with Phaser and managing the controls is Phaser-based, but it could also be done in pure JavaScript. The good thing about using Phaser is that it offers helper variables and functions for easier and faster development, but it's totally up to you which approach you chose.
 
 ## Pure JavaScript approach
 

files/en-us/glossary/flex/index.md

@@ -6,7 +6,7 @@ page-type: glossary-definition
 
 {{GlossarySidebar}}
 
-`flex` is a value of the CSS {{cssxref("display")}} property. Along with `inline-flex`, it causes the element it applies to to become a {{glossary("flex container")}}, and the element's children to each become a {{glossary("flex item")}}. The items then participate in flex layout, and all of the properties defined in the [CSS flexible box layout module](/en-US/docs/Web/CSS/CSS_flexible_box_layout) may be applied.
+`flex` is a value of the CSS {{cssxref("display")}} property. Along with `inline-flex`, it causes the element it applies to become a {{glossary("flex container")}}, and the element's children to each become a {{glossary("flex item")}}. The items then participate in flex layout, and all of the properties defined in the [CSS flexible box layout module](/en-US/docs/Web/CSS/CSS_flexible_box_layout) may be applied.
 
 There is also a {{cssxref("flex")}} property, which is a shorthand for the flexbox properties {{cssxref("flex-grow")}}, {{cssxref("flex-shrink")}} and {{cssxref("flex-basis")}}. This property is only applicable to flex containers.
 

files/en-us/glossary/grid/index.md

@@ -10,7 +10,7 @@ A _CSS grid_ is defined using the `grid` value of the {{cssxref("display")}} pro
 
 The grid that you define using these properties is described as an _explicit grid_.
 
-If you place content outside of this explicit grid, or if you are relying on auto-placement and the grid algorithm needs to create additional row or column {{glossary("grid tracks", "tracks")}} to hold {{glossary("grid item", "grid items")}}, then extra tracks will be created in the implicit grid. The _implicit grid_ is the grid created automatically due to content being added outside of the tracks defined.
+If you place content outside of this explicit grid, or if you are relying on auto-placement and the grid algorithm needs to create additional row or column {{glossary("grid tracks", "tracks")}} to hold {{glossary("grid cell", "grid cells")}}, then extra tracks will be created in the implicit grid. The _implicit grid_ is the grid created automatically due to content being added outside of the tracks defined.
 
 In the example below I have created an _explicit grid_ of three columns and two rows. The _third_ row on the grid is an _implicit grid_ row track, formed due to their being more than the six items which fill the explicit tracks.
 

files/en-us/glossary/inset_properties/index.md

@@ -12,7 +12,7 @@ The inset properties include the {{cssxref("top")}}, {{cssxref("left")}}, {{cssx
 
 **Physical properties** reference specific physical sides of an element. Logical properties use directional keywords relative to the block and inline axes. **Block axis** refers to the axis that defines the stacking order of elements in a block layout. The **inline axis** is perpendicular to the block axis, representing the direction along which inline content like text flows within a block. The mapping depends on the element's {{cssxref("writing-mode")}}, {{cssxref("direction")}}, and {{cssxref("text-orientation")}}.
 
-The interpretation of inset properties depends on the value of the {{cssxref("position")}} property. When `position: absolute` is set, they represent insets from the [containing block](/en-US/docs/Web/CSS/Containing_block) or [anchor element](/en-US/docs/Web/CSS/CSS_anchor_positioning/Using). With `position: relative`, they represent insets from the box's default margin edge position. With `sticky`, they represent insets from the {{glossary("scrollport")}} edge. The `fixed` value is similar to `absolute`, except the element is positioned and sized relative to its fixed positioning containing block, which is often the viewport.
+The interpretation of inset properties depends on the value of the {{cssxref("position")}} property. When `position: absolute` is set, they represent insets from the [containing block](/en-US/docs/Web/CSS/Containing_block) or [anchor element](/en-US/docs/Web/CSS/CSS_anchor_positioning/Using). With `position: relative`, they represent insets from the box's default margin edge position. With `sticky`, they represent insets from the {{glossary("scroll container")}} edge. The `fixed` value is similar to `absolute`, except the element is positioned and sized relative to its fixed positioning containing block, which is often the viewport.
 
 ## See also
 

files/en-us/glossary/routers/index.md renamed to files/en-us/glossary/router/index.md

@@ -1,6 +1,6 @@
 ---
-title: Routers
-slug: Glossary/Routers
+title: Router
+slug: Glossary/Router
 page-type: glossary-definition
 ---