Adjust for terminfo(3)/terminfo(5) (at least in this context, there
are no significant user-visible changes, except that the several
TERMs can be no more consulted by reading /usr/share/misc/termcap!)

Thanks to yambo at #NetBSD@Freenode for spotting that!

Index: chap-cons.xml
===================================================================
RCS file: /cvsroot/htdocs/docs/guide/en/chap-cons.xml,v
retrieving revision 1.10
diff -u -p -r1.10 chap-cons.xml
--- chap-cons.xml	3 Dec 2017 20:30:47 -0000	1.10
+++ chap-cons.xml	8 Sep 2018 10:49:24 -0000
@@ -366,11 +366,11 @@ options WS_KERNEL_BG=WSCOL_xxx</programl
 	<sect4 id="chap-cons-wscons-wsdisplay-colors-term">
 	  <title>Getting applications to use colors on the console</title>
 	  
-	  <para>&os; uses the <database>termcap</database> database to
+	  <para>&os; uses the <database>terminfo</database> database to
 	  tell applications what the current terminal's capabilities are.
 	  For example, some terminals don't support colors, some don't
 	  support underlining (PC VGA terminals don't, for example) etc.
-	  The <envar>TERM</envar> environment variable tells the termcap
+	  The <envar>TERM</envar> environment variable tells the terminfo
 	  library the type of terminal.  It then refers to its database
 	  for the options.</para>
 
@@ -391,7 +391,7 @@ options WS_KERNEL_BG=WSCOL_xxx</programl
 	    <literal>ansi</literal> terminal type, which supports
 	    ANSI color codes.  However, other functionality may be
 	    missing with this terminal type.  You can have a look
-	    at the file <filename>/usr/share/misc/termcap</filename>
+	    at the file <filename>/usr/share/misc/terminfo</filename>
 	    to see if you can find a useful match for your
 	    console type.
 	  </para>