Tweak guide 06_typescript for typos & fluency

Author: mieky

packages/overmind-website/guides/beginner/06_typescript.md

@@ -1,12 +1,12 @@
 # Typescript
 
-Overmind is written in Typescript and it is written with a focus on your keeping as little time as possible helping Typescript understand what your app is all about. Typescript will spend a lot more time helping you. If you are not a Typescript developer Overmind is a really great project to start learning it as you will get the most out of the little typing you have to do.
+Overmind is written in Typescript and it is written with a focus on you dedicating as little time as possible to help Typescript understand what your app is all about. Typescript will spend a lot more time helping you. If you are not a Typescript developer Overmind is a really great project to start learning it as you will get the most out of the little typing you have to do.
 
 ## Two typing approaches
 
 ### 1. Declare module
 
-The most straight forward way to type your application is to use the **declare module** approach. This will work for most applications, but might make you feel uncomfortable as a harcore Typescripter. The reason is that we are overriding an internal type, meaning that you can only have one instance of Overmind running inside your application.
+The most straightforward way to type your application is to use the **declare module** approach. This will work for most applications, but might make you feel uncomfortable as a hardcore Typescripter. The reason is that we are overriding an internal type, meaning that you can only have one instance of Overmind running inside your application.
 
 ```marksy
 h(Example, { name: "guide/typescript/declare" })
@@ -34,7 +34,7 @@ h(Example, { name: "guide/typescript/explicit_import" })
 ```
 
 ```marksy
-h(Notice, null, "The Overmind documentation is written for implicit typing. That means whenever you see a type import directly from the Overmind package, you should rather import from your own defined types")
+h(Notice, null, "The Overmind documentation is written for implicit typing. That means whenever you see a type import directly from the Overmind package, you should rather import from your own defined types.")
 ```
 
 ## Linting
@@ -43,13 +43,13 @@ When you are using TSLint it is important that you use the official [Microsoft E
 
 ## Actions
 
-The action type takes either an input type, an output type or both.
+The action type takes either an input type, an output type, or both.
 
 ```marksy
 h(Example, { name: "guide/typescript/action" })
 ```
 
-You also have **async** version of this type. You use this when you want to define an **async** function, which implicitly returns a promise, or a function that explicitly returns a promise.
+You also have an **async** version of this type. You use this when you want to define an **async** function, which implicitly returns a promise, or a function that explicitly returns a promise.
 
 ```marksy
 h(Example, { name: "guide/typescript/async_action" })
@@ -58,13 +58,13 @@ h(Example, { name: "guide/typescript/async_action" })
 
 ## Operators
 
-Operators is like the **Action** type, it can take an optional input, but it always produces an output. By default the output of an operator is the same as the input.
+Operators is like the **Action** type: it can take an optional input, but it always produces an output. By default the output of an operator is the same as the input.
 
 ```marksy
 h(Example, { name: "guide/typescript/operatorinputsandoutputs" })
 ```
 
-The **Operator** type is used to type all operators. The type arguments you give to **Operator** has to match the specific operator you use though. So for example if you type a **mutate** operator with a different output than the input:
+The **Operator** type is used to type all operators. The type arguments you give to **Operator** have to match the specific operator you use though. So for example if you type a **mutate** operator with a different output than the input:
 
 ```marksy
 h(Example, { name: "guide/typescript/wrongoperator" })
@@ -90,7 +90,7 @@ To fix this we just add a generic type to the definition of our operator:
 h(Example, { name: "guide/typescript/operatorinfer_solution" })
 ```
 
-Now Typescript infers the input type of the operator and passes it a long.
+Now Typescript infers the input type of the operator and passes it along.
 
 ### Partial input
 
@@ -108,4 +108,4 @@ To fix this we again infer the type, but using **extends** to indicate that we d
 h(Example, { name: "guide/typescript/operatorpartial_solution" })
 ```
 
-That means this operator can handle any type that matches an **isAwesome** property, though will pass the original type through.
+That means this operator can handle any type that matches an **isAwesome** property, though will pass the original type through.