Update 1yr.md

1yr.md

@@ -14,7 +14,7 @@ The past year has been great, albeit frustrating at times. I went through a lear
 With some reflection, here's what I think I learned:
 
 ### Take a moment to look around
-Like most obvious advice, this is often skipped. Torkel was the largest and primary contributor to Grafana at the time (and still is), but there was a community in place. Before jumping in, I wanted to get a sense of that. It's like walking into a new bar and trying to figure out the lay of the land. I see people get frustrated and leave projects right away because they're first remarks werent well received - despite the quality of the remark being poor. 
+Like most obvious advice, this is often skipped. Torkel was the largest and primary contributor to Grafana at the time (and still is), but there was a community in place. Before jumping in, I wanted to get a sense of that. It's like walking into a new bar and trying to figure out the lay of the land. I see people get frustrated and leave projects right away because they're first remarks were not well received - despite the quality of the remark being poor. 
 
 Read the issues. Search. Get a sense of the community. Then chime in.
 
@@ -26,7 +26,7 @@ And when I did start submitting issues, I wanted to make sure they were good one
 
 Resources: [LICEcap - Simple Animated Gif capture tool](http://www.cockos.com/licecap/), [Grafana issues](https://github.com/grafana/grafana/issues). 
 
-### There are no invitiations and nobody is going to wait for you
+### There are no invitations and nobody is going to wait for you
 Active projects like Grafana move fast. Master changes out from under my feet daily, which is quite different from the world I came from. At first, it was unsettling. “How this can be in master? It’s not done yet. It still needs features a and b. And c. And what about d... And e..."
 
 While working on Grafana, I'm often reminded that not all great ideas take weeks/months of ideation and subconscious thought. Sometimes it just takes an unreasonably tight deadline and lots of stress (like any great artist will tell you). 
@@ -35,7 +35,7 @@ When the feature/idea/interface element matters, insert yourself into the issue/
 
 
 ### Contribute in the way you can
-Especially coming to Grafana on the front-end/UX side, my original contributions were mockups and clickable prototypes. At first, I was apprehensive that I wasnt committing code. I've since realized that a big hole can be the ideation and germination phases of a project. 
+Especially coming to Grafana on the front-end/UX side, my original contributions were mockups and clickable prototypes. At first, I was apprehensive that I wasn't committing code. I've since realized that a big hole can be the ideation and germination phases of a project. 
 
 Bringing some UX best practices into Grafana, I was able to flesh out the New User Registrations process in a flow chart before a single line of code was written. It changed form a few times, and I think it saved a good chunk of actual development/refactoring in the grand scheme. 
 
@@ -48,7 +48,7 @@ Resources: Invision Clickable Prototype
 
 
 ### Make a strong case
-Doing things in public, asyncronously is daunting. You dont necessarily know your audience, you dont know who will provide feedback, you dont know their perspective, and probably, they dont know yours. There were a few times that I felt really great about a new design/feature, but nobody else thought so. In almost every case, it was becauase I didnt have enough or had not given enough context. In most of the cases that I thought I had a great feature but nobody else cared, it was 100% my fault. 
+Doing things in public, asynchronously is daunting. You don't necessarily know your audience, you don't know who will provide feedback, you don't know their perspective, and probably, they don't know yours. There were a few times that I felt really great about a new design/feature, but nobody else thought so. In almost every case, it was because I didnt have enough or had not given enough context. In most of the cases that I thought I had a great feature but nobody else cared, it was 100% my fault. 
 
 Crafting both a description of the problem and how the proposed feature offers a solution is huge. With these, things move faster. If you are misunderstanding, the feedback will be more appropriate, and you'll know why you were mistaken. And if you're bringing new perspective, you've effectively made your case and helped others quickly understand. 
 
@@ -58,14 +58,14 @@ Anticipate the nobody has the backstory - give enough context to turn lurkers in
 ### Thicken your skin
 I have bad ideas. A lot. Going through a bunch of bad ideas is usually the way I find the good ones. 
 
-Torkel has been the best open source sherpa I could have asked for. He’s solicited ideas, made sure I had ample time to contribute, and turned my clickable prototypes into real code, but there were times that he'd abruptly close an issue saying, in effect, notabugwontfix. Or when a suggestion is way out of whack with feasibility, Torkel wasnt shy about letting me know. He was great, but it was disconcerting because I felt like I wasted his time. 
+Torkel has been the best open source sherpa I could have asked for. He’s solicited ideas, made sure I had ample time to contribute, and turned my clickable prototypes into real code, but there were times that he'd abruptly close an issue saying, in effect, notabugwontfix. Or when a suggestion is way out of whack with feasibility, Torkel wasn't shy about letting me know. He was great, but it was disconcerting because I felt like I wasted his time. 
 
 In some cases, I did waste his time, and those are the opportunities to learn. If an ideas is not resonating, there's a reason. Do some research, better understand the issue and try again. 
 
 
 ### Keep at it
 
-Rome wasnt built in a single commit. I'm extremely proud of what Grafana 3.0 has become, and I do believe my many contributions over the past year have helped make better software for everyone. 
+Rome wasn't built in a single commit. I'm extremely proud of what Grafana 3.0 has become, and I do believe my many contributions over the past year have helped make better software for everyone. 
 
 You can do the same. Pick a project you enjoy (perhaps Grafana?) and start helping. Then in a year, look back, and let me know how it went. Good luck.