Note that it is possible for setupterm to expect a different set of
capabilities than are actually present in the file. Either the
- database may have been updated since setupterm has been recompiled
+ database may have been updated since setupterm was recompiled
(resulting in extra unrecognized entries in the file) or the program
may have been recompiled more recently than the database was updated
(resulting in missing entries). The routine setupterm must be prepared
@@ -283,11 +283,11 @@
The magic number in a binary terminfo file is the first 16-bits (two
bytes). Besides making it more reliable for the library to check that
- a file is terminfo, utilities such as file also use that to tell what
- the file-format is. System V defined more than one magic number, with
- 0433, 0435 as screen-dumps (see scr_dump(5)). This implementation uses
- 01036 as a continuation of that sequence, but with a different high-
- order byte to avoid confusion.
+ a file is terminfo, utilities such as file(1) also use that to tell
+ what the file-format is. System V defined more than one magic number,
+ with 0433, 0435 as screen-dumps (see scr_dump(5)). This implementation
+ uses 01036 as a continuation of that sequence, but with a different
+ high-order byte to avoid confusion.
@@ -376,7 +376,7 @@
extended number support for ncurses 6.1
Eric S. Raymond
- documented legacy terminfo format, e.g., from pcurses.
+ documented legacy terminfo format, e.g., from pcurses.