more errata

ERRATA.md

@@ -0,0 +1,26 @@
+https://github.com/flyingmachine/brave-clojure-web/pull/125/commits
+"carat" should be "caret"
+
+https://github.com/flyingmachine/brave-clojure-web/pull/124/files
+
+
+https://github.com/flyingmachine/brave-clojure-web/pull/94/files
+remove "@" in front of butter-promise
+
+https://github.com/flyingmachine/brave-clojure-web/pull/120/files
+feelings should be feelings-about
+
+https://github.com/flyingmachine/brave-clojure-web/pull/119/files
+feelings should be feelings-about
+
+https://github.com/flyingmachine/brave-clojure-web/pull/71/files
+parthensis
+
+https://github.com/flyingmachine/brave-clojure-web/pull/101/files
+small typo
+
+https://github.com/flyingmachine/brave-clojure-web/pull/88/files
+typos
+
+https://github.com/flyingmachine/brave-clojure-web/pull/81
+core fucntions fix

README.md

@@ -2,9 +2,12 @@
 
 Pull requests
 [Clojure for the Brave and True](http://www.braveclojure.com) are very
-much welcome! I'll use them as errata reports.
+much welcome! I'll use them as errata reports. Please keep in mind
+that the HTML was generated by Adobe InDesign or some such, so it's
+pretty crappy - and that's OK. I'm not concerned with that; I *am*
+concerned with inaccuracies in the content.
 
-All the textual content's under `/content`.
+All the textual content's under `/content/cftbat`.
 
 After installing ruby and bundler, build with
 

content/cftbat/appendix-a.html

@@ -8,8 +8,7 @@
 
       <div class="chapter-number">Appendix A</div>
       <h1>Building and Developing with Leiningen</h1>
-      <p class="x1st-Para"><span>Writing software in any language involves generating </span><em>artifacts</em><span>, which are executable files or library packages that are meant to be deployed or shared. It also involves managing dependent artifacts, also called </span><em>dependencies</em><span>, by ensuring that they’re loaded into the project you’re </span></p>
-      <p class="BodyFirst">building. The most popular tool among Clojurists for managing artifacts is Leiningen, and this appendix will show you how to use it. You’ll also learn how to use Leiningen to totally enhancify your development experience with <em>plug-ins</em>.</p>
+      <p class="x1st-Para"><span>Writing software in any language involves generating </span><em>artifacts</em><span>, which are executable files or library packages that are meant to be deployed or shared. It also involves managing dependent artifacts, also called </span><em>dependencies</em><span>, by ensuring that they’re loaded into the project you’re </span> building. The most popular tool among Clojurists for managing artifacts is Leiningen, and this appendix will show you how to use it. You’ll also learn how to use Leiningen to totally enhancify your development experience with <em>plug-ins</em>.</p>
       <h2>The Artifact Ecosystem</h2>
       <p class="BodyFirst">Because Clojure is hosted on the Java Virtual Machine <span>(</span> JVM), Clojure artifacts are distributed as JAR files (covered in Chapter 12). Java land <span>already has an entire artifact ecosystem for handling JAR files, and </span><span>Clojure uses it. </span><em>Artifact ecosystem</em><span> isn’t an official programming term; I use </span>it to refer to the suite of tools, resources, and conventions used to identify and distribute artifacts. Java’s ecosystem grew up around the Maven build tool, and because Clojure uses this ecosystem, you’ll often see references to Maven. Maven is a huge tool that can perform all kinds of wacky project <span>management</span> tasks. Thankfully, you don’t need to get your PhD in Mavenology to be an effective Clojurist. The only feature you need to know is that Maven specifies a pattern for identifying artifacts that Clojure projects adhere to, and it also specifies how to host these artifacts in Maven <em>repositories</em>, which are just servers that store artifacts for distribution.</p>
       <h3>Identification</h3>

content/cftbat/core-functions-in-depth.html

@@ -281,7 +281,7 @@ <h3>take, drop, take-while, and drop-while</h3>
 <span class="tok-c1">; =&gt; (4 5 6 7 8 9 10)</span>
 </code></pre></div></div>
 
-      <p class="Body"><span>Their cousins </span><code>take-while</code><span> and </span><code>drop-while</code><span> are a bit more interesting. </span>Each takes a <em>predicate function</em> (a function whose return value is evaluated for truth or falsity) to determine when it should stop taking or dropping. Suppose, for example, that you had a vector representing entries in your<em> </em>“food” journal. Each entry has the year, month, day, and what you ate. To preserve space, we’ll only include a few entries:</p>
+      <p class="Body"><span>Their cousins </span><code>take-while</code><span> and </span><code>drop-while</code><span> are a bit more interesting. </span>Each takes a <em>predicate function</em> (a function whose return value is evaluated for truth or falsity) to determine when it should stop taking or dropping. Suppose, for example, that you had a vector representing entries in your<em> </em>“food” journal. Each entry has the month and day, along with what you ate. To preserve space, we’ll only include a few entries:</p>
       <div class="listingblock"><div class="content"><pre class="pygments highlight"><code data-lang="clojure" class="block"><span class="tok-p">(</span><span class="tok-k">def </span><span class="tok-nv">food-journal</span>
   <span class="tok-p">[{</span><span class="tok-ss">:month</span> <span class="tok-mi">1</span> <span class="tok-ss">:day</span> <span class="tok-mi">1</span> <span class="tok-ss">:human</span> <span class="tok-mf">5.3</span> <span class="tok-ss">:critter</span> <span class="tok-mf">2.3</span><span class="tok-p">}</span>
    <span class="tok-p">{</span><span class="tok-ss">:month</span> <span class="tok-mi">1</span> <span class="tok-ss">:day</span> <span class="tok-mi">2</span> <span class="tok-ss">:human</span> <span class="tok-mf">5.1</span> <span class="tok-ss">:critter</span> <span class="tok-mf">2.0</span><span class="tok-p">}</span>