a few changes

1 files changed, 3 insertions, 3 deletions

diff --git a/_posts/2020-11-09-hi-myrtille.md b/_posts/2020-11-09-hi-myrtille.md
index 86703cb..72d8790 100644
--- a/_posts/2020-11-09-hi-myrtille.md
+++ b/_posts/2020-11-09-hi-myrtille.md
@@ -11,7 +11,7 @@ Hello, I am cedrozor the author of Myrtille, a project that started in 2007 as a
 
 It was originally the idea of UltraSam, the author of UltraVNC (another well known open source project), who was before that my project manager in a teleconferencing company based in France. But instead of the VNC protocol, we focused more on RDP because the rest of the team (including me) was more into .NET/C# development and we wanted something new in the Windows environment. That said, Myrtille relies on an abstraction layer and could easily integrate VNC or any other protocol (as it was done with SSH).
 
-We started with RDesktop, but quickly switched to FreeRDP (which is based on RDesktop), because it was just better! :)
+We started with RDesktop, but moved quickly to FreeRDP when it was released! :)
 
 ![myrtille-windows](/assets/myrtille/myrtille_windows.png){:height="95%" width="95%"}
 
@@ -31,7 +31,7 @@ From the start we decided that we didn't want any plugin, extension or whatsoeve
 
 It was even more difficult back in time (2007), because websockets and canvas (HTML5) weren't available. We had to rely on XmlHttp requests, long polling and divs (HTML 4), with of course different implementations in different browsers (no typescript back then). IE was still widely used at this time, so we wanted our PoC to run on the first version that supported XmlHttp, namely IE6 (to add even more difficulty!).
 
-That said, that was before SignalR was available to abstract and simplify network communication (automatic and transparent switching of protocols in case one of them is not available or fails). If Myrtille were to start today, I would of course make use of it (in addition to a few other libraries). Another thing I would do would be to use .NET core and the latest new stuff, in order to take Myrtille forward in the future and also have it on multiple platforms (using xfreerdp on Linux, for example). This is planned in fact, and I could use some help for it (any contribution is welcome!). Another option would be to have a commercial version of Myrtille, with a paid license to support these developments (because it's a big job and I now have to earn a living, as an independent developer).
+That said, that was before SignalR was available to abstract and simplify network communication (automatic and transparent switching of protocols in case one of them is not available or fails). If Myrtille were to start today, I would of course make use of it (in addition to a few other libraries). Another thing I would do would be to use .NET core and the latest new stuff, in order to take Myrtille forward in the future and also have it on multiple platforms (using xfreerdp on Linux, for example). This is planned in fact, and I could use some help for it (any contribution is welcome!). Another option would be to have a commercial version of Myrtille, with a paid license to support these developments (because it's a lot of work and I now have to earn a living, as an independent developer).
 
 Among the upcoming features, file transfer is the next improvement goal. Microphone support is also planned. Maybe also smart cards after that. A separation of the Myrtille gateway and services is also planned, for an easier configuration of the gateway into a DMZ, and further enhance the security (the installer will allow to select the module to be installed; currently this must be done manually). Still about security, I would like to offer another 2FA out of the box (probably Google Authenticator).
 
@@ -49,6 +49,6 @@ Whenever possible, I try to parallelize the processing. The user inputs and disp
 A path for improvement would be to use hardware accelerated graphics and take advantage of the H.264/AVC encoding supported by FreeRDP. Myrtille actually relies on images (PNG/JPEG/WEBP), generated by GDI+ (win32 API, software), but this could be replaced by a video stream (MP4/OGG/WEBM, etc.), generated by FreeRDP (against hardware, or software when using a VM), and pushed from the gateway to the browser into an HTML5 <video> tag or handled by a modern web API (MediaSource, WebRTC, etc.).
 
 # Thank you
-Many thanks to the FreeRDP team for this wonderful project! It is not an easy task when working on a closed source protocol with so little documentation and with so many changes over the years.
+Many thanks to the FreeRDP team for this wonderful project! It is not an easy task when working with such a complex protocol and with so many changes over the years.
 
 If you want to know more about Myrtille and its offered services (support, training, etc.), watch demo/tutorial videos or get in touch, you can consult our [website](https://www.myrtille.io).
\ No newline at end of file