Typo fixes (#1999)

Author: Chalarangelo

CONTRIBUTING.md

@@ -13,7 +13,7 @@
 Breaking any of these rules will result in your pull request being closed. Please follow these guidelines above all else:
 
 - **Always be polite and respectful to others** and try to follow the advice of the moderators/collaborators/owners.
-- **Only create or modify snippet and collecton files**, never touch the `assets` or `languages` directories or any of the files in the root directory.
+- **Only create or modify snippet and collection files**, never touch the `assets` or `languages` directories or any of the files in the root directory.
 - **Use existing templates for snippets and collections**, ensuring to follow guidelines and that files are in the correct location.
 - **Follow snippet and collection format exactly**, otherwise your content will not be recognized correctly by the tools responsible for publishing them on the website. Consult the templates or previous snippets/collections if you are unsure.
 - **Snippets should solve real-world problems**, no matter how simple and should be abstract enough to be applied to different scenarios.

snippets/js/s/event-loop-explained.md

@@ -44,7 +44,7 @@ function bar() {
 
 **Tasks** are scheduled, synchronous blocks of code. While executing, they have exclusive access to the Call Stack and can also enqueue other tasks. Between Tasks, the browser can perform rendering updates. Tasks are stored in the **Task Queue**, waiting to be executed by their associated functions. The Task Queue, in turn, is a FIFO (First In, First Out) data structure. Examples of Tasks include the callback function of an event listener associated with an event and the callback of `setTimeout()`.
 
-### Microtasks an the Microtask Queue
+### Microtasks and the Microtask Queue
 
 **Microtasks** are similar to Tasks in that they're scheduled, synchronous blocks of code with exclusive access to the Call Stack while executing. Additionally, they are stored in their own FIFO (First In, First Out) data structure, the **Microtask Queue**. Microtasks differ from Tasks, however, in that the Microtask Queue must be emptied out after a Task completes and before re-rendering. Examples of Microtasks include `Promise` callbacks and `MutationObserver` callbacks.