fixed typos

Author: bennobuilder

docs/main/Introduction.md

@@ -157,60 +157,60 @@ Without any context this section might be useless to you. As the name suggests,
 AgileTs, which are outsourced for a better overview. You might get redirected to parts of the Interface Section from
 other docs. Often to learn some more about specific properties of an interface.
 
-## ❓ Something missing
+## 💬 What others say
 
-If you find issues with the documentation or have suggestions on how to improve the documentation or the project in
-general, please [file an issue](https://github.com/agile/agile-ts/issues) for us or join
-our [Discord Community](https://discord.gg/T9GzreAwPH).
+Actually nothing, yet. If you want to be the first one, don't mind tweeting what ever you think about AgileTs.
+But don't forget to tag [@AgileFramework](https://twitter.com/AgileFramework), otherwise we can't find your tweet.
 
 ## 🌏 Creation of AgileTs
 
 After exploring the many options for Javascript State libraries, including Redux.
 I felt like I need a simpler, more straightforward solution.
 So I started searching for Redux alternatives and accidentally stumbled across a stream from [@jamiepine](https://twitter.com/jamiepine).
 Jamie was using an interesting approach of State Management which was more modular and flexible, called PulseJs.
-I instantly fell in love with the syntax of this framework.
-At this point (spring 2020) it wasn't officially released and had no documentation.
+I instantly fell in love with the concept of this framework.
+At this point (spring 2020) it wasn't officially released and had no documentation at all.
 But I tried to figure out how to use it anyway, and after some painful hours, I got it to work in my React application.
 To save others this time, I decided to write a small [pre-documentation](https://www.notion.so/bennoworkspace/Pulse-v3-No-official-Docs-4e92e8d02dd3423582fa95072806cab6) for PulseJs.
 Unfortunately, this documentation didn't make PulseJs more stable, and it remained very buggy.
 So I waited and waited until summer where still no stable version of PulseJs was released.
-In July, I decided to contribute to PulseJs, in order to help to stabilize the framework faster.
+In July, I came to the conclusion to contribute to PulseJs, in order to speed up the development process.
 But before I could contribute, I had to figure out how PulseJs works internally.
 After hours, I still couldn't figure out how it works. This was due to the fact that I wasn't very experienced in Typescript,
 and the codebase was pretty messy (no comments, variables called x, a, b, ..).
-In order to change that, I rewrote PulseJs from scratch (in a separate project)
+In order to change that, I rewrote PulseJs from scratch (in a separate project, later AgileTs)
 and after a while, I got the hang and figured out how PulseJs works internally.
 Now that I know how it works, I could finally contribute to PulseJs. My [first contribution](https://github.com/pulse-framework/pulse/commits?author=bennodev19) was on the 16th August 2020,
 where I refactored the `PulseHOC`.
 At the end of August, PulseJs was moving further and further away from my idea of an ideal State Management Framework.
 Mainly because of the introduction of the `Pulse.Core`,
-which more or less forced you to define all States, Actions in a single object called `core`
-and didn't work correctly at all.
-I wouldn't say I liked that behavior since I mainly switched to PulseJs in order not to define all my States in a single object.
-And I hadn't seen fit to rewrite my entire global State Management Logic of my applications to use the latest stable version of PulseJs.
-Another reason I turned away, was that some of my changes never got merged into the `master`. For instance, I fixed an annoying usePulse type issue,
-and 8 months later, it is still not in the `master`. Why should I contribute if my changes will never be in the release version?
-Luckily I had the refactored PulseJs lying around, which I created to learn how PulseJs works internally and released it as an own framework called
-[`agile-architecture`](https://www.npmjs.com/package/agile-architecture).
+which more or less forced you to define all States, Actions in a single object called `core`.
+And it didn't even work correctly at all.
+I wouldn't say I liked that change since I switched among others things to PulseJs in order not to define all my States in a single object.
+And I hadn't seen fit to rewrite my entire global State Management Logic of my applications to use the latest version of PulseJs.
+That I didn't even like.
+Luckily I had the refactored PulseJs version lying around, which I created to learn how PulseJs works internally and released it as an own framework called
+[agile-architecture](https://www.npmjs.com/package/agile-architecture).
 Agile-Architecture was at that point just the old refactored PulseJs without the `Pulse.Core`.
-I liked the old PulseJs more than the new PulseJs, so I stuck to my version of PulseJs.
+Another reason I turned away from PulseJs, was that some of my changes never got merged into the `master`. For instance, I fixed an annoying usePulse type issue,
+and 8 months later, it is still not merged into the `master`. Why should I contribute if my changes will never be in a release version?
 Now that I had my own State Management Framework, I adapted it to my needs and optimized it.
-Over time AgileTs has evolved away from PulseJs and can be seen as a standalone state management framework.
+Over time AgileTs has evolved away from PulseJs and can be seen as a standalone state management framework with other visions and goals.
 Today AgileTs has only a similar syntax to PulseJs. Internal, it works entirely different.
 
-Conclusion: The idea of AgileTs is based on PulseJs, and I would have loved to continue working on PulseJs.
-But the organisation was a mess, and I wasn't following the same vision anymore. 
-Therefore, I created AgileTs. To make the things better that Pulse wasn't able to accomplish.
+**Conclusion:** The idea of AgileTs is based on PulseJs, and I would have loved to continue working on PulseJs.
+But certain circumstances, such as the poor organization and different visions,
+have driven me to write my own State Manager based on the ground concept of PulseJs and MVVM frameworks.
 
 ## 🎉 Credits
 
 AgileTs is inspired by MVVM frameworks like [MobX](https://mobx.js.org/README.html)
 and [PulseJs](https://github.com/pulse-framework/pulse).
 
-## 💬 What others say
+## ❓ Something missing
 
-Actually nothing, yet. If you want to be the first one, don't mind tweeting what ever you think about AgileTs.
-But don't forget to tag [@AgileFramework](https://twitter.com/AgileFramework), otherwise we can't find your tweet.
+If you find issues with the documentation or have suggestions on how to improve the documentation or the project in
+general, please [file an issue](https://github.com/agile/agile-ts/issues) for us or join
+our [Discord Community](https://discord.gg/T9GzreAwPH).