chore: typos

Author: daKmoR

README.md

@@ -10,9 +10,9 @@ I am a little afraid that I am not going to do TypeScript justice.
 The reason for that is that we are going to use it heavily - but in a rather indirect way.
 
 See - we are a big fan of a [buildless]() development setup. We have [a post]() or [two]() about it :grimmacing:
-It is [our believe](https://open-wc.org/about/rationales.html) that it is the best way to bring developers (you) and the platform (browser) back on the same table.
+It is [our belief](https://open-wc.org/about/rationales.html) that it is the best way to bring developers (you) and the platform (browser) back on the same table.
 
-Knowing this makes it hard to root for TypeScript as it is a [Transpiler Language]() - in other words it requires a build step.
+Knowing this makes it hard to root for TypeScript as it is a [Transpiler Language]() - in other words, it requires a build step.
 
 So how come we are still fans?
 Let's dive into and see what Types can give you.
@@ -40,11 +40,11 @@ export function square(number: number) {
 
 So yeah I know what you have been thinking - a string as an argument?
 While implementing we found out that it was a bad idea.
-And thanks to the power of types we can just go back to our code/tests and tada we immeditelly see in vscode that `square('two')` is not working.
+And thanks to the power of types we can just go back to our code/tests and tada we immediately see in vscode that `square('two')` is not working.
 
 ![01-ts-square-two](https://github.com/daKmoR/generate-typescript-definition-files-from-javascript/blob/master/images/01-ts-square-two.png)
 
-And we will of course get the same if we try to run `tsc`.
+And we will, of course, get the same if we try to run `tsc`.
 
 ```bash
 npm i -D typescript
@@ -72,7 +72,7 @@ expect(square(2)).to.equal(4);
 expect(square('two')).to.equal(4);
 ```
 
-For the code we removed the type
+For the code, we removed the type
 
 ```js
 // helpers.js
@@ -87,7 +87,7 @@ And our if we go back to the test now we do not see that `square('two')` is wron
 
 So that is the power of types. But we can make it work for JavaScript as well :hugs:
 
-Let's add a types via JsDoc
+Let's add types via JsDoc
 
 ```js
 /**
@@ -120,11 +120,11 @@ and configure TypeScript to check for JavaScript as well by adding a `tsconfig.j
 }
 ```
 
-Doing this allows as to get exaclty the same behavior in VSCode as with TypeScript.
+Doing this allows as to get exactly the same behaviour in VSCode as with TypeScript.
 
 ![03-js-square-two-typed](https://github.com/daKmoR/generate-typescript-definition-files-from-javascript/blob/master/images/03-js-square-two-typed.png)
 
-We even get the same behavior when running `tsc`.
+We even get the same behaviour when running `tsc`.
 
 ```bash
 $ npx tsc
@@ -168,7 +168,7 @@ export function square(number, offset = 0) {
 }
 ```
 
-In both cases it will give
+In both cases, it will give
 
 ```bash
 test/helpers.tests.js:13:22 - error TS2345: Argument of type '"ten"' is not assignable to parameter of type 'number'.
@@ -177,7 +177,7 @@ test/helpers.tests.js:13:22 - error TS2345: Argument of type '"ten"' is not assi
                         ~~~~~
 ```
 
-Also in both cases the only thing we needed to add was `offset = 0` as it contains the type information already.
+Also in both cases, the only thing we needed to add was `offset = 0` as it contains the type information already.
 
 If you wanna know more about how to use JSDoc for types I can recommend you these blog posts.
 
@@ -186,7 +186,7 @@ If you wanna know more about how to use JSDoc for types I can recommend you thes
 
 ### Publishing a library
 
-If someone is to use your code you will need to publish it. Usually that happens on npm.
+If someone is to use your code you will need to publish it. Usually, that happens on npm.
 You will also want to provide those types to your users.
 That means you will need to have `*.d.ts` files in the package you are publishing.
 As those are the only files that `TypeScript` respects by default in the `node_modules` folder.
@@ -220,13 +220,13 @@ e.g. the output of the js file is exactly the same we wrote in our js version.
 #### What does it means for JavaScript?
 
 Sadly as of now `tsc` does not support generating `*.d.ts` files from JSDoc annotated files.
-But it probably will be in the future. The original [issue](https://github.com/microsoft/TypeScript/issues/7546) is from 2016 but recently it has been said was planned for `3.6` (but it didn't make it into beta) so it seems it on the board for for `3.7`. However don't take my word for it as here is a working [Pull Request](https://github.com/microsoft/TypeScript/pull/32372).
+But it probably will be in the future. The original [issue](https://github.com/microsoft/TypeScript/issues/7546) is from 2016 but recently it has been said was planned for `3.6` (but it didn't make it into beta) so it seems it on the board for `3.7`. However, don't take my word for it as here is a working [Pull Request](https://github.com/microsoft/TypeScript/pull/32372).
 
 And it is working so great that we are using it even in production for [open-wc](https://github.com/open-wc/open-wc/blob/master/package.json#L7).
 
 > WARNING
 > This is an unsupported version => if something does not work no one is going to fix it.
-> Therefore if your usecase is not supported you will need to wait for the offical release of TypeScript to support it.
+> Therefore if your use-case is not supported you will need to wait for the official release of TypeScript to support it.
 
 So you have been warned if you still think it's a good idea to test it you feel free to do so.
 We published a forked version [typescript-temporary-fork-for-jsdoc](https://www.npmjs.com/package/typescript-temporary-fork-for-jsdoc) which is just a copy of what the above Pull Request is providing. (again to be clear - we did not change anything it is a temporary fork which is good enough for our use case).
@@ -266,7 +266,7 @@ Congratulations you now have a type safety without a build step :tada:
 
 It comes down two 2 things
 
-- Typings can be immensely useful (type safety, auto complete, documentation, ...) for you and/or your users
+- Typings can be immensely useful (type safety, auto-complete, documentation, ...) for you and/or your users
 - TypeScript is very flexible and supports types for "just" JavaScript as well
 
 Follow us on [Twitter](https://twitter.com/openwc), or follow me on my personal [Twitter](https://twitter.com/dakmor).