manual: (faq-boot-hang-after-starting) fix config entries

Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

diff --git a/docs/manual/faq-troubleshooting.txt b/docs/manual/faq-troubleshooting.txt
index 2fdb53079d31e751e01ac136351eac6cc46e0f08..26c84604eccdc3a70927279ce93808dd542bc0ed 100644 (file)
--- a/docs/manual/faq-troubleshooting.txt
+++ b/docs/manual/faq-troubleshooting.txt
@@ -19,11 +19,11 @@ Starting dropbear sshd: generating rsa key... generating dsa key... OK
 
 then it means that your system is running, but didn't start a shell on
 the serial console. In order to have the system start a shell on your
-serial console, you have to go into the Buildroot configuration, +System
-configuration+, and modify +Port to run a getty (login prompt) on+ and
-+Baudrate to use+ as appropriate. This will automatically tune the
-+/etc/inittab+ file of the generated system so that a shell starts on
-the correct serial port.
+serial console, you have to go into the Buildroot configuration, in 
++System configuration+, modify +Run a getty (login prompt) after boot+ 
+and set the appropriate port and baud rate in the +getty options+ 
+submenu. This will automatically tune the +/etc/inittab+ file of the 
+generated system so that a shell starts on the correct serial port.
 
 [[faq-no-compiler-on-target]]
 == Why is there no compiler on the target?