fix some spelling mistakes, fix grammar

Code-Editor-Roadmap.md

@@ -15,7 +15,7 @@
 * [issue #15579](https://github.com/Microsoft/vscode/issues/15579): Regex search issue
   * seed search string only if the selection is created explicitly (i.e. not due to a find match)
 * Widget size/position
-  * [x] Make it resizeable: [#2657](https://github.com/Microsoft/vscode/issues/2657), [#2220](https://github.com/Microsoft/vscode/issues/2220)
+  * [x] Make it resize-able: [#2657](https://github.com/Microsoft/vscode/issues/2657), [#2220](https://github.com/Microsoft/vscode/issues/2220)
   * [x] Bug, Replace Box in Current File Truncated [#5861](https://github.com/Microsoft/vscode/issues/5861)
   * [x] Cover search result: [#5525](https://github.com/Microsoft/vscode/issues/5525)
 * Multiline search

Code-Organization.md

@@ -1,4 +1,4 @@
-Code consists of a layered and modular `core` that can be extended using extensions. Extensions are run in a separate process refered to as the
+Code consists of a layered and modular `core` that can be extended using extensions. Extensions are run in a separate process referred to as the
 `extension host.` Extensions are implemented by utilizing the [extension API](https://code.visualstudio.com/docs/extensions/overview).
 
 # Layers
@@ -24,7 +24,7 @@ The `core` of Code is fully implemented in [TypeScript](https://github.com/micro
 
 # Dependency Injection
 
-The code is organised around services of which most are defined in the `platform` layer. Services get to its clients via `constructor injection`. 
+The code is organized around services of which most are defined in the `platform` layer. Services get to its clients via `constructor injection`. 
 
 A service definition is two parts: (1) the interface of a service, and (2) a service identifier - the latter is required because TypeScript doesn't use nominal but structural typing. A service identifier is a decoration (as proposed for ES7) and should have the same name as the service interface. 
 

December-Pre-Release.md

@@ -4,7 +4,7 @@ A pre-release of the [December update](../issues/917) is now available on the so
 
 We love getting feedback on the pre-release and you can help us in many ways:
 - test new features as described in the [[December Test Plan]].
-- verify the bugs you have filed and that are targetting the December milestone [bug fixes](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+label%3Abug+milestone%3A%22Dec+2015%22).
+- verify the bugs you have filed and that are targeting the December milestone [bug fixes](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+label%3Abug+milestone%3A%22Dec+2015%22).
 
 ## Reporting Issues
 When reporting issues please mention in the comment that you found the issue in the `insiders` release and follow our reporting issues guidelines [[Submitting-Bugs-and-Suggestions]].

Extension-API-process.md

@@ -1,7 +1,7 @@
 Extension API Process
 =
 
-The goal of this process is to be transparent about how API is created, what phases a proposal goes through, and to know what proposals are finalised when. Still, we want to maintain flexibility in making API. 
+The goal of this process is to be transparent about how API is created, what phases a proposal goes through, and to know what proposals are finalized when. Still, we want to maintain flexibility in making API. 
 
 About Proposed API
 --

Extension-Authoring:-Adopting-Multi-Root-Workspace-APIs.md

@@ -197,7 +197,7 @@ Under the hood, resource settings are resolved with a simple logic: We try to fi
 ### Perspectives
 An extension author, you should have following two perspectives while defining a setting
 
-1. **End User:** Given a setting, an end user should know where he/she can customise this setting. By defining a setting as `resource` or `window` scoped, user can be able customise it at right targets. It means, User can open settings and can customise a window (`window.zoomLevel`) or resource (`editor.wordWrap`) setting  in User/Workspace Settings. But when user lands into Folder Settings, user can only customise resource settings (`editor.wordWrap`). VS Code will use the setting's classification information to provide right proposals in intelli-sense and will warn user if customising `window` settings in Folder settings. 
+1. **End User:** Given a setting, an end user should know where he/she can customise this setting. By defining a setting as `resource` or `window` scoped, user can be able customise it at right targets. It means, User can open settings and can customise a window (`window.zoomLevel`) or resource (`editor.wordWrap`) setting  in User/Workspace Settings. But when user lands into Folder Settings, user can only customise resource settings (`editor.wordWrap`). VS Code will use the setting's classification information to provide right proposals in intelli-sense and will warn user if customising `window` settings in Folder settings.
 
 2. **Extension author:** Extension author's main purpose is to define a setting and read its value and apply it. As mentioned before now, there is a new target `Folder Settings` where a resource scoped setting can only be customisable. So extension author should be knowing if a setting is associated to a resource or not and thereby, classify the setting. If it is a resource setting, ask for the value of the setting by passing the resource for which the value has to be applied. Otherwise you can just ask for the value without passing any resource. API will give you back the value user customised for this setting.
 

Issue-Tracking.md

@@ -64,7 +64,7 @@ During the iteration planning process we use the following sources as input:
 - Review feature requests with many reactions.
 Issues we plan to work on during an iteration are assigned to the current milestone.
 
-## Filing bugs as development team member
+## Filing bugs as a development team member
 When team members files a bug they perform steps of the inbox tracker for the issue they filed. Therefore bugs filed by the development team do not need to be triaged by the inbox tracker. 
  
 ## Verification
@@ -111,4 +111,4 @@ To enable planning across repositories all the Visual Studio Code related reposi
 ## Iteration Planning
 We use issues for iteration plans and the wiki for the test plan. 
 - Iteration Plans have a label `iteration-plan` with `tasks` [ ] for the different items. The individual items are tracked in existing issues (bugs, feature requests). If there is no existing issue then a new issue with the label `plan-item` is created. Here is an [example](https://github.com/Microsoft/vscode/issues/917).
-- We use a wiki page for a test plan. Here is an [example](https://github.com/Microsoft/vscode/wiki/December-Test-Plan).
+- We use a wiki page for a test plan. Here is an [example](https://github.com/Microsoft/vscode/wiki/December-Test-Plan).