Formatting tweaks.

coleslaw-org · Dec 8, 2014 · deb2e55 · deb2e55 · sternenseemann · Dec 8, 2014
1 parent 0fdac81
commit deb2e55
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -8,7 +8,8 @@
 > behind the enormous bushy eyebrows and that we called him Coleslaw. - anon
 
 Coleslaw is Flexible Lisp Blogware similar to [Frog](https://github.com/greghendershott/frog), [Jekyll](http://jekyllrb.com/), or [Hakyll](http://jaspervdj.be/hakyll/).
-Have questions? Come talk to us on **IRC in #coleslaw on Freenode**!
+
+Have questions? Come talk to us on IRC in **#coleslaw** on Freenode!
 
 ## Features
 

diff --git a/docs/hacking.md b/docs/hacking.md
@@ -272,7 +272,7 @@ This is a initial set of commands which will be used to implement the first cole
 Imagine a executable `coleslaw`, the commands would be invoked like this: `coleslaw <commandname> <args>`
 
 * `build` generates the site. Takes:
-	* `--repo-dir`: first defaults to `~/.coleslawrc`'s `repo-dir` then to `./.coleslawrc`'s `repo-dir` and otherwise fails
+	* `--repo-dir`: first defaults to `~/.coleslawrc`'s `repo-dir` then to `.` and otherwise fails
 * `clean` removes the files from `output-dir` and `staging-dir`. Takes:
 	* `--repo-dir`: See above
 * `rebuild` is a shortcut for `clean` and then `build`. Takes:
@@ -288,7 +288,9 @@ Imagine a executable `coleslaw`, the commands would be invoked like this: `coles
 
 Ideas for later:
 
-* handle deployment with commands but because we've got many methods there would have to be an intelligent way of handling that.
+* Deployment. It would be nice to have but user needs vary greatly
+  and there are multiple deployment methods to support (heroku, s3,
+  gh-pages, git, etc). This will require some careful thought.
 
 ### Plugin Constraints