commit - 5af91fc0052cabeee956c8b0b3c61299d85f795e
commit + 338c6432501e9c50a5fc03b8b2f917b54b8f5a0b
blob - 528c6910d8a6ef23f682846efddb821bec539977
blob + bf3628c12bea03d8196029316babd0d0882f7880
--- doc/FAQ.txt
+++ doc/FAQ.txt
@@ -65,8 +65,15 @@ A: On Linux/glibc with chroot enabled you need to put 
    linking ngircd statically does not help this. The only known workaround
    is to either disable chroot support or to link against dietlibc instead
    of glibc. (tnx to Sebastian Siewior)
+Q: I have added an [Oper] section, how do i log on as IRC operator?
+A: You can use the /OPER command in your IRC client to become an IRC operator.
+   ngIRCd will also log all OPER requests (using syslog), if OPER fails you
+   can look there to determine why it did not work (bad password, unauthorized
+   host mask, etc.)
+Q: I am an IRC operator, but MODE doesn't work!
+A: You need to set 'OperCanUseMode = yes' in ngircd.conf to enable MODE for IRC
+   operators.
 
-
 IV. Bugs!?
 ~~~~~~~~~~
 Q: Is there a list of known bugs and desired feature enhancements?