|
|
@@ -31,7 +31,7 @@ generate file names by most installation tools.
|
|
|
Typically, this is the original package's version number in whatever form
|
|
|
the program's author uses. It may also include a Debian revision number
|
|
|
(for non-native packages). If both version and revision are supplied,
|
|
|
-they are seperated by a hyphen, `-'. For this reason, the original version
|
|
|
+they are separated by a hyphen, `-'. For this reason, the original version
|
|
|
may not have a hyphen in its version number.
|
|
|
.TP
|
|
|
.BR Maintainer: " <fullname email>"
|
|
|
@@ -45,7 +45,7 @@ software that was packaged.
|
|
|
The format for the package description is a short brief summary on the
|
|
|
first line (after the "Description" field). The following lines can be
|
|
|
used as a longer, more detailed description. Each line of the long description
|
|
|
-must be preceded by a space, and blank lines in the long desription must
|
|
|
+must be preceded by a space, and blank lines in the long description must
|
|
|
contain a single '.' following the preceding space.
|
|
|
.
|
|
|
.SH OPTIONAL FIELDS
|
|
|
@@ -157,7 +157,7 @@ used in the case of several packages all providing the same service.
|
|
|
For example, sendmail and exim can serve as a mail server, so they
|
|
|
provide a common package (`mail-transport-agent') on which other packages
|
|
|
can depend. This will allow sendmail or exim to serve as a valid option
|
|
|
-to satisy the dependency. This prevents the packages that depend on a mail
|
|
|
+to satisfy the dependency. This prevents the packages that depend on a mail
|
|
|
server from having to know the package names for all of them, and using
|
|
|
`|' to separate the list.
|
|
|
.LP
|