More copy edits

docs/blog/2017-12-20-introducing-the-gatsby-ux-research-program/index.md

@@ -6,17 +6,19 @@ author: "Shannon Soper"
 
 ## How this all started
 
-After teaching college-level writing and training sales people for the last several years, I’d been contemplating a career change. Earlier this year my brother suggested that UX design could be a natural fit as we drove past [red rock cliffs](https://utah.com/hiking/st-george) on a road trip in Utah. After serious reflection, I applied to a UX bootcamp and got in. Fast-forward to August where Kyle Mathews and I are sitting with a bunch of friends in a dry grass field in Idaho, waiting for the solar eclipse. We’ve been friends since college, and he asked if I’d be interested in doing UX interviews for Gatsby. 
+After teaching college-level writing and training sales people for the last several years, I’d been contemplating a career change. Earlier this year on a car trip with my brother near the [red rock cliffs](https://utah.com/hiking/st-george) of southern Utah, he suggested that UX design could be a natural fit. After serious reflection, I applied to a UX bootcamp for this fall and got in.
 
-I’d been watching Gatsby grow from the beginning and felt enthusiastic about the chance to dive deep into a project with passionate community members working on such an interesting project. I saw that UX research would inform the community how to maintain and enhance Gatsby’s awesome developer experience.
+Fast-forward now to August where Kyle Mathews and I are sitting with friends in a dry grass field in Idaho, waiting for the solar eclipse. We’ve been friends since college, and he asked if I’d be interested in doing UX interviews for Gatsby. 
 
-All this leads me to this blog post, in which I’d like to summarize the research I’ve done with GatsbyJS users the past few months and how it’s informing upcoming projects and design decisions. If you already use GatsbyJS, I hope you’ll compare your experience with the following results and [let me know](https://twitter.com/shannonb_ux/status/938551014956732418) if you have more feedback that is not reflected in our data. If you don’t use GatsbyJS and would like to, it’d be great to start with these [tutorials](/tutorial/) and by following us on [Twitter](https://twitter.com/gatsbyjs).
+I’d been watching Gatsby grow from the beginning and felt enthusiastic about the chance to dive deep into a project with passionate community members working on such an interesting project. I saw that UX research would help inform the community how to maintain and enhance Gatsby’s awesome developer experience.
+
+Which this leads me to this blog post. Here I'll summarize the research I’ve done with GatsbyJS users the past few months and how it’s informing upcoming projects and design decisions. If you already use GatsbyJS, I hope you’ll compare your experience with the following results and [let me know](https://twitter.com/shannonb_ux/status/938551014956732418) if you have more feedback that is not reflected in our data. If you don’t use GatsbyJS and would like to, perhaps start with the [official tutorials](/tutorial/) and by following us on [Twitter](https://twitter.com/gatsbyjs).
 
 ## Why do UX research for Gatsby?
 
 One of the goals of Gatsby is to enable an awesome developer experience. UX research encourages continual feedback from the community to help guide us towards that goal. To gather feedback, I started reaching out to Gatsby users through Twitter and Discord and wow, the response has been amazing! Many people have generously offered to chat over the phone, Google hangouts, Discord, email, and more to tell me their experiences. These interviews allowed me to talk with a wide breadth of people and get in-depth information about the Gatsby development experience.
 
-To gather more feedback, we also added a question at the bottom of each doc and tutorial that says: “Was this page helpful?” with thumbs-up and thumbs-down icons. In the future, we’ll implement more feedback systems to help us understand Gatsby users even more.
+To gather more feedback, we also added a question at the bottom of each doc and tutorial that asks: “Was this page helpful?” with thumbs-up and thumbs-down icons. In the future, we’ll implement more feedback systems to help us understand Gatsby users even more.
 
 In interviews, I ask open-ended questions that are intended to gather candid feedback:
 
@@ -51,21 +53,21 @@ About 73% of interviewees are developers, with UX designers being the next bigge
 
 ### What types of sites do people build with Gatsby?
 
-Most sites built with Gatsby are blogs or a combined portfolio plus blog, with sites for work being the second most common type of site built with Gatsby. 
+Most sites built with Gatsby are blogs or a combined portfolio plus blog. Sites for work are the second most common type of site. 
 
-People working on bigger work projects experienced pain points including how to build complex navigation and menu bars and how to handle complex workflows that involve multiple writers and editors.
+It was interesting to hear that people working on larger projects (most often for work) experienced pain points including how to build complex navigation and menu bars and how to handle complex workflows that involve multiple writers and editors.
 
 ![Gatsby Sites](sites.png)
 
 ### What are the top 10 pain points of Gatsby users?
 
-Plugin-related issues take home the gold medal for biggest pain point; many more people than we expected are interested in plugins and have struggled to find the plugin they need,to make sure the plugin they find isn’t going to break their site, or to build a new plugin.
+Plugin-related issues take home the gold medal for the most common pain point; many more people than we expected are interested in plugins and have struggled to find the plugin they need, to make sure the plugin they find isn’t going to break their site, or to build a new plugin.
 
-The second biggest pain point is GraphQL. About half of our interviewees expressed that GraphQL has a steep learning curve and more learning resources would make it easier to learn.
+The second most common pain point is GraphQL. About half of our interviewees said that GraphQL has a steep learning curve and more learning resources would make it easier to learn.
 
 ![Gatsby User Pain Points](pain-points.png)
 
-Other salient feedback includes the fact that people who have used Wordpress for a long time are looking for other solutions and want Gatsby to play well with different kinds of CMSs. Finally, almost every interviewee loves the Gatsby development experience because it is smooth and fast. Here are some fun quotes:
+Other salient feedback includes that people who have used WordPress for a long time are looking for other solutions and want Gatsby to play well with many kinds of CMSs. Finally, almost every interviewee loves the Gatsby development experience because it is smooth and fast. Here are some fun quotes:
 
 > You guys are pretty much nailing it. Just keep killin’ it, I guess! 
 >
@@ -87,7 +89,9 @@ The community has done some excellent work with plugins, and we wanted to celebr
 
 ## Details on why a plugin search tool matters
 
-Currently, everyone is installing plugins and many awesome users are building them. Building a plugin search tool will increase discoverability. Some specific problem scenarios that you interviewees described to me:
+Everyone is using plugins and many awesome users are building them. Building a plugin search tool will help users find the right plugins to solve their problems.
+
+Some specific problems with searching for plugins that interviewees described to me:
 
 * Your site breaks because you installed a plugin that wasn’t compatible with the current version of Gatsby.
 * You are working after hours trying to build a plugin to help some CMS play nicely with Gatsby and you’re having trouble finding a good plugin to imitate.
@@ -97,7 +101,7 @@ Currently, everyone is installing plugins and many awesome users are building th
 
 We’re working on the final prototypes for the plugin search tool and welcome contributions from the community. Here are ways you can contribute:
 
-* Follow the plugin search tool’s progress and contribute to it on [Github](https://github.com/gatsbyjs/gatsby/issues/3003).
+* Follow the plugin search tool’s progress and contribute to it on the [Github issue](https://github.com/gatsbyjs/gatsby/issues/3003).
 * [Contact me here](https://twitter.com/shannonb_ux/status/938551014956732418) if you have feedback that differs from or provides deeper insight into any of the pain points this article mentions
 * Follow us on [Twitter](https://twitter.com/gatsbyjs)
 * Contribute to issues in the [Github repo](https://github.com/gatsbyjs/gatsby/issues)