diff --git a/ntfsprogs/ntfsclone.8.in b/ntfsprogs/ntfsclone.8.in
index f62ee750..6c03fb9b 100644
--- a/ntfsprogs/ntfsclone.8.in
+++ b/ntfsprogs/ntfsclone.8.in
@@ -1,9 +1,9 @@
 .\" Copyright (c) 2003\-2005 Richard Russon.
-.\" Copyright (c) 2003\-2005 Szabolcs Szakacsits.
+.\" Copyright (c) 2003\-2006 Szabolcs Szakacsits.
 .\" Copyright (c) 2004 Per Olofsson.
 .\" This file may be copied under the terms of the GNU Public License.
 .\"
-.TH NTFSCLONE 8 "December 2005" "ntfsprogs version @VERSION@"
+.TH NTFSCLONE 8 "January 2006" "ntfsprogs version @VERSION@"
 .SH NAME
 ntfsclone \- Efficiently clone, image, restore or rescue an NTFS
 .SH SYNOPSIS
@@ -51,7 +51,7 @@ NTFS support then the file can be mounted as
 .SS Sparse Files
 A file is sparse if it has unallocated blocks (holes). The reported size of
 such files are always higher than the disk space consumed by them.  The
-.B du
+.BR du
 command can tell the real disk space used by a sparse file.
 The holes are always read as zeros. All major Linux filesystem like,
 ext2, ext3, reiserfs, Reiser4, JFS and XFS, supports
@@ -85,14 +85,14 @@ with the options
 (handle sparse files "efficiently") and
 .B \-j
 (filter the archive through bzip2). Although
-.B tar
+.BR tar
 still reads and analyses the entire file, it doesn't pass on the
 large data blocks having only zeros to filters and it also avoids
 writing large amount of zeros to the disk needlessly. But since
-.B tar
+.BR tar
 can't create an archive from the standard input, you can't do this
 in\-place by just reading
-.B ntfsclone
+.BR ntfsclone
 standard output.
 .SS The Special Image Format
 It's also possible, actually it's recommended, to save an NTFS filesystem
@@ -119,7 +119,7 @@ using '\-' as the
 file.
 .SS Metadata\-only Cloning
 One of the features of
-.B ntfsclone
+.BR ntfsclone
 is that, it can also save only the NTFS metadata using the option
 .B \-m
 or
@@ -178,8 +178,8 @@ compression, encryption or streaming through a network.
 .TP
 \fB\-r\fR, \fB\-\-restore\-image\fR
 Restore from the special image format specified by
-.I SOURCE .
-If the
+.I SOURCE
+argument. If the
 .I SOURCE
 is '\-' then the image is read from the standard input.
 .TP
@@ -279,8 +279,8 @@ Pack NTFS metadata for NTFS experts
 .SH KNOWN ISSUES
 There are no known problems with
 .BR ntfsclone .
-If you find a bug please send an email describing the problem to the
-development team:
+If you think you have found a problem then please send an email describing it
+to the development team:
 .br
 .nh
 linux\-ntfs\-dev@lists.sourceforge.net
diff --git a/ntfsprogs/ntfsfix.8.in b/ntfsprogs/ntfsfix.8.in
index 47a9754e..42e53053 100644
--- a/ntfsprogs/ntfsfix.8.in
+++ b/ntfsprogs/ntfsfix.8.in
@@ -1,8 +1,8 @@
-.\" Copyright (c) 2004 Szabolcs Szakacsits.
+.\" Copyright (c) 2005-2006 Szabolcs Szakacsits.
 .\" Copyright (c) 2005 Richard Russon.
 .\" This file may be copied under the terms of the GNU Public License.
 .\"
-.TH NTFSFIX 8 "November 2005" "ntfsprogs version @VERSION@"
+.TH NTFSFIX 8 "January 2006" "ntfsprogs version @VERSION@"
 .SH NAME
 ntfsfix \- fix common errors and force Windows to check NTFS
 .SH SYNOPSIS
@@ -20,7 +20,8 @@ check for the first boot into Windows.
 .sp
 You may run
 .B ntfsfix
-on an NTFS volume if you think it's damaged and it can't be mounted.
+on an NTFS volume if you think it was damaged by Windows or some other way 
+and it can't be mounted.
 .SH OPTIONS
 Below is a summary of all the options that
 .B ntfsfix
@@ -52,8 +53,7 @@ linux\-ntfs\-dev@lists.sourceforge.net
 .hy
 .SH AUTHORS
 .B ntfsfix
-was written by Anton Altaparmakov.
-.B ntfsfix.
+was written by Anton Altaparmakov, with contributions from Szabolcs Szakacsits.
 .SH AVAILABILITY
 .B ntfsfix
 is part of the
diff --git a/ntfsprogs/ntfsresize.8.in b/ntfsprogs/ntfsresize.8.in
index 59840872..965df66d 100644
--- a/ntfsprogs/ntfsresize.8.in
+++ b/ntfsprogs/ntfsresize.8.in
@@ -1,8 +1,8 @@
-.\" Copyright (c) 2002\-2005 Szabolcs Szakacsits.
+.\" Copyright (c) 2002\-2006 Szabolcs Szakacsits.
 .\" Copyright (c) 2005 Richard Russon.
 .\" This file may be copied under the terms of the GNU Public License.
 .\"
-.TH NTFSRESIZE 8 "December 2005" "ntfsprogs version @VERSION@"
+.TH NTFSRESIZE 8 "January 2006" "ntfsprogs version @VERSION@"
 .SH NAME
 ntfsresize \- resize an NTFS filesystem without data loss
 .SH SYNOPSIS
@@ -43,6 +43,7 @@ parameter is given in kilo\-, mega\- or gigabytes respectively.
 .B Ntfsresize
 conforms to the SI, ATA, IEEE standards and the disk manufacturers
 by using k=10^3, M=10^6 and G=10^9.
+
 If both
 .B \-\-info
 and
@@ -96,6 +97,7 @@ starting sector and with the same partition type as before.
 Otherwise you won't be able to access your filesystem. Use the 'u'
 fdisk command to switch to the reliable sector unit from the
 default cylinder one.
+
 Also make sure you set the bootable flag for the partition if it
 existed before. Failing to do so you might not be able to boot your
 computer from the disk.
@@ -148,6 +150,7 @@ first.
 \fB\-f\fR, \fB\-\-force\fR
 Forces ntfsresize to proceed with the resize operation even if the filesystem
 is marked for consistency check.
+
 Please note, ntfsresize always marks the filesystem
 for consistency check before a real resize operation
 and it leaves that way for extra
@@ -167,6 +170,7 @@ Continue with the real resizing only if the test run passed.
 Support disks having hardware errors, bad sectors with those
 .B ntfsresize
 would refuse to work by default.
+
 Prior using this option, it's strongly recommended to make a backup by
 .BR ntfsclone (8)
 using the \-\-rescue option, then running 'chkdsk /f /r volume:' on Windows
@@ -174,6 +178,7 @@ from the command line. If the disk guarantee is still valid then replace it.
 It's defected. Please also note, that no software can repair these type of
 hardware errors. The most what they can do is to work around the permanent
 defects.
+
 This option doesn't have any effect if the disk is flawless.
 .TP
 \fB\-P\fR, \fB\-\-no\-progress\-bar\fR
@@ -191,7 +196,7 @@ and exit.
 Display help and exit.
 .SH EXIT CODES
 The exit code is 0 on success, non\-zero otherwise.
-.SH BUGS
+.SH KNOWN ISSUES
 No reliability problem is known. If you need
 help please try the Ntfsresize FAQ first (see below) and if you
 don't find your answer then send your question, comment or bug report to