Changes requested resolved

Rails-Girls-Summer-Of-Code-2017-Blog-Post-2.md

@@ -1,6 +1,6 @@
 # Team 276linesofCode - Rails Girls Summer of Code 2017
 
-About two and a half months back, none of us had an idea of what this journey would be like. RGSoC had been the first Summer of Code or any other program as such that we were a part of, and our eagerness to grasp the most from the program had us going all throughout. Not to mention, we have gained so much more than we had even anticipated.
+About two and a half months back, none of us had an idea of what this journey would be like. RGSoC had been the first Summer of Code or any other code mentorship program that we were a part of, and our eagerness to grasp the most from the program had us going all throughout. Not to mention, we have gained so much more than we had even anticipated.
 
 We both believe that Tessel was the best project that we could have worked on since it welcomes new contributors in a positive manner that motivates them to give back to the community as much as they can.
 
@@ -12,11 +12,11 @@ We've got our hands dirty with things like Documentation, Tutorials, Code, Hardw
 
 Our Hardware modules were shipped by the Tessel team from the US and we spent some time exploring them. This was the most exciting part - Making circuits, seeing the LEDs shimmer, watching the Accelerometer come back to life, and many many more.
 
-After exploring the different repositories in Tessel, we started exploring issues which were Contribution starters. A lot of them were listed in the Tessel blog called "[This Week in Tessel](https://tessel.io/blog/157835574022/this-week-in-tessel-fun-with-open-source)" and we started completing them one at a time.
+After exploring the different repositories in Tessel, we started exploring issues which were Contribution starters which are beginner friendly issues that help in getting an idea of what Tessel is all about. A lot of them were listed in the Tessel blog called "[This Week in Tessel](https://tessel.io/blog/157835574022/this-week-in-tessel-fun-with-open-source)" and we started completing them one at a time.
 
 We made important tutorial modules for Tessel for their documentation page. This included Fritzing diagrams of the circuits, describing the functionality in layman terms, and writing code which would be easily understood, with the help of the comments. Along with this we started working on "[reach](https://github.com/tessel/reach-wg)" during the last few weeks of the program.
 
-Apart from all the technical work, we learnt about Product Design and how exactly does a product make it's way to the Open Source domain. We made a draft of something called a Product Requirement Document (PRD) for our proposal of HAP (Humanoid Arm Project) that we had made during our application process.
+Apart from all the technical work, we learned about Product Design and how exactly does a product make its way to the Open Source domain. We made a draft of something called a Product Requirement Document (PRD) for our proposal of HAP (Humanoid Arm Project) that we had made during our application process.
 
 ## Challenges
 
@@ -32,11 +32,11 @@ Before RGSoC had started, our mentor, Kelsey had sent us a Plan of Work to follo
 
 ## A shoutout to the amazing Tessel Community!!
 
-Our blog couldn't be complete had we not thanked the awesome Tessel Community that made our descent into Open Source, a fun and a smooth ride. Every call with Kelsey would begin with her asking us whether we have been achieving whatever we planned for. She even asked if the tasks for the week were a lot or were they too less. But she always ensured that we had the right amount of work on our plate for that week.
+Our blog couldn't be complete had we not thanked the awesome Tessel Community that made our descent into Open Source, a fun and a smooth ride. Every call with Kelsey would begin with her asking us whether we have been achieving whatever we planned for. She even asked if the tasks for the week were a lot or were they too little. But she always ensured that we had the right amount of work on our plate for that week.
 
 Our weekly calls with Kelsey, our mentor, were the times where we had learnt the most. The timely response of the community members on any of our doubts were commendable. Any PR review would come in a day or a two and the reviews gave us a different perspective on the issues. Nick and Kelsey, both Tessel Steering Committee members would leave comments asking questions about our code, which would force us to research more on the issue.
 
-On our third meeting with Kelsey, she had said that "It is better to over-communicate rather than Under-communicate" and thus, we would ( shamelessly 🙈 ) ping them on slack or on the issues whenever we were stuck and a descriptive solution to our questions would follow. Many a times, Kelsey would explain us our doubts on our call. Despite whatever mistakes we would make, the committee members were always positive and ensured that we were able to rectify our errors and learn from them. Many a times, they've tagged us in issues that they thought we should be aware of and sent us links and resources to escalate our learning.
+On our third meeting with Kelsey, she had said that "It is better to over-communicate rather than Under-communicate" and thus, we would ( shamelessly 🙈 ) ping them on slack or on the issues whenever we were stuck and a descriptive solution to our questions would follow. Many a times, Kelsey would explain us our doubts on our call. Despite whatever mistakes we would make, the committee members were always positive and ensured that we were able to rectify our errors and learn from them. Many times, they've tagged us in issues that they thought we should be aware of and sent us links and resources to escalate our learning.
 
 Tessel has provided us amazing Mentorship, one that is really hard to find. We are so glad that we began our journey with Open Source with such a welcoming community, so much so that we are more than willing to work for Tessel even after RGSoC is over. Tessel, We love you!
 
@@ -48,6 +48,6 @@ It was a great experience for both of us because we were able to pass on our kno
 
 ## What's next?
 
-RGSoC provided us with a whole lot of things that we not even imagined of gaining in this interval of three months. As it was a wonderful journey for both of us, we have thought of recommending this program to more and more people by conducting a few related meetups at our University under our Rails Girls Summer of Code, Delhi Chapter. Apart from this, we had discussed way back with our mentor during the application process that we would love to contribute to Tessel even after RGSoC ends. The months might be over, but the memories are here to stay!
+RGSoC provided us with a whole lot of things that we didn't even imagine gaining in this interval of three months. As it was a wonderful journey for both of us, we have thought of recommending this program to more and more people by conducting a few related meetups at our University under our Rails Girls Summer of Code, Delhi Chapter. Apart from this, we had discussed way back with our mentor during the application process that we would love to contribute to Tessel even after RGSoC ends. The months might be over, but the memories are here to stay!
 
 Who would know that two confused, scared and shy humans who had absolutely no idea how they would survive the tech world could successfully complete RGSoC, loaded with experience and confidence?