Merge pull request #142 from harrigan/fix-typos

Fix typos
This commit is contained in:
Ben Bader 2015-01-07 10:28:58 -08:00
commit f7bd09f1be
4 changed files with 5 additions and 5 deletions

View file

@ -2751,7 +2751,7 @@ I wonder?</p>
(group-lines))] (group-lines))]
{:ns ns {:ns ns
:groups groups})) :groups groups}))
</pre></td></tr><tr><td class="docs"><h2>Ouput Generation</h2> </pre></td></tr><tr><td class="docs"><h2>Output Generation</h2>
</td><td class="codes"><pre class="brush: clojure"></pre></td></tr><tr><td class="docs"><p>Generates an uberdoc html file from 3 pieces of information:</p> </td><td class="codes"><pre class="brush: clojure"></pre></td></tr><tr><td class="docs"><p>Generates an uberdoc html file from 3 pieces of information:</p>
<ol> <ol>
@ -3199,7 +3199,7 @@ saying that all this is WIP and will prabably change in the future.</p>
&quot;SyntaxHighlighter.defaults['gutter'] = false; &quot;SyntaxHighlighter.defaults['gutter'] = false;
SyntaxHighlighter.all()&quot;]]])) SyntaxHighlighter.all()&quot;]]]))
</pre></td></tr><tr><td class="docs"><p>Syntax highlighting is done a bit differently than docco. Instead of embedding </pre></td></tr><tr><td class="docs"><p>Syntax highlighting is done a bit differently than docco. Instead of embedding
the higlighting metadata on the parse / html gen phase, we use <a href="http://alexgorbatchev.com/SyntaxHighlighter/">SyntaxHighlighter</a> the highlighting metadata on the parse / html gen phase, we use <a href="http://alexgorbatchev.com/SyntaxHighlighter/">SyntaxHighlighter</a>
to do it in javascript.</p> to do it in javascript.</p>
</td><td class="codes"><pre class="brush: clojure"></pre></td></tr><tr><td class="docs"><p>This generates a stand alone html file (think <code>lein uberjar</code>). </td><td class="codes"><pre class="brush: clojure"></pre></td></tr><tr><td class="docs"><p>This generates a stand alone html file (think <code>lein uberjar</code>).
It's probably the only var consumers will use.</p> It's probably the only var consumers will use.</p>

View file

@ -386,7 +386,7 @@
;; Syntax highlighting is done a bit differently than docco. Instead of embedding ;; Syntax highlighting is done a bit differently than docco. Instead of embedding
;; the higlighting metadata on the parse / html gen phase, we use [SyntaxHighlighter](http://alexgorbatchev.com/SyntaxHighlighter/) ;; the highlighting metadata on the parse / html gen phase, we use [SyntaxHighlighter](http://alexgorbatchev.com/SyntaxHighlighter/)
;; to do it in javascript. ;; to do it in javascript.
(defn uberdoc-html (defn uberdoc-html

View file

@ -105,7 +105,7 @@
"GENERATED ALWAYS AS IDENTITY") "GENERATED ALWAYS AS IDENTITY")
(defn strict-eval-op-fn (defn strict-eval-op-fn
"`strict-eval-op-fn` is used to define functions of the above pattern for fuctions such as `+`, `*`, etc. Cljs special forms defined this way are applyable, such as `(apply + [1 2 3])`. "`strict-eval-op-fn` is used to define functions of the above pattern for functions such as `+`, `*`, etc. Cljs special forms defined this way are applyable, such as `(apply + [1 2 3])`.
Resulting expressions are wrapped in an anonymous function and, down the line, `call`ed, like so: Resulting expressions are wrapped in an anonymous function and, down the line, `call`ed, like so:

View file

@ -27,7 +27,7 @@
Provides the following variables to the assertion context: Provides the following variables to the assertion context:
* `number-of-generated-pages` - result of running the `doc-generator` * `number-of-generated-pages` - result of running the `doc-generator`
function (which should ultimately call one of the marginalias' own function (which should ultimately call one of the Marginalia's own
functions. functions.
* `project-name` - the name of the project * `project-name` - the name of the project