path: root/debhelper.pod
diff options
authorjoey <joey>2001-06-21 02:09:34 +0000
committerjoey <joey>2001-06-21 02:09:34 +0000
commit23a8188b668fbbdd8e84260040e276a6ef3a879c (patch)
treebef3e0d3db9049d16dfb46f887199e0e741c94fb /debhelper.pod
parent6f79d5cba3c0d84591a8147576a494a7eccffe51 (diff)
r482: * Spellpatch, Closes: #101553
Diffstat (limited to 'debhelper.pod')
1 files changed, 3 insertions, 3 deletions
diff --git a/debhelper.pod b/debhelper.pod
index a93034e..85b3fd2 100644
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -194,7 +194,7 @@ you have a package that builds many binary packages, you will need to also
use the -p flag to specify which binary package the debhelper program will
act on.
-=head2 Debhelper compatability levels
+=head2 Debhelper compatibility levels
From time to time, major non-backwards-compatible changes need to be made
to debhelper, to keep it clean and well-designed as needs change and its
@@ -208,7 +208,7 @@ debhelper should be used. There are currently 3:
=item V1
Setting DH_COMPAT=1 (or leaving it unset) causes debhelper to act in
-compatability mode. It will use debian/tmp as the package tree
+compatibility mode. It will use debian/tmp as the package tree
directory for the first binary package listed in the control file, while using
debian/<package> for all other packages listed in the control file.
This mode is deprecated.
@@ -282,7 +282,7 @@ that modifies files on the build system.
-Specifies what compatability level debhelper should run at. See above.
+Specifies what compatibility level debhelper should run at. See above.
=item DH_NO_ACT