Update README.md

README.md

@@ -124,9 +124,9 @@ Before you decide to use the framework for new projects, please see the followin
 > 
 > For about 10 years, I had worked on this project almost every day of my life.
 > 
-> But with the new life, there came new steps to be climbed, and I suddently had new responsabilities and things to accomplish well. I started a PhD and had to focus on it so I could not keep up maintaining the library for about three years. I tried to hire freelance developers to help maintain the project in the meantime I had to be absent, and it worked to some extent, but at some point, I did not have the resources to keep up with the development anymore. Eventually, I developed panic-level anxiety since I felt I had left so many people behind by not being able to keep up with the development of the project. At all costs, I had decided to avoid at all costs opening the issues page of the project, or even checking my own personal e-mails, to avoid receiving new inquiries about the project. 
+> But with the new life, there came new steps to be climbed, and I suddently had new responsabilities and things that I absolutely needed to accomplish very well. I started a PhD and had to focus on it so I could not keep up maintaining the library for about three years. I tried to hire freelance developers to help maintain the project in the meantime I had to be absent, and it worked to some extent, but at some point, I did not have the resources to keep up with the development anymore. Eventually, I developed panic-level anxiety since I felt I had left so many people behind by not being able to keep up with the development of the project. At all costs, I had decided to avoid at all costs opening the issues page of the project, or even checking my own personal e-mails, to avoid receiving new inquiries about the project. 
 >
-Then, a few months before my PhD defense (which happened very well, actually!), Microsoft announced that they wanted to make ML.net, which I actually fully support, the standard approach for machine learning in .NET. While this is great news (because I fully support MS giving more support for ML needs out there), this eventually meant **that Accord.NET would eventually become obsolete as ML.net was on its path to become the de-facto ML library for .NET**.
+> Then, a few months before my PhD defense (which happened very well, actually!), Microsoft announced that they wanted to make ML.net, which I actually fully support, the standard approach for machine learning in .NET. While this is great news (because I fully support MS giving more support for ML needs out there), this eventually meant **that Accord.NET would eventually become obsolete as ML.net was on its path to become the de-facto ML library for .NET**.
 > 
 > I think that the reasons above would have been already enough reasons to sustain my reasons on why I decided to not update Accord.NET anymore. However... in addition, I have to say that, as a researcher, and not solely as a developer, I have also published in, and attended to, **the most important machine learning conferences in the world to date**. And under this context, I need to say that, in the academia, **no one has ever heard of the framework or the project itself**. From my experience, people in those conferences can laugh or even mistreat you, if you mention you have ever developed anything in C#, specially for machine learning, as everyone [understandably] uses Python nowadays to accomplish tasks in this domain (I myself only use Python to do my work, and while I love C#/.NET, there is nothing that can compete with Python/Pytorch nowadays).