"would be aware" -> "would become aware"

Because the improvements were done quietly, fewer people would _become_
aware of those improvements. This seems to fit in slightly better.

Author: dmitshur

_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown

@@ -17,7 +17,7 @@ Installation or upgrade instructions remain the same, even though GopherJS has a
 
 Over the last few years, GopherJS has become increasingly complete and stable. Many advanced features of the Go language spec were implemented (such as goroutines, channels, and select statements). More and more of the viable standard library packages had all their tests pass and became officially supported. Many bugs were reported, investigated, and fixed. Today, it is used by many people for a broad range of projects.
 
-However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would be aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and the fact that you can get started with it today.
+However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would become aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and the fact that you can get started with it today.
 
 In closing, we would like to thank everyone who contributed to this release of GopherJS. The Go team created and released Go 1.7. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support. Many people have contributed code and bug fixes, reported/investigated/helped reproduce issues, created libraries and wrappers for various browser APIs. Everyone's effort has helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it!