fix: fix some typos

configuration-sample/README.md

@@ -33,7 +33,7 @@ Explains how to test this extension in an Empty workspace
 - Open a different file. No message is shown.
 - Run the command `Configure empty last line for current file`
 - Value in User settings is updated. Message is shown now
-- Run the command `Configure empty last line for files` and provide abosoulte path of another file
+- Run the command `Configure empty last line for files` and provide absolute path of another file
 - Value should be updated in User Settings
 
 ### Testing Language Specific configuration
@@ -66,7 +66,7 @@ Explains how to test this extension in a Folder workspace
 - Open a different file from the opened folder. No message is shown.
 - Run the command `Configure empty last line for current file`
 - Value in Workspace settings is updated. Message is shown now.
-- Run the command `Configure empty last line for files` and provide abosoulte path of another file.
+- Run the command `Configure empty last line for files` and provide absolute path of another file.
 - Pick the target `User Settings` or `Workspace Settings` into which the value should be updated
 - Value should be updated in selected target
 
@@ -101,7 +101,7 @@ Explains how to test this extension in a Multiroot workspace
 - Open a different file from one of the root folders. No message is shown.
 - Run the command `Configure empty last line for current file`
 - Value in Folder Settings of the root folder of the current file is updated. Message is shown now.
-- Run the command `Configure empty last line for files` and provide abosoulte path of another file.
+- Run the command `Configure empty last line for files` and provide absolute path of another file.
 - Pick the target `User Settings` or `Workspace Settings` or `Workspace Folder Settings` into which the value should be updated
 - Selecting User or Workspace Settings should update the value in respective targets.
 - Selecting Workspace Folder Settings will show a Workspace Folder Picker

language-configuration-sample/README.md

@@ -5,7 +5,7 @@ This is the source code for the [Language Configuration Guide](https://code.visu
 - Comment toggling
 - Brackets definition
 - Autoclosing
-- Autosurronding
+- Autosurrounding
 - Folding
 - Word pattern
 - Indentation Rules
@@ -18,4 +18,4 @@ This is the source code for the [Language Configuration Guide](https://code.visu
 
 ## Running the Sample
 
-- Run the `Run Extension` target in the Debug View
+- Run the `Run Extension` target in the Debug View

lsp-embedded-language-service/README.md

@@ -6,7 +6,7 @@ Heavily documented sample code for https://code.visualstudio.com/api/language-ex
 
 This extension contributes a new language, `html1`. The new language is for illustration purpose and has basic syntax highlighting.
 
-This Language Server works for `html1` file. HTML1 is like HTML file but has file extension `.html1`. You can create a `test.html1` file to play with below functionaltiies:
+This Language Server works for `html1` file. HTML1 is like HTML file but has file extension `.html1`. You can create a `test.html1` file to play with below functionalities:
 
 - Completions for HTML tags
 - Completions for CSS in `<style>` tag
@@ -23,5 +23,5 @@ This Language Server works for `html1` file. HTML1 is like HTML file but has fil
 - If you want to debug the server as well use the launch configuration `Attach to Server`
 - In the [Extension Development Host] instance of VSCode, open a HTML document
   - Type `<d|` to try HTML completion
-  - Type `<style>.foo { c| }</style>` to try CSS completino
+  - Type `<style>.foo { c| }</style>` to try CSS completion
   - Have `<style>.foo { }</style>` to see CSS Diagnostics

lsp-embedded-request-forwarding/README.md

@@ -6,7 +6,7 @@ Heavily documented sample code for https://code.visualstudio.com/api/language-ex
 
 This extension contributes a new language, `html1`. The new language is for illustration purpose and has basic syntax highlighting.
 
-This Language Server works for `html1` file. HTML1 is like HTML file but has file extension `.html1`. You can create a `test.html1` file to play with below functionaltiies:
+This Language Server works for `html1` file. HTML1 is like HTML file but has file extension `.html1`. You can create a `test.html1` file to play with below functionalities:
 
 - Completions for HTML
 - Completions for CSS in `<style>` tag
@@ -22,4 +22,4 @@ This Language Server works for `html1` file. HTML1 is like HTML file but has fil
 - If you want to debug the server as well use the launch configuration `Attach to Server`
 - In the [Extension Development Host] instance of VSCode, open a HTML document
   - Type `<d|` to try HTML completion
-  - Type `<style>.foo { c| }</style>` to try CSS completino
+  - Type `<style>.foo { c| }</style>` to try CSS completion

lsp-multi-server-sample/README.md

@@ -11,5 +11,5 @@ The example uses proposed Language Server protocol. So the code demoed here migh
 - Press Ctrl+Shift+B to compile the client and server
 - Switch to the Debug viewlet
 - Select `Launch Client` from the drop down
-- Run the lauch config
-- If you want to debug the server as well use the launch configuration `Attach to Server`
+- Run the launch config
+- If you want to debug the server as well use the launch configuration `Attach to Server`

task-provider-sample/README.md

@@ -10,7 +10,7 @@ This is the source code for the [Task Provider Guide](https://code.visualstudio.
 
 ### Contribution Points
 
-- [`contributes.taskdefinitions`](https://code.visualstudio.com/api/references/contribution-points#contributes.taskDefinitions)
+- [`contributes.taskDefinitions`](https://code.visualstudio.com/api/references/contribution-points#contributes.taskDefinitions)
 
 
 ## Running the example
@@ -18,4 +18,4 @@ This is the source code for the [Task Provider Guide](https://code.visualstudio.
 - Open this example in VS Code
 - `npm install`
 - `npm run compile`
-- `F5` to start debugging
+- `F5` to start debugging

task-provider-sample/src/customTaskProvider.ts

@@ -21,7 +21,7 @@ export class CustomBuildTaskProvider implements vscode.TaskProvider {
 	static CustomBuildScriptType = 'custombuildscript';
 	private tasks: vscode.Task[] | undefined;
 
-	// We use a CustomExecution task when state needs to be shared accross runs of the task or when 
+	// We use a CustomExecution task when state needs to be shared across runs of the task or when 
 	// the task requires use of some VS Code API to run.
 	// If you don't need to share state between runs and if you don't need to execute VS Code API in your task, 
 	// then a simple ShellExecution or ProcessExecution should be enough.
@@ -132,4 +132,4 @@ class CustomBuildTaskTerminal implements vscode.Pseudoterminal {
 			}, isIncremental ? 1000 : 4000);
 		});
 	}
-}
+}