A small iteration

website/src/_posts/2019-04-1.0.md

@@ -32,7 +32,7 @@ Sometimes, however, you might like to add a drag-and-drop surface with file prev
 
 Then there's also the issue of large files, where resumability is essential. It's basically unacceptable in this day and age to still have to restart your upload from scratch, just because your WiFi had a hiccup. That's why Uppy uses Tus, the open protocol for resumable file uploading.
 
-All these things significantly improve the user experience to the point where more files actually make it to your platform, and less users rage-quit and close the tab. These things become important when uploading is a central aspect of your website or app. Uppy can also be deployed with nothing but a JS tag, using an existing `<form>` for fallback (to support IE6! :), and your Apache/Nginx server.
+All these things significantly improve the user experience to the point where more files actually make it to your platform, and less users rage-quit and close the tab. These things become important when uploading is a central aspect of your website or app. Uppy can also be deployed with nothing but a JS tag, using an existing `<form>` for fallback (to support IE6! :smile:), and your Apache/Nginx server.
 
 ## Building a team to create Uppy
 
@@ -60,7 +60,7 @@ Read more [about Golden Retriever and that team meetup](https://uppy.io/blog/201
 
 We had been postponing the 1.0 release for quite some time. There’s always just one more feature you'd like to add or another bug you want to fix, before calling something ready for a 1.0 release. Truth be told, Uppy has been [used in production](https://github.com/transloadit/uppy#used-by) for a while already, and even though we iterate and change things frequently, the API had mostly stabilized.
 
-So, about a month ago, we decided to pull the trigger and [announced an Uppy Month](https://uppy.io/blog/2019/03/liftoff-01/) within Transloadit. This meant that all team members, including those not working primarily on Uppy — the Tus core team, our SDK teams, as well as our infra and API engineers, designers, content writers, and the founders themselves — all chipped in and did their part to ensure liftoff in thirty days. We also asked [Evgenia](http://github.com/lakesare) to join us for the month to land a hand with frontend work. Every week, we had a call where we looked at the [Asana](https://asana.com/) Uppy 1.0 project board and talked about our progress.
+So, about a month ago, we decided to pull the trigger and [announced an Uppy Month](https://uppy.io/blog/2019/03/liftoff-01/) within Transloadit. This meant that all team members, including those not working primarily on Uppy — the Tus core team, our SDK teams, as well as our infra and API engineers, designers, content writers, and the founders themselves — all chipped in and did their part to ensure liftoff in thirty days. We also asked [Evgenia](http://github.com/lakesare) to join us for the month to lend a hand with frontend work. Every week, we had a call where we looked at the [Asana](https://asana.com/) Uppy 1.0 project board and talked about our progress.
 
 Here are some highlights of what we’ve managed to deliver during one month of Everything Uppy:
 
@@ -103,7 +103,7 @@ We felt that Uppy is straightforward enough to use, and presets could end up mak
 
 Instead of going for `{ theme: 'dark' }`, we only offer theming via CSS. It is, of course, very feasible to create a `dark.css` file, and maybe we can come up with a section on the site for easily sharing and distributing such files, but we let go of this desire for Uppy 1.0.
 
-And we did not ship Google Photos or Box support. We hope these are things that the community can help with. So, while we didn't tick all the boxes, for a three-year gameplan, we are very happy with this result.
+We also did not ship Google Photos or Box support. We hope these are things that the community can help with. So, while we didn't tick all the boxes, for a three-year gameplan, we are very happy with this result.
 
 ## What’s next for Uppy?
 
@@ -113,4 +113,4 @@ There are still quite a lot of [issues](https://github.com/transloadit/uppy/issu
 
 Uppy has already seen serious usage by a seriously large community and by various serious enterprises. So, with 1.0, we're now also signaling to you: Hey, we take this seriously and we won't be swapping things out from under your app, just like that. Also, if you don't yet have Uppy powering your file uploads, now is the best time to give it a shot!
 
-We hope your users will be as delighted by Uppy 1.0 as we have been designing and building it, and seeing your support and contributions while doing so. It makes all the difference. Thank you so much!
+We hope your users will be as delighted by Uppy 1.0 as we have been designing and building it. Seeing your support and contributions while doing so, made all the difference. Thank you so much!