Fixed typos on release notes from v0_7_0 to v1_89 (#7437)

release-notes/v0_7_0.md

@@ -127,7 +127,7 @@ This includes sections on:
 ## PHP
 We added a set of common snippets for PHP.  To access these hit `kb(editor.action.triggerSuggest)` to get a context specific list.
 
-![PHP Snipets](images/0_7_0/PHPSnip.png)
+![PHP Snippets](images/0_7_0/PHPSnip.png)
 
 ## C#
 We have moved to the latest OmniSharp version 1.1.0.

release-notes/v1_13.md

@@ -166,7 +166,7 @@ Set `emmet.useNewEmmet` to `true` to start using this new feature. This feature
 If you have `editor.quickSuggestions` turned off, you can use one of the methods below to get Emmet expansion:
 
 * Manually trigger the suggestion by pressing `kb(editor.action.triggerSuggest)` and then choose the expansion from the suggestion list.
-* Run the command **Emmet: Expand Abbreviation** explicity from the **Command Palette**.
+* Run the command **Emmet: Expand Abbreviation** explicitly from the **Command Palette**.
 * Bind your own keyboard [shortcut](https://code.visualstudio.com/docs/getstarted/keybindings) to **Emmet: Expand Abbreviation** (command id `editor.emmet.action.expandAbbreviation`).
 
 You will see two kinds of suggestions in HTML-like files:

release-notes/v1_22.md

@@ -180,7 +180,7 @@ The boxes for include and exclude patterns in the Search view have been combined
 
 ### Tree: Horizontal scrolling support
 
-There's a new global setting, `workbench.tree.horizontalScrolling`, which enables horizontal scrolling for several tree widgets across the workbench. Use it to provide better readibility for wide tree elements such as deep file system hierarchies in the File Explorer.
+There's a new global setting, `workbench.tree.horizontalScrolling`, which enables horizontal scrolling for several tree widgets across the workbench. Use it to provide better readability for wide tree elements such as deep file system hierarchies in the File Explorer.
 
 ## Integrated Terminal
 

release-notes/v1_23.md

@@ -182,7 +182,7 @@ Use the **Developer: Open Process Explorer** command or **Help** > **Open Proces
 
 ### Multi-root support for terminal splitting
 
-You will now be able to select the folder to split the terminal into when inside a multi-root workspace. The old behavior can be reenabled by keybinding the `workbench.action.terminal.splitInActiveWorkspace` command.
+You will now be able to select the folder to split the terminal into when inside a multi-root workspace. The old behavior can be re-enabled by keybinding the `workbench.action.terminal.splitInActiveWorkspace` command.
 
 ## Languages
 

release-notes/v1_44.md

@@ -170,7 +170,7 @@ This change does not affect the font choice in the editor.
 
 VS Code will now keep the **Undo/Redo** stack of a file when the file is closed. When the file is reopened, if its contents hasn't changed since it was closed, the Undo/Redo stack will be restored.
 
-This is very useful if you limit the number of open editors with the `workbench.editor.limit.value` setting or you accidently close a file you are working on.
+This is very useful if you limit the number of open editors with the `workbench.editor.limit.value` setting or you accidentally close a file you are working on.
 
 ### Explicit ordering for Code Actions on save
 

release-notes/v1_65.md

@@ -562,7 +562,7 @@ The following screencast shows that the intermediate object makes it difficult t
 
 In this release, we have improved VS Code to render the intermediate object in a compact form with a **(...)** button for requesting the full value.
 
-![Reviewing property getter values with lazy evaluation triggerd by '(...)' button](images/1_65/lazy-after.gif)
+![Reviewing property getter values with lazy evaluation triggered by '(...)' button](images/1_65/lazy-after.gif)
 
 A debug adapter can request this new presentation style for a variable by adding a `VariablePresentationHint` with a `lazy` property ([see DAP additions](#debug-adapter-protocol)). If the client does not support the `lazy` flag, the variable will be shown as before.
 

release-notes/v1_70.md

@@ -500,7 +500,7 @@ On window reload, watch tasks can be reconnected to by enabling `task.experiment
 
 We have been working to provide a better experience with **Code Actions** in VS Code. [Code Actions](https://code.visualstudio.com/docs/editor/refactoring#_code-actions-quick-fixes-and-refactorings) include [Refactorings](https://code.visualstudio.com/docs/languages/typescript#_refactoring), Source Actions, and Quick Fixes.
 
-The new experimental Code Actions control can be opened from the [context menu](https://code.visualstudio.com/api/ux-guidelines/context-menus) by selecting **Refactor** or **Source Action**, from a lighbulb, or via a Quick Fix. Try it out via the `editor.experimental.useCustomCodeActionMenu` setting. Let us know about any feedback by creating issues in the [VS Code repository](https://github.com/microsoft/vscode/issues) or commenting in [issue #152913](https://github.com/microsoft/vscode/issues/152913).
+The new experimental Code Actions control can be opened from the [context menu](https://code.visualstudio.com/api/ux-guidelines/context-menus) by selecting **Refactor** or **Source Action**, from a lightbulb, or via a Quick Fix. Try it out via the `editor.experimental.useCustomCodeActionMenu` setting. Let us know about any feedback by creating issues in the [VS Code repository](https://github.com/microsoft/vscode/issues) or commenting in [issue #152913](https://github.com/microsoft/vscode/issues/152913).
 
 Refactoring previews for Code Actions are also accessible from the new Code Action control. Hover over enabled items to view how to preview. Custom keybindings are supported for selection of Code Actions, as well as to preview the selection.
 

release-notes/v1_77.md

@@ -174,7 +174,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
 
 ### Extension installation not blocked by signature verification failures
 
-Extension signature verification is incorrectly reporting errors for a small number of valid extensions and preventing them from being installed. These failures are caused by bugs in the VS Marketplace and VS Code and we are actively working on fixes. In order to unblock extension use, VS Code will install extensions even if signing verification fails. We will reenable signature verification checking once [VS Marketplace issue #619](https://github.com/microsoft/vsmarketplace/issues/619) is fixed, most likely in our next Stable release.
+Extension signature verification is incorrectly reporting errors for a small number of valid extensions and preventing them from being installed. These failures are caused by bugs in the VS Marketplace and VS Code and we are actively working on fixes. In order to unblock extension use, VS Code will install extensions even if signing verification fails. We will re-enable signature verification checking once [VS Marketplace issue #619](https://github.com/microsoft/vsmarketplace/issues/619) is fixed, most likely in our next Stable release.
 
 ## Contributions to extensions
 

release-notes/v1_89.md

@@ -453,7 +453,7 @@ This API is used by the GitHub Pull Request extension's Issues and PR views.
 
 The language model namespace (`vscode.lm`) exports new functions to retrieve language model information and to count tokens for a given string. Those are `getLanguageModelInformation` and `computeTokenLength` respectively. You should use these functions to build prompts that are within the limits of a language model.
 
-> **Note**: inline chat is now powered by the upcoming chat particpants API. This also means `registerInteractiveEditorSessionProvider` is deprecated and will be removed very soon.
+> **Note**: inline chat is now powered by the upcoming chat participants API. This also means `registerInteractiveEditorSessionProvider` is deprecated and will be removed very soon.
 
 ### Updated document paste proposal
 

release-notes/vJanuary.md

@@ -229,7 +229,7 @@ Whenever the editor contents is not loaded from the file system but comes from t
 
 ### Remote Debugging
 
-The followings improvements enable VS Code to support remote debugging, includes debugging into a Docker container:
+The following improvements enable VS Code to support remote debugging, includes debugging into a Docker container:
 
 * The `attach` launch configuration now supports an `address` attribute where a remote host can be specified. Please note that remote debugging is only supported on recent versions of Node.js (>= 4.x).
 * The `attach` launch configuration now supports a `localRoot` and a `remoteRoot` attribute that can be used to map paths between a local VS Code project and a (remote) Node.js folder. This works even locally on the same system or across different operating systems. Whenever a code path needs to be converted from the remote Node.js to a local VS Code path, the `remoteRoot` path is stripped off the path and replaced by `localRoot`. For the reverse conversion, the `localRoot` path is replaced by the `remoteRoot`.

release-notes/vMarch.md

@@ -8,7 +8,7 @@ MetaDescription: See what is new in the Visual Studio Code March 2016 Release (1
 
 ## March 2016 (1.0)
 
-March was the end game milestone leading up to our [1.0 release](/blogs/2016/04/14/vscode-1.0.md).  We wanted the product to meet the high expections of a 1.0 release and we focused on fundamentals like quality, accessibility, global reach and performance. We also added features you care about and streamlined some common tasks.
+March was the end game milestone leading up to our [1.0 release](/blogs/2016/04/14/vscode-1.0.md).  We wanted the product to meet the high expectations of a 1.0 release and we focused on fundamentals like quality, accessibility, global reach and performance. We also added features you care about and streamlined some common tasks.
 
 Here are a few highlights in this release: