More FAQ polishing.

diff --git a/FAQ.asc b/FAQ.asc
index bbcd2ff4ac425f8be8572f32956e49cb30f96613..1cb03525d08dda239ff1fe8e995d2c70a872aadc 100644 (file)
--- a/FAQ.asc
+++ b/FAQ.asc
@@ -66,7 +66,6 @@ respect to the reasons SRC exists.
 
 [[beginners-vcs]]
 == Is SRC a good system on which to learn about version control? ==
-=======
 
 *YES*! SRC is explicitly designed to have the bare-bones features and
 commands of a modern version control system. Keep in mind that SRC’s
@@ -146,7 +145,7 @@ original design. Resurrect RCS?  Wrap it in a decent UI?  _Really?_
 There's a significant amount of ha-ha-only-serious here.  Laugh, but
 treat SRC as a lesson in several things.  Unix minimalism.  The virtue
 of re-use, even of technology as old as RCS.  The effectiveness of a
-carefully designed UI.  The value of a conservative design with no
+carefully crafted UI.  The value of a conservative design with no
 surprises and no undue cleverness.
 
 What *will* be funny is when we implement the back end to talk to