Editing first chapter intro

diff --git a/chapter01.md b/chapter01.md
index c3c34bbd6b6b570a1d562d0eddfa96676bf4c01f..3173d402df4f73c58196737165761f50a981f728 100644 (file)
--- a/chapter01.md
+++ b/chapter01.md
@@ -1,13 +1,13 @@
 # The Journey of the mediocre programmer
 ## How we got here
 
-You have your own unique story of how you got here as a programmer. Whether you found out about programming as a curious child who wanted to see what the computer could do, or as an adult who heard that there were these things called computers that you could program, you had a journey to get to this point. And you learned a certain amount to get here. You spent your free time learning how to code or you were fortunate to be able to work on programming as part of your job. You went to school to learn more about programming or you took training classes. You bought books or read articles online to learn more about programming. Whatever the path you took you started the journey as a programmer.
+You have your own unique story of how you got here as a programmer. You might have found out about programming as a curious child who wanted to see what the computer could do. Or you could have arrived as an adult who heard about these things called computers that you could program. Whatever the case, you had a journey to get to this point, and you learned a certain amount to get here. You spent your free time learning how to code, or you were fortunate to be able to work on programming as part of your job. You went to school to learn more about programming or you took training classes. You bought books or read articles online to learn more about programming. Whatever the path you took you started the journey as a programmer.
 
 And now you feel stuck.
 
 You look around and wonder if you'll ever know everything that you should know. You read an article on a site and your interest is piqued. A friend online mentions this neat thing that they've found and expects that you will learn more about it. Your colleague found something that might solve an issue you're having at work on a project and now you have one more thing to learn. 
 
-Perhaps you're seeing new things show up in job postings with a minimum of 3+ years of required experience and you're wondering how anyone would have that level of experience yet. Or you chose to ignore that thing for a while and now it's become a driving factor in your domain of work. It's as if someone flipped a bit somewhere and now you're suddenly unworthy of being called a programmer unless you know this thing. 
+New topics and technologies seem to emerge almost weekly. These "things" creep into programming discussions and our work. Perhaps you're seeing these new things show up in job postings with a minimum of 3+ years of required experience and you're wondering how anyone could have that level of experience. Or you chose to ignore these things for a while and now they've become a driving factor in your work. It's as if someone flipped a bit and now you're unworthy of being called a programmer unless you were an early adopter of these things.
 
 Each of these experiences causes you to feel as though you are incomplete without learning these new things. They show us that no matter our current experience there are still gaps in our knowledge that must be filled. As you look to the horizon you can see the gaps that creep up in between where you are and where you think you should be.