Updated «what Git can do for you with coder & creative options

git-primer.tex

@@ -159,6 +159,7 @@
 	{\fontsize{12}{0}\selectfont for Coders and Creatives}\\
 	{\fontsize{10}{0}\selectfont Typeset in \LaTeX{}}\\
 	{\fontsize{10}{0}\selectfont v. 0.2.0}
+	\\ \color{red5}Remember to take this out of ``draft'' mode\\before publishing
 }
 
 
@@ -206,9 +207,9 @@ Git also allows you to experiment easily without worrying about messing up your
 
 Git is great if you are a software developer, because as you work you make a \textit{lot} of changes to your code. It's also great if you are a writer, because you can experiment as much as you want and not have to worry about losing or overwriting something. You can just revert to an earlier version, or \textit{branch} in order to experiment. But more about that later.
 
-Git works best with text-based files\index{files, text-based}—basically, anything that has a \texttt{.txt}, \texttt{.html}, \texttt{.css}, \texttt{.php}, etc. extension will work. There's no reason that you can't add binaries, such as images, pdfs, Microsoft Word files, or LibreOffice files. (I'm writing this zine in \LaTeX{}, and do include a few images in most issues, for example.) The issue is that because they are binaries, Git won't be able to tell you the difference between versions. (I would add, though, that if you are writing, you really should separate out the content and the styling from the beginning, so that you can focus on the story you want to tell. Plain text files are your friends.)
+If you are just getting started in your career in programming, Git will have a lot of benefits for you. It can streamline your coding process, help you avoid losing work (and thus hours), make it easier to collaborate with others, and also give you a place to show off your work when you are looking for a job.
 
-\todo[inline]{Add stuff about "If you are a coder" and "If you are a creative".}
+If you are a writer rather than a coder, Git still has a lot to offer you as well. Revisions are a stock in trade for writers, as are experiments, and Git makes those things easily managed. Then too, because Git requires you to use text files (more about that later), you can focus on your writing without having to use any sort of ``distraction-free'' word processing program. 
 
 \section{Git Concepts}
 
@@ -224,6 +225,8 @@ You can work with a local repository only, or you can decide to work with one or
 
 \paragraph{Concept Four: Repositories are multi-dimensional.} If you make a series of commits to a repository, it will be linear in nature. This is perfectly ordinary. But you may get to a point where you want to experiment with something and you're not sure whether you'll like the new version or the old version better. Rather than commit that new version, which overrides the original version, you can \textit{branch} and have both versions existing at the same time. A branch is basically a copy of a repository at this point in time (i.e., from the last commit). You can then switch between branches and test things out. You can treat it like a sandbox, essentially.
 
+\paragraph{Concept Five: Git works best with text-based files\index{files, text-based}} Basically, this means anything that has a \texttt{.txt}, \texttt{.html}, \texttt{.css}, \texttt{.php}, etc. extension will work. There's no reason that you can't add binaries, such as images, pdfs, Microsoft Word files, or LibreOffice files. (This document does include at least one image file, for example.) The issue is that because they are binaries, Git won't be able to tell you the difference between versions.
+
 \section{Git Clients}
 
 Git is a command line based technology. Yes, there are GUIs (Graphical User Interfaces) out there for Git, and if you are on Windows or macOS, you may find them useful. You can see a fairly comprehensive list at \kref{https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces}{https://git-scm.com/book/en\\/v2/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces}.