# HG changeset patch # User Steve Losh # Date 1328310409 18000 # Node ID 540256c254e31995524136b09fd1b5ccb5c087aa # Parent bad650893001709d800cef83f21ab5c604b7bbfa d: Update site. diff -r bad650893001 -r 540256c254e3 d/faqs/index.html --- a/d/faqs/index.html Fri Feb 03 18:05:34 2012 -0500 +++ b/d/faqs/index.html Fri Feb 03 18:06:49 2012 -0500 @@ -29,11 +29,11 @@

Should I use d for my project?

-

If you want lots of control over the resulting documentation: no.

-

If you want to hook in API docs and such: no.

-

If you want to write in something other than Markdown: no.

+

If you want lots of control over the resulting documentation: no.

+

If you want to hook in API docs and such: no.

+

If you want to write in something other than Markdown: no.

If you have a large project and need more than one level of organization for -your documentation: no.

+your documentation: no.

If you have a small project and want to quickly write some docs that don't look like ass: yes!

What if I Outgrow d?