Within a relative path reference, the complete path segments "." and
".." have special meanings: "the current hierarchy level" and "the
level above this hierarchy level", respectively, just like they do in
-Unix-like systems.
+UNIX-like systems.
A path segment which contains a colon
character can't be used as the first segment of a relative URI path
(e.g., "this:that"), because it would be mistaken for a scheme name;
server requests a password, the program interpreting the URL
should request one from the user.
.PP
-Here are some of the most common schemes in use on Unix-like systems
+Here are some of the most common schemes in use on UNIX-like systems
that are understood by many tools.
Note that many tools using URIs also have internal schemes or specialized
schemes; see those tools' documentation for information on those schemes.
parenthesis and section number; see
.BR man (7)
for more information on the meaning of the section numbers.
-This URI scheme is unique to Unix-like systems (such as Linux)
+This URI scheme is unique to UNIX-like systems (such as Linux)
and is not currently registered by the IETF.
An example is <man:ls(1)>.
.PP
This scheme refers to online info reference pages (generated from
texinfo files),
a documentation format used by programs such as the GNU tools.
-This URI scheme is unique to Unix-like systems (such as Linux)
+This URI scheme is unique to UNIX-like systems (such as Linux)
and is not currently registered by the IETF.
As of this writing, GNOME and KDE differ in their URI syntax
and do not accept the other's syntax.
Only complete word matches are returned.
See
.BR whatis (1).
-This URI scheme is unique to Unix-like systems (such as Linux)
+This URI scheme is unique to UNIX-like systems (such as Linux)
and is not currently registered by the IETF.
.PP
.B "ghelp \- GNOME help documentation"