sophie updates

Author: react-translation-bot

content/blog/2019-02-20-react-translations.md

@@ -1,21 +1,23 @@
 ---
-title: "¡React en español! And Other Languages"
+title: "¡React en español! and Other Languages"
 author: [tesseralis]
 ---
 
 We’re excited to announce an ongoing effort to maintain official translations of the React documentation website into different languages. Thanks to the dedicated efforts of React community members from around the world, React is now being translated into *over 30* languages! You can check out our ongoing efforts in the new [Languages](/languages) page!
 
-In addition, the following three languages have completed translating the core pages of the React Docs! 🎉
+In addition, the following three languages have completed translating most of the React Docs! 🎉
 
 * Spanish: [es.reactjs.org](https://es.reactjs.org)
 * Japanese: [ja.reactjs.org](https://ja.reactjs.org)
 * Brazilian Portuguese [pt-br.reactjs.org](https://pt-br.reactjs.org)
 
+Special congratulations to the Spanish team for being the first to *completely* translate the core pages of the docs!
+
 ## Why Localization Matters
 
-React is one of the most powerful JavaScript libraries and has [meetups](https://reactjs.org/community/meetups.html) and [conferences](https://reactjs.org/community/conferences.html) all around the world. Not all of the places where React is used has English as a primary language. We'd love to support local communities who use React, and maintaining official translations is one way to do that!
+React already has many meetups and conferences around the world, but many programmers don't use English as their primary language. We’d love to support local communities who use React by making our documentation available in most popular languages.
 
-In addition, if there is enough demand in a language community, people *will* create translations for it, as people have done in [Chinese](https://github.com/discountry/react), [Arabic](https://wiki.hsoub.com/React), and [Korean](https://github.com/reactjs/ko.reactjs.org/issues/4). While useful, these resources are also hard to find. With an official translation, people can find the translated docs from the React website itself and translators have access to the React team to clarify any questions.
+In the past, React community members have created unofficial translations for [Chinese](https://github.com/discountry/react), [Arabic](https://wiki.hsoub.com/React), and [Korean](https://github.com/reactjs/ko.reactjs.org/issues/4); by making an official channel for these translated docs we're hoping to make them easier to find and help make sure that non-English-speaking users of React aren't left behind.
 
 ## Contributing
 
@@ -25,11 +27,11 @@ Can't find your language? If you'd like to maintain your langauge's translation
 
 ## Backstory
 
-Hi everyone! I'm Nat! You may know me as the [polyhedra lady](https://www.youtube.com/watch?v=Ew-UzGC8RqQ). For the past few weeks, I've been helping the React team coordinate their translation effort. Here's how I did it.
+Hi everyone! I'm [Nat](https://twitter.com/tesseralis)! You may know me as the [polyhedra lady](https://www.youtube.com/watch?v=Ew-UzGC8RqQ). For the past few weeks, I've been helping the React team coordinate their translation effort. Here's how I did it.
 
 Our original approach for translations was to use a SaaS platform that allows users to submit translations. There was already a [pull request](https://github.com/reactjs/reactjs.org/pull/873) to integrate it and my original responsibility was to finish that integration. However, we had concerns about the feasibility of that integration and the current quality of translations on the platform. Our primary concern was ensuring that translations kept up to date with the main repo and didn't become "stale".
 
-Dan encouraged me to look for alternate solutions, and we stumbled across how [Vue](https://vuejs.org) maintained its translations -- through different forks of the main repo on GitHub. In particular, the [Japanese translation](jp.vuejs.org) used a bot to periodically check for changes in the English repo and submits pull requests whenever there is a change.
+[Dan](https://twitter.com/gaearon) encouraged me to look for alternate solutions, and we stumbled across how [Vue](https://vuejs.org) maintained its translations -- through different forks of the main repo on GitHub. In particular, the [Japanese translation](jp.vuejs.org) used a bot to periodically check for changes in the English repo and submits pull requests whenever there is a change.
 
 This approach appealed to us for several reasons:
 
@@ -59,13 +61,13 @@ After lots of notepad calculations, I found a solution: delete each repo once we
 
 There were other smaller issues that I ran into. I tried using the [Heroku Scheduler](https://elements.heroku.com/addons/scheduler) add-on so I didn't have to write any actual `watch` code, but it end up running too inconsistently, and I [had an existential meltdown on Twitter](https://twitter.com/tesseralis/status/1097387938088796160) when I couldn't figure out how to send commits from the Heroku dyno. But in the end, this frontend engineer was able to get the bot working!
 
-There are, as always, improvements I want to make to the bot. Right now it doesn't check whether there is an outstanding pull request before pushing another one. It's still hard to tell the exact change that happened in the original source, and it's possible to miss out on a needed translation change. But I trust the maintainers we've chosen to work through these issues, and the bot is [open-source](https://github.com/reactjs/reactjs.org-translation) if anyone wants to help me make these improvements!
+There are, as always, improvements I want to make to the bot. Right now it doesn't check whether there is an outstanding pull request before pushing another one. It's still hard to tell the exact change that happened in the original source, and it's possible to miss out on a needed translation change. But I trust the maintainers we've chosen to work through these issues, and the bot is [open source](https://github.com/reactjs/reactjs.org-translation) if anyone wants to help me make these improvements!
 
 ## Thanks
 
 Finally, I would like to extend my gratitude to the following people and groups:
 
- * The [Vue.js Japan User Group](https://github.com/vuejs-jp) for initiating the idea of having bot-managed translations, and especially [Hanatani Takuma](https://github.com/potato4d) for helping us understand their approach and helping maintian the Japanese translation.
+ * The [Vue.js Japan User Group](https://github.com/vuejs-jp) for initiating the idea of having bot-managed translations, and especially [Hanatani Takuma](https://github.com/potato4d) for helping us understand their approach and helping maintain the Japanese translation.
  * [Soichiro Miki](https://github.com/smikitki) for many [contributions](https://github.com/reactjs/reactjs.org/pull/1636) and thoughtful comments on the overall translation process, as well as for maintaining the Japanese translation.
  * All the translation maintainers and contributors who are helping translate React to more than thirty languages.
  * The Spanish translation maintainers: [Alejandro Ñáñez Ortiz](https://github.com/alejandronanez), [Rainer Martínez Fraga](https://github.com/carburo), [David Morales](https://github.com/dmorales), and [Miguel Alejandro Bolivar Portilla](https://github.com/Darking360), and contributors for pushing the Spanish translation through the finish line!