updates

Author: ndanielsen

materials/1-Intro-Command-Line.md

@@ -141,12 +141,12 @@ The relative path to the another HackforLa project folder on my computer is:
 * Remove *one* of the previously created files.
 * Go up one directory and remove the `test` directory with the empty files in it.  **NOTE**:  Be careful and make sure you are removing the correct files!
 * Create an empty file called `test.txt`.  
-* Change the name to `civic_hacking_is_cool.txt`.
+* Change the name to `opensource_is_cool.txt`.
 * Create an empty file called `my_secrets.txt`.
 * Create a new directory called `my_diary`.  
 * Move the two previously created files into this directory.
-* Create a new directory called `my_blog`.  Copy the file `civic_hacking_is_cool.txt` from `my_diary` to `my_blog`.
-* Examine the files in `my_blog` to confirm that `civic_hacking_is_cool.txt` is there.
+* Create a new directory called `my_blog`.  Copy the file `opensource_is_cool.txt` from `my_diary` to `my_blog`.
+* Examine the files in `my_blog` to confirm that `opensource_is_cool.txt` is there.
 * Zip the folders `my_diary` and `my_blog` into a new file called `writings.zip`.
 * Delete the folders `my_diary` and `my_blog`.
 * Unzip `writings.zip` to get your folders back.

materials/3-Github.md

@@ -9,7 +9,7 @@ The lesson materials are hosted on GitHub at https://github.com/ndanielsen/intro
 
 ## Typical Workflows on Github
 
-The typical workflow for a contributor to a new `Hack for La` Project is as follows:
+The typical workflow for a contributor to a `Open Source` Project is as follows:
 
 1. **Discover** a bug or a feature.
 2. **Discuss** with the project leads by [adding an issue](https://github.com/ndanielsen/intro-cli-git-github/issues).
@@ -22,7 +22,7 @@ The typical workflow for a contributor to a new `Hack for La` Project is as foll
 
 **Note**: Create a pull request as soon as possible, even before you've started coding. This will allow the Project Leads to give you advice about where to add your code or utilities and discuss other style choices and implementation details as you go. Don't wait!
 
-Many Hack-for-La projects believe that *contribution is collaboration* and therefore emphasize *communication* throughout the entire process. Project Leads rely heavily on GitHub's social coding tools to allow them to do this.
+Many `Open Source` projects believe that *contribution is collaboration* and therefore emphasize *communication* throughout the entire process. Project Leads (ie maintainers) rely heavily on GitHub's social coding tools to allow them to do this.
 
 ### Forking the Repository