diff --git a/files/en-us/learn/common_questions/tools_and_setup/what_are_browser_developer_tools/index.md b/files/en-us/learn/common_questions/tools_and_setup/what_are_browser_developer_tools/index.md index 7c4853ccbbdc00d..9e5024aa8047193 100644 --- a/files/en-us/learn/common_questions/tools_and_setup/what_are_browser_developer_tools/index.md +++ b/files/en-us/learn/common_questions/tools_and_setup/what_are_browser_developer_tools/index.md @@ -22,7 +22,6 @@ How do you pull it up? Three ways: - **_Keyboard:_** - **Windows:** Ctrl + Shift + I or F12 - - **macOS:** ⌘ + ⌥ + I - **_Menu bar:_** diff --git a/files/en-us/learn/css/styling_text/styling_links/index.md b/files/en-us/learn/css/styling_text/styling_links/index.md index 6e84b7a9b057134..93ce1fecff9f3bf 100644 --- a/files/en-us/learn/css/styling_text/styling_links/index.md +++ b/files/en-us/learn/css/styling_text/styling_links/index.md @@ -45,7 +45,6 @@ The first thing to understand is the concept of link states — different states - **Visited**: A link that has already been visited (exists in the browser's history), styled using the {{cssxref(":visited")}} pseudo class. - **Hover**: A link that is hovered over by a user's mouse pointer, styled using the {{cssxref(":hover")}} pseudo class. - **Focus**: A link that is focused (e.g., moved to by a keyboard user using the Tab key or something similar, or programmatically focused using {{domxref("HTMLElement.focus()")}}) — this is styled using the {{cssxref(":focus")}} pseudo class. - - **Active**: A link that is activated (e.g., clicked on), styled using the {{cssxref(":active")}} pseudo class. ### Default styles diff --git a/files/en-us/learn/performance/what_is_web_performance/index.md b/files/en-us/learn/performance/what_is_web_performance/index.md index 16e00ba9a35c3dc..35ac6ec5f3a8dc0 100644 --- a/files/en-us/learn/performance/what_is_web_performance/index.md +++ b/files/en-us/learn/performance/what_is_web_performance/index.md @@ -53,7 +53,6 @@ To summarize, many features impact performance including latency, application si To effectively understand web performance, the issues behind it, and the major topic areas we mentioned above, you really should understand some specifics about how browsers work. This includes: - **How the browser works**. When you request a URL and hit Enter / Return, the browser finds out where the server is that holds that website's files, establishes a connection to it, and requests the files. See [Populating the page: how the browser works](/en-US/docs/Web/Performance/How_browsers_work) for a detailed overview. - - **Source order**. Your HTML index file's source order can significantly affect performance. The download of additional assets linked to from the index file is generally sequential, based on source order, but this can be manipulated and should definitely be optimized, realizing that some resources block additional downloads until their content is parsed and executed. - **The critical path**. This is the process that the browser uses to construct the web document once the files have been downloaded from the server. The browser follows a well-defined set of steps, and optimizing the critical rendering path to prioritize the display of content that relates to the current user action will lead to significant improvements in content rendering time. See [Critical rendering path](/en-US/docs/Web/Performance/Critical_rendering_path) for more information. - The **document object model**. The document object model, or DOM, is a tree structure that represents the content and elements of your HTML as a tree of nodes. This includes all the HTML attributes and the relationships between the nodes. Extensive DOM manipulation after the pages has loaded (e.g., adding, deleting, or moving of nodes) can affect performance, so it is worth understanding how the DOM works, and how such issues can be mitigated. Find out more at [Document Object Model](/en-US/docs/Web/API/Document_Object_Model). diff --git a/files/en-us/web/api/keyboardevent/key/index.md b/files/en-us/web/api/keyboardevent/key/index.md index 22624bb66e6ae84..31935f0c7d5e111 100644 --- a/files/en-us/web/api/keyboardevent/key/index.md +++ b/files/en-us/web/api/keyboardevent/key/index.md @@ -43,7 +43,6 @@ Consider the event sequence generated when we interact with the Shift Try experimenting using the following two test cases: 1. Press and hold the Shift key, then press 2 and release it. Next, release the Shift key. - 2. Press and hold the Shift key, then press and hold 2. Release the Shift key. Finally, release 2. ### HTML