changelog: More from gbp-dch

[dgit.git] / dgit-user.7.pod

diff --git a/dgit-user.7.pod b/dgit-user.7.pod
index c74396a56954d2ff176c2032cb022b1d71447921..18f06dac6e9a83e5d425875442f80af2ba974868 100644 (file)
--- a/dgit-user.7.pod
+++ b/dgit-user.7.pod
@@ -97,8 +97,8 @@ you can look it up with dpkg:
 
 (In this example,
 libc6 is a "multi-arch: allowed" package,
- which means that it exists in several different builds
- for different architectures.
+which means that it exists in several different builds
+for different architectures.
 That's where C<:i386> comes from.)
 
 =head2 Finding the Debian release (the "suite")
@@ -367,8 +367,9 @@ have enabled.
 You'll need a chroot for each of the secondary architectures.
 This is somewhat tiresome,
 even though Debian has excellent tools for managing chroots.
-C<sbuild-createchroot> from the sbuild package is a
-good starting point.
+C<sbuild-debian-developer-setup> from the package of the same name
+and C<sbuild-createchroot> from the C<sbuild> package are
+good starting points.
 
 Otherwise you could deinstall the packages of interest
 for those other architectures
@@ -378,7 +379,7 @@ If neither of those are an option,
 your desperate last resort is to try
 using the same version number
 as the official package for your own package.
-(The version is controlled by C<debian/changelog> - see above).
+(The version is controlled by C<debian/changelog> - see above.)
 This is not ideal because it makes it hard to tell what is installed,
 and because it will mislead and confuse apt.