added FAQ about 'proc'

tools/niminst/buildsh.tmpl

@@ -95,7 +95,7 @@ case $ucpu in
       LINK_FLAGS="$LINK_FLAGS -m64"
     fi
     mycpu="powerpc64" ;;
-  *power*|*Power* ) 
+  *power*|*Power*|*ppc* ) 
     mycpu="powerpc" ;;
   *mips* ) 
     mycpu="mips" ;;

web/question.txt

@@ -20,12 +20,6 @@ shared memory heap is also provided for the increased efficiency that results
 from that model.
 
 
-Why is it named Nimrod?
------------------------
-You have to find out for yourself. If you don't find a tongue-in-cheek 
-interpretation you will have to look harder.
-
-
 Why yet another programming language?
 -------------------------------------
 
@@ -80,7 +74,7 @@ never been designed as a general purpose VM anyway. A CLR backend is possible
 but would require much work. 
 
 What about editor support?
--------------------------------
+--------------------------
 
 - Nimrod IDE: https://github.com/nimrod-code/Aporia
 - Emacs: https://github.com/Tass/nimrod-mode
@@ -89,6 +83,16 @@ What about editor support?
 - Gedit: The `Aporia .lang file <https://github.com/nimrod-code/Aporia/blob/master/share/gtksourceview-2.0/language-specs/nimrod.lang>`_
 - jEdit: https://github.com/exhu/nimrod-misc/tree/master/jedit
 
+
+Why is it named ``proc``?
+-------------------------
+
+*Procedure* used to be the common term as opposed to a *function* which is a
+mathematical entity that has no side effects. It was planned to have ``func``
+as syntactic sugar for ``proc {.noSideEffect.}`` but the more fine-grained
+effect system makes that unimportant.
+
+
 Compilation
 ===========