fix typo

Author: mkwtys

docs/compiler/scanner.md

@@ -14,7 +14,7 @@ Here is a *simplied* version of the actual code in the parser that you can run d
 ```ts
 import * as ts from "ntypescript";
 
-// TypeScript has a singelton scanner
+// TypeScript has a singleton scanner
 const scanner = ts.createScanner(ts.ScriptTarget.Latest, /*skipTrivia*/ true);
 
 // That is initialized using a function `initializeState` similar to

docs/staging/generators.md

@@ -31,7 +31,7 @@ console.log(iterator.next()); // 2
 Now that you have seen `function*`, `yield` and `.next()` we can dig deeper.
 
 #### Catching Errors
-Any errors thrown (intentially using `throw` or unintentionally due to error) from the generator can be caught using `try/catch` just like normal function executions. This is demonstrated below:
+Any errors thrown (intentionally using `throw` or unintentionally due to error) from the generator can be caught using `try/catch` just like normal function executions. This is demonstrated below:
 
 ```ts
 function* wholeNumbers() {

docs/styleguide/styleguide.md

@@ -258,7 +258,7 @@ const foo: string = "hello";
 > Reasons: Its easier to read. Its used by the TypeScript team. Makes easier to know something is an array as the mind is trained to detect `[]`.
 
 ## Filename
-Name files with `camelCase`. E.g. `accordian.tsx`, `myControl.tsx`, `utils.ts`, `map.ts` etc.
+Name files with `camelCase`. E.g. `accordion.tsx`, `myControl.tsx`, `utils.ts`, `map.ts` etc.
 
 > Reason: Conventional across many JS teams.
 

docs/tips/nominalTyping.md

@@ -18,7 +18,7 @@ type Id<T extends string> = {
 type FooId = Id<'foo'>;
 type BarId = Id<'bar'>;
 
-/** Optional: contructors functions */
+/** Optional: constructors functions */
 const createFoo = (value: string): FooId => ({ type: 'foo', value });
 const createBar = (value: string): BarId => ({ type: 'bar', value });
 

docs/types/index-signatures.md

@@ -301,7 +301,7 @@ type FormState =
   & { [fieldName: string]: FieldState }
 
 
-// Use it for some JavaScript object you are gettting from somewhere 
+// Use it for some JavaScript object you are getting from somewhere 
 declare const foo:FormState; 
 
 const isValidBool = foo.isValid;

docs/types/never.md

@@ -21,7 +21,7 @@ However, *only `never` can be assigned to another never*. e.g.
 let foo: never = 123; // Error: Type number is not assignable to never
 
 // Okay as the function's return type is `never`
-let bar: never = (() => { throw new Error('Throw my hands in the air like I just dont care') })();
+let bar: never = (() => { throw new Error(`Throw my hands in the air like I just don't care`) })();
 ```
 
 Great. Now let's just jump into its key use case :)

docs/types/typeGuard.md

@@ -81,7 +81,7 @@ doStuff(new Bar());
 
 ### in 
 
-The `in` operator does a safe check for the existance of a property on an object and can be used as a type guard. E.g. 
+The `in` operator does a safe check for the existence of a property on an object and can be used as a type guard. E.g. 
 
 ```ts
 interface A {

docs/why-typescript.md

@@ -141,7 +141,7 @@ var inc = x => x+1;
 In this section we have provided you with the motivation and design goals of TypeScript. With this out of the way we can dig into the nitty gritty details of TypeScript.
 
 [](Interfaces are open ended)
-[](Type Inferernce rules)
+[](Type Inference rules)
 [](Cover all the annotations)
 [](Cover all ambients : also that there are no runtime enforcement)
 [](.ts vs. .d.ts)