Merge branch 'search-lunr' of github.com:benhalverson/nodejs.dev into…

… search-lunr

package.json

@@ -130,7 +130,7 @@
     "prettier": "^2.4.1",
     "remark-cli": "^10.0.0",
     "remark-frontmatter": "^4.0.0",
-    "remark-preset-lint-node": "^3.1.0",
+    "remark-preset-lint-node": "^3.2.0",
     "stylelint": "^13.13.1",
     "stylelint-config-prettier": "^8.0.2",
     "stylelint-config-recommended-scss": "^4.3.0",

src/documentation/0029-node-event-loop/index.md

@@ -144,7 +144,7 @@ Why is this happening?
 
 When setTimeout() is called, the Browser or Node.js starts the timer. Once the timer expires, in this case immediately as we put 0 as the timeout, the callback function is put in the **Message Queue**.
 
-The Message Queue is also where user-initiated events like click or keyboard events, or fetch responses are queued before your code has the opportunity to react to them. Or also DOM events like `onLoad`.
+The Message Queue is also where user-initiated events like click or keyboard events, or fetch responses are queued before your code has the opportunity to react to them. Or also DOM events like `onload`.
 
 **The loop gives priority to the call stack, and it first processes everything it finds in the call stack, and once there's nothing in there, it goes to pick up things in the message queue.**