Update 2016-12-21-this-year.md

Author: kvark

_posts/2016-12-21-this-year.md

@@ -7,7 +7,7 @@ In 2016, Gfx-rs got wings. It was a big year for us, so let's take a moment to r
 
 It started with the adoption of the new paradigm - [Pipeline State Objects](http://gfx-rs.github.io/2016/01/22/pso.html), which improved our run-time safety checks, and paved the way to the new API backends. The implementation was further polished through the year, including raw PSO components and better error messages.
 
-Then came the D3D11 backend, which quickly got the 1st tier status. It featured two different command buffer styles: native D3D11 deferred context, and our software fallback. Windows users rejoiced having the first major D3D11 renderer in Rust. The backend proved our capability to abstract over the APIs in general, but the battle for next-gen API adoption was still ahead.
+Then came the D3D11 backend, which quickly got to 1st tier status. It features two different command buffer styles: native D3D11 deferred context, and our software fallback. Windows users rejoiced having the first major D3D11 renderer in Rust. The backend proved our capability to abstract over the APIs in general, but the battle for next-gen API adoption was still ahead.
 
 We got a [few](https://github.com/fkaa) [new](https://github.com/eugene2k) [strong](https://github.com/Bastacyclop) [contributors](https://github.com/msiglreith), bringing modern vision, ideas, and energy to the project. They [implemented](https://github.com/gfx-rs/gfx/pull/1027) [features](https://github.com/gfx-rs/gfx/pull/1026), cleaned up the [internals](https://github.com/gfx-rs/gfx/pull/1031), and added [some](https://github.com/gfx-rs/gfx/pull/1027) [new](https://github.com/gfx-rs/gfx/pull/1072) [examples](https://github.com/gfx-rs/gfx/pull/1079). Our synthetic [friend](https://github.com/ozkriff) made it possible to run Gfx-rs on Android, with a major game project using it: [ZoC](https://github.com/ozkriff/zoc).