Minor Fixes

diff --git a/Makefile b/Makefile
index 434ac51704fee38bf312b3af73942aeb65cfc5da..60304fb9c5eea6d3eb8a00cf5013288dcfed842e 100644 (file)
--- a/Makefile
+++ b/Makefile
@@ -4,7 +4,7 @@ TITLE = title.txt
 METADATA = metadata.xml
 CHAPTERS = intro.md chapter01.md chapter02.md chapter03.md chapter04.md chapter05.md chapter06.md chapter07.md epilogue.md gratitude.md appendixa.md
 TOC = --toc --toc-depth=2
-COVER_IMAGE = images/cover.jpg
+COVER_IMAGE = images/cover_ebook_1600x2400.png
 LATEX_CLASS = book
 
 all: book
@@ -30,6 +30,6 @@ $(BUILD)/html/$(BOOKNAME).html: $(CHAPTERS)
 
 $(BUILD)/pdf/$(BOOKNAME).pdf: $(TITLE) $(CHAPTERS)
        mkdir -p $(BUILD)/pdf
-       pandoc $(TOC) --chapters --number-offset=0 --latex-engine=xelatex -V documentclass=$(LATEX_CLASS) -o $@ $^
+       pandoc $(TOC) --chapters --number-offset=0 --latex-engine=pdflatex -V documentclass=$(LATEX_CLASS) -o $@ $^
 
 .PHONY: all book clean epub html pdf

diff --git a/chapter05.md b/chapter05.md
index 569dd1cb2635800d8a20e7af56c73b24531f0842..d1b8ce5a591b784dc8fde299535b2f022ffca11c 100644 (file)
--- a/chapter05.md
+++ b/chapter05.md
@@ -4,7 +4,7 @@
 
 Programmers are always trying to find new ways to be productive. Tweaks to text editors, compilation tweaks, scripts and automation; the list goes on for how programmers want to maximize their productive time coding. We also spend time tweaking the rest of our lives with the belief that we should always be doing something related to coding. Any moment we're not coding is a moment where our projects get behind. And getting behind with our coding can lead to other problems: missed deadlines, other companies getting their program to market before us, or other instances where we miss an opportunity. We're constantly worrying that we're not doing enough to succeed.
 
-We've heard the stories of developers waking up at their computers to the strange sound of beeping because they fell asleep at the keyboard and the keyboard auto repeat can't handle any more input with their face resting on the keys. Isn't that how developers should work?
+We've heard stories of developers waking up at their computers to the strange sound of beeping because they fell asleep at the keyboard and the keyboard's auto repeat can't handle any more input with their face resting on the keys. Isn't that how developers should work?
 
 There's a tendency to think that because we work with machines that are tireless and ready for more work that we need to behave in the same way; we need to constantly utilize these resources. We try become like the machine; tireless and always ready for more work. 
 

diff --git a/chapter06.md b/chapter06.md
index 44fba5fc9d342a34b220b22e79a336e5340cb499..87990fb191373aaffeeafd4ef55aa25e5b45945d 100644 (file)
--- a/chapter06.md
+++ b/chapter06.md
@@ -24,7 +24,7 @@ Each day you have an opportunity to learn more about the realm of computers and
 
 There are many opportunities to learn, whether it be via books, tutorials, videos, or computer-based training. There's also a myriad of different topics to learn. How do you decide which one is most important to learn? How do you manage what you're learning? How do you keep from getting overwhelmed with the options available?
 
-This gets back to focusing on one thing at a time and listening to how you learn best. This feedback will help you decide what to learn next. One approach is to think about the things that you're most passionate about right now; what excites you at this moment. If there's something that you're eager to learn then start there. If you have multiple things that are exciting or interesting to you then write them down on a list and see if you are more drawn to one of the topics than the others. If you're still having trouble deciding from this list then pick one at random (roll some dice or create a random-number generator to select one -- that could be a project).
+This gets back to focusing on one thing at a time and listening to how you learn best. This feedback will help you decide what to learn next. One approach is to think about the things that you're most passionate about right now; what excites you at this moment. If there's something that you're eager to learn then start there. If you have multiple things that are exciting or interesting to you then write them down on a list and see if you are more drawn to one of the topics than the others. If you're still having trouble deciding from this list then pick one at random (roll some dice or create a random-number generator to select one --- that could be a project).
 
 If you have trouble thinking of something to learn and are struggling to come up with one item that is exciting to you then give yourself permission to browse and see what is out there. Look around and see what people are talking about. Head to a programmer meeting to see what they're talking about. Or, if you're really stuck, browse some job listings to see what employers are looking for and see if that sparks some interest.