diff --git a/docs/style-guide-for-curriculum-challenges.md b/docs/style-guide-for-curriculum-challenges.md
index 133c285890..1496703335 100644
--- a/docs/style-guide-for-curriculum-challenges.md
+++ b/docs/style-guide-for-curriculum-challenges.md
@@ -141,9 +141,9 @@ Here are specific formatting guidelines for the challenge seed code:
 
 ## Why do we have all these rules?
 
-Our goal is to have a fun, clear interactive learning experience.
+Our goal is to develop a fun and clear interactive learning experience. 
 
-Designing interactive coding challenges is hard. It would be so much easier to write a lengthy explanation, or to create a video tutorial. There's a place for those on Medium and YouTube. But for our core curriculum, we're sticking with what works best for most people - a fully interactive, video game-like experience.
+Designing interactive coding challenges is difficult. It would be much easier to write a lengthy explanation or to create a video tutorial, and there's a place for those on Medium and YouTube. However, for our core curriculum, we're sticking with what works best for most people - a fully interactive, video game-like experience. 
 
 We want campers to achieve a flow state. We want them to build momentum and blast through our curriculum with as few snags as possible. We want them to go into the projects with confidence and a wide exposure to programming concepts.