Update documentation for tty .conf option

Signed-off-by: Joachim Nilsson <troglobit@gmail.com>

README.md

@@ -151,7 +151,6 @@ up the TTY, optionally clearing it, and waits for user input before
 handing over to `/bin/login`, which handles all nasty bits with PAM etc.
 
 ```conf
-# /etc/finit.conf
 tty [12345] /dev/tty1    38400  linux
 tty [12345] /dev/ttyAMA0 115200 vt100 noclear
 ```
@@ -419,7 +418,8 @@ append="init=/sbin/finit --debug"
 To debug startup issues, in particular issues with getty/login, try
 `configure --enable-fallback-shell`.  When no TTYs are detected, and
 Finit is configured with this option, Finit will try to start a bare
-`/bin/sh` on the boot console.
+`/bin/sh` on the boot console.  Remember, this is only for debugging
+and would leave your production system potentially wide open.
 
 
 Origin & References

doc/config.md

@@ -137,14 +137,19 @@ Syntax:
   Include another configuration file.  Absolute path required.
 
 * `tty [LVLS] <DEV> [BAUD] [TERM] [noclear]`  
-  Start a getty on the given TTY device DEV, in the given runlevels.  If
+  Start the built-in getty on the given TTY device DEV, in the given
-  no tty setting is given in `finit.conf` no login is possible.  Use the
+  runlevels.  Default baud rate is `38400`.
-  `service` stanza to start a stand-alone shell for really bare bones
-  systems.
 
-  Finit comes with a lightweight built-in getty, which after it has
+```conf
-  opened a TTY and the user has input a username, calls `/bin/login`
+        tty [12345] /dev/ttyAMA0 115200 noclear
-  like any other getty.
+```
+
+  On really bare bones systems Finit offers a fallback shell, but one
+  can also use the `service` stanza to start a stand-alone shell:
+
+```shell
+        configure --enable-fallback-shell
+```
 
 * `console <DEV>`  
   Use this, along with a matching `tty DEV` line, to mark this TTY as a