[pull] main from mdn:main

files/en-us/learn_web_development/core/scripting/a_first_splash/index.md

@@ -509,7 +509,7 @@ All we have left to do now in this article is to talk about a few other importan
 
 Above, we mentioned **Loops**, a very important concept in programming, which allow you to keep running a piece of code over and over again, until a certain condition is met.
 
-Let's explore a basic example to show you with this means. Go to your [browser developer tools JavaScript console](/en-US/docs/Learn_web_development/Howto/Tools_and_setup/What_are_browser_developer_tools) again, paste the following code into it, and press <kbd>Enter</kbd>/<kbd>Return</kbd>:
+Let's explore a basic example to show you what this means. Go to your [browser developer tools JavaScript console](/en-US/docs/Learn_web_development/Howto/Tools_and_setup/What_are_browser_developer_tools) again, paste the following code into it, and press <kbd>Enter</kbd>/<kbd>Return</kbd>:
 
 ```js
 const fruits = ["apples", "bananas", "cherries"];

files/en-us/mdn/writing_guidelines/howto/markdown_in_mdn/index.md

@@ -20,7 +20,7 @@ The GFM specification defines two basic types of links:
 - [inline links](https://github.github.com/gfm/#inline-link), in which the destination is given immediately after the link text.
 - [reference links](https://github.github.com/gfm/#reference-link), in which the destination is defined elsewhere in the document.
 
-On MDN we prefer to use inline links because they are easier to read and maintain without loosing context. This is the preferred way to write links on MDN:
+On MDN we prefer to use inline links because they are easier to read and maintain without losing context. This is the preferred way to write links on MDN:
 
 ```md
 [Macarons](https://en.wikipedia.org/wiki/Macaron) are delicious but tricky to make.

files/en-us/web/api/htmlelement/command_event/index.md

@@ -35,7 +35,7 @@ const popover = document.getElementById("mypopover");
 // …
 
 popover.addEventListener("command", (event) => {
-  if (event.action === "show-popover") {
+  if (event.command === "show-popover") {
     console.log("Popover is about to be shown");
   }
 });

files/en-us/web/css/guides/cascade/shorthand_properties/index.md

@@ -15,7 +15,11 @@ There are a few edge cases to keep in mind when using shorthand properties.
 
 ### Omitting properties
 
-A value which is not specified is set to its initial value. That means that it **overrides** previously set values. For example:
+A value which is not specified is set to a default value defined by the shorthand,
+which may differ from the property's initial value.
+
+That means that it **overrides** previously set values.
+For example:
 
 ```css
 p {

files/en-us/web/html/reference/elements/input/search/index.md

@@ -467,7 +467,7 @@ You can see a good example of a search form used in context at our [website-aria
       <td><strong>Implicit ARIA Role</strong></td>
       <td>
         with no <code>list</code> attribute:
-        <code><a href="/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/textbox_role">searchbox</a></code><br />
+        <code><a href="/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/searchbox_role">searchbox</a></code><br />
         with <code>list</code> attribute: <code><a href="/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/combobox_role">combobox</a></code>
       </td>
     </tr>