document the single-repo case and why that might not scale well.

Author: justinabrahms

content/05-appendix.md

@@ -1,10 +1,19 @@
 # Appendix
-## Managing work vs personal personas
+## Managing work vs personal emails in git
 In the world of open source, folks may have an online identity that pre-dates
 their employment with our current organization. Simultaneously, the organization
 may want contributions done on their behalf to happen with corporate emails.
 
-To manage this, we can use a feature of git which allows different
+One way that folks can solve this is by encoding their commit email on a
+per-repository basis, like:
+
+```
+git config user.email "[email protected]"
+```
+
+
+If you work with several repositories, this will become difficult to manage and
+easy to forget. Instead, we can use a feature of git which allows different
 configurations based on our directory structures.
 
 Our `~/.gitconfig` file might look like this:
@@ -18,7 +27,7 @@ Our `~/.gitconfig` file might look like this:
     path = ~/my-company/.gitconfig
 ```
 
-This sets our default persona (which, in this case, is for a personal
+This sets our default email (which, in this case, is for a personal
 account). If we have repositories in the `~/my-company` directory, we'll load an
 additional git config file which is located at `~/my-company/.gitconfig`. That
 file might look like: