Merge pull request #31 from snastase/text-fix

Minor text adjustments and standardization

Author: yarikoptic

_episodes/00-overview.md

@@ -7,8 +7,8 @@ questions:
 - "Who is this module for?"
 - "How should I study it?"
 objectives:
-- To think about reproducibility as an inherent part of research activities
-- To use lesson materials as soon as possible
+- "Think about reproducibility as an inherent part of research activities"
+- "Use lesson materials as soon as possible"
 keypoints:
 - "Efficient practices are the (more) reproducible ones"
 
@@ -19,8 +19,8 @@ keypoints:
 The term "reproducibility" conjures a mental image of dedicated systems
 conducting automated and repeatable computations.  However, **you** can
 embrace reproducibility as a principle to apply to your day-to-day
-research activities.  Neuroimaging is a heavily data- and software- driven
-field of science.  As a result, by learning more tricks and techniques
+research activities.  Neuroimaging is a heavily data- and software-driven
+field of science. As a result, by learning more tricks and techniques
 for the tools that you already use daily, you will discover ways to
 not only improve your efficiency but also to increase the reproducibility of
 your research.
@@ -29,7 +29,7 @@ To some degree, reproducibility requires knowledge of **what**,
 **when**, and **how** any particular analysis was carried out.
 Therefore the lessons in this module will focus on helping
 answer those questions.  Before addressing these specific questions,
-referenced external materials (tutorials, lessons, etc) will provide a
+referenced external materials (tutorials, lessons, etc.) will provide a
 more generic and thorough presentation of the topics.
 
 
@@ -40,7 +40,6 @@ software for data analysis, writing custom code or editing documents.
 
 > ## Prerequisites
 >
->
 > Depending on your level of competence in any particular topic, you
 > might like to go through additional materials that will be
 > referenced in each particular lesson.  Even if you feel that you are
@@ -51,13 +50,13 @@ software for data analysis, writing custom code or editing documents.
 
 ### How much time should this take?
 
-That primarily depends on your familiarity and experience with working
+That primarily depends on your experience and familiarity with working
 in command line/shell, using version control systems, managing
-software environments, having experience providing constructive
-feedback about defects you found in software you use, etc. All those
+software environments, and providing constructive
+feedback about defects you find in software you use. All those
 topics seem independent but are also very much related, so it is likely
 that you might have some familiarity with all of them, or that you know
-just one of them well.  If you have no experience with any topic,
+just one of them well. If you have no experience with any topic,
 this may take you a long time: for instance, 5 to 7 full days. If you
 are experienced, some of the information may be redundant and it may take
 you only a few hours to go through this material in detail. In each
@@ -68,7 +67,7 @@ the lesson, assuming you have a basic understanding of the topic.
 
 It is important to **apply** the knowledge gained from the lessons to
 your day-to-day activities as soon as possible! Start using shell
-and/or do it more efficiently by using shortcuts, scripting, making
+and/or using it more efficiently by using shortcuts, scripting, making
 those scripts robust, etc. Use version control systems for anything
 you change (code, data, documents) and increase "traceable" collaboration
 exchange, even if it’s just between you on computer 1 and you on
@@ -78,17 +77,17 @@ run into and don’t just leave them unresolved.
 
 An efficient approach to learning the materials is to first skim
 through all the materials, noting the key concepts and applying them
-right away. Then, after gaining experience and stumbling upon some
+right away. Then, after gaining experience and stumbling on some
 problems, it will be useful to review the relevant topic in greater
-detail while concentrating on the relevant aspects.
+detail while concentrating on the most pertinent aspects.
 
 **The least efficient approach would be to spend a week "learning
 it" only to forget all of it by not using any of the learned tools
 or recommended practices.**
 
 ### What are the lessons in this module?
 
-This module guides through three somewhat independent topics, which
+This module will guide you through three somewhat independent topics, which
 are at the heart of establishing and efficiently using common generic
 resources: command line shell, version control systems (for code and
 data), distribution package managers, and a few additional aspects such