Fix spelling mistakes across Markdown docs (#331)

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rzhao271 <7199958+rzhao271@users.noreply.github.com>

December-Test-Plan.md

@@ -11,7 +11,7 @@ Verify that long text now nicely wraps across multiple lines in the debug repl b
 - [x] linux @aeschli 
 
 We have changed breakpoints states and now show it differently in the UI. Verify:
-* new UI properly and intuitivly reflects if breakpoints are enabled, disabled, verified, or deactivated. 
+* new UI properly and intuitively reflects if breakpoints are enabled, disabled, verified, or deactivated. 
 * breakpoints get hit / not hit depending on their enablement state
 
 ### Debug - extension debugging

Feature-Areas.md

@@ -32,6 +32,6 @@ In addition there can be feature sub areas which are colored light blue.
 |||
 |api|vscode extension API||
 |install-update|install and update of vscode||
-|accessiblity|accessibility support||
+|accessibility|accessibility support||
 |i18n|internationalization - Code, translation error||
 |L10N|New UI language request in loc platform for language pack extension||

Keybinding-Issues.md

@@ -43,7 +43,7 @@ The first keydown event is for the `MetaLeft` key (`cmd`) and cannot be dispatch
   * Are you connecting to the Linux machine via some form of virtualization or remote desktop software?
     * **symptoms**: e.g. pressing <kbd>AltGr</kbd> acts as `Backspace`, pressing <kbd>C</kbd> acts as `ArrowLeft`, etc.
     * **solution**: use `"keyboard.dispatch": "keyCode"` in your settings and restart VS Code.
-    * **explanation**: VS Code on Linux dispatches keybindings using scan codes to accomodate various keyboard layouts. This works well when sitting physically at the machine and the OS is the one creating keyboard events, but some virtualization / remote desktop software creates keyboard events with incorrect scan codes.
+    * **explanation**: VS Code on Linux dispatches keybindings using scan codes to accommodate various keyboard layouts. This works well when sitting physically at the machine and the OS is the one creating keyboard events, but some virtualization / remote desktop software creates keyboard events with incorrect scan codes.
 
   * Are you switching keyboard layouts while VS Code is running?
     * **symptoms**: VS Code keybindings reflect the keyboard layout that was active when VS Code was launched.

Known-issues.md

@@ -19,5 +19,5 @@ reported by [**alexey-kozlenkov**](https://github.com/Microsoft/vscode/issues/12
 
 reported by [**rcdmk**](https://github.com/Microsoft/vscode/issues/12637#issuecomment-277464550)
  > I have another trick that does work as long as I keep focus on the VS code window: 
- > 1. Tap with tree fingers, so Search/Cortana pannel shows up to the left of screen. 
+ > 1. Tap with three fingers, so Search/Cortana panel shows up to the left of screen. 
  > 2. Swipe with two fingers over the VS code window and notice that the document does scroll

Lists-And-Trees.md

@@ -26,7 +26,7 @@ Apart from being a virtual rendering engine, the `List` provides quite a lot of
 
 ### Index Tree
 
-A tree UI widget should be able to represent tree-like data, eg. a file explorer. A rendered tree can always be rendered as a list; it is each row's indentation level and twistie indicators which give the user the perception of tree structure. By leveraging the virtual rendering functionalites of the list we can use composition to create a tree widget.
+A tree UI widget should be able to represent tree-like data, eg. a file explorer. A rendered tree can always be rendered as a list; it is each row's indentation level and twistie indicators which give the user the perception of tree structure. By leveraging the virtual rendering functionalities of the list we can use composition to create a tree widget.
 
 There is the question of API: how can we keep a tree-like structure API relatively simple, yet allow for complex operations, such as removing and inserting whole subtrees? If we take the same `splice` analogy as the list's (pick a location, remove some elements and add other elements), it's possible to come up with a tree `splice` call, in which the location is multi-dimensional (the first element of the `start` array represents the index in the root's children array; the `n`-th element of the `start` array represents the index in the `n - 1`-th children array) and the elements to insert are entire subtrees.
 
@@ -95,4 +95,4 @@ Here are the results from profiling all these cases on the same machine along wi
 | **Filter to One** | 970 ms | 78 ms | 12.4x |
 | **Collapse All** | 30.000 ms 😱 | 625 ms | **48x** 😎 |
 
-While the speedup results are impressive, some of the absolute values are still unnaceptable: 625ms for collapsing all tree nodes will eat up a large chunk of JavaScript time, drastically reducing our frame rate, even if collapsing all nodes is a punctual operation. The good news is that there is still lots of room for improvement, given that we now have a solid algorithm and data structure foundation on which can iterate much easier. Stay tuned!
+While the speedup results are impressive, some of the absolute values are still unacceptable: 625ms for collapsing all tree nodes will eat up a large chunk of JavaScript time, drastically reducing our frame rate, even if collapsing all nodes is a punctual operation. The good news is that there is still lots of room for improvement, given that we now have a solid algorithm and data structure foundation on which can iterate much easier. Stay tuned!

Notebook-documentation.md

@@ -29,7 +29,7 @@ Since we are using the `TextModelResolverService` for cell's text model resoluti
 
 ## Viewport rendering
 
-The viewport rendering of notebook list view is a "guess and validate" process. It will calcuate how many cells/rows it can render within the viewport first, have them all rendered, and then ask for their real dimensions, and based on the cell/row dimensions it will decide if it needs to render more cells (if there is still some room in the viewport) or remove a few.
+The viewport rendering of notebook list view is a "guess and validate" process. It will calculate how many cells/rows it can render within the viewport first, have them all rendered, and then ask for their real dimensions, and based on the cell/row dimensions it will decide if it needs to render more cells (if there is still some room in the viewport) or remove a few.
 
 For short, the process is more or less
 
@@ -103,7 +103,7 @@ Since most elements' positions are absolute and there is latency between the two
 * Fewer layout messages between the main and iframe
 * Less flickering and forced reflow on scrolling
 
-While we continue optimizing the layout code, we need to make sure that the new optimization won't lead to regression in above three aspects. Here is a list of existing optimziations we already have and we want to make sure they still perform well when updating layout code.
+While we continue optimizing the layout code, we need to make sure that the new optimization won't lead to regression in above three aspects. Here is a list of existing optimizations we already have and we want to make sure they still perform well when updating layout code.
 
 ## Avoid flickering on resize of cells above current viewport
 
@@ -164,7 +164,7 @@ will genrate text output `2`. The re-rendering of the output is fast and we want
 	2. In 200ms, we will reset the output height to `0`, unless there is a new output rendered
 2. Received new output
 	1. Re-render the new output
-	2. Calcuate the height of the new output, update layout
+	2. Calculate the height of the new output, update layout
 
 
 If the new output is rendered within 200ms, users won't see the UI movement.
@@ -192,7 +192,7 @@ We also warm up all rendered markdown in the document, from top to bottom, when
   * require our own serialization/deserialization
 * Performance
   * `window.find` can be slow
-    * We currently travese the DOM tree to figure out which cell/output contain the find match belongs to, it's really costly. One idea is checking the absolute position of the find match and compare it with output container positions.
+    * We currently traverse the DOM tree to figure out which cell/output contain the find match belongs to, it's really costly. One idea is checking the absolute position of the find match and compare it with output container positions.
   * Search only rendered outputs
     * MutationObserver for output change
 	* Change active selection to the beginning of the new output and then request `window.find`

Roadmap-2020.md

@@ -217,7 +217,7 @@ VS Code is made possible through a wide range of technologies. Below are example
 
 ## Explorations
 
-- [ ] Explore support to synchronize more state when opening the same folder in different VS Code installs such as  untitled files, open files, focussed editor.
+- [ ] Explore support to synchronize more state when opening the same folder in different VS Code installs such as  untitled files, open files, focused editor.
 - [ ] Explore how to better provide support for low-end devices.
 - [ ] :runner: Explore how to support new user in learning VS Code (interactive exploration mode, videos)  
 - [ ] Explore how to make it easier to show, tell, and share your VS Code customizations.

Search-Issues.md

@@ -8,7 +8,7 @@ Besides `.gitignore`, we also look at the `.ignore`, `.rgignore`, and `.git/info
 
 > **Tip**: You can set `"search.useIgnoreFiles": false` to disable using the `.gitignore` file for search
 
-An easy way to validate whether exclude setttings or ignore files are affecting your search is to turn off the "Use Exclude Settings and Ignore Files" button in the search viewlet. This is the gear button in the lower right corner:
+An easy way to validate whether exclude settings or ignore files are affecting your search is to turn off the "Use Exclude Settings and Ignore Files" button in the search viewlet. This is the gear button in the lower right corner:
 
 ![Use Exclude Settings and Ignore Files button](https://user-images.githubusercontent.com/8586769/132767680-dd9048dc-beef-4849-a5cd-2cfadcd01e19.png)
 

VS-Code-Speech.md

@@ -14,7 +14,7 @@ Install the [GitHub Copilot Chat](https://marketplace.visualstudio.com/items?ite
 
 ## Keybindings
 
-For a quick experience of starting to listen from the microphone and submitting when done you can assign the following keybinding squence:
+For a quick experience of starting to listen from the microphone and submitting when done you can assign the following keybinding sequence:
 
 ```json
 {