Edited DESCR in the case of:

 File too long (should be no more than 24 lines).
 Line too long (should be no more than 80 characters).
 Trailing empty lines.
 Trailing white-space.
Trucated the long files as best as possible while preserving the most info
contained in them.

6 files changed, 98 insertions, 134 deletions

diff --git a/sysutils/agedu/DESCR b/sysutils/agedu/DESCR
index cd7823b2a44..ed74862ddf6 100644
--- a/sysutils/agedu/DESCR
+++ b/sysutils/agedu/DESCR
@@ -1,30 +1,24 @@
-Suppose you're running low on disk space. You need to free some
-up, by finding something that's a waste of space and deleting it
-(or moving it to an archive medium). How do you find the right
-stuff to delete, that saves you the maximum space at the cost of
-minimum inconvenience?
+Suppose you're running low on disk space. You need to free some up, by finding
+something that's a waste of space and deleting it (or moving it to an archive
+medium). How do you find the right stuff to delete, that saves you the maximum
+space at the cost of minimum inconvenience?
 
-Unix provides the standard du utility, which scans your disk and
-tells you which directories contain the largest amounts of data.
-That can help you narrow your search to the things most worth
-deleting.
+Unix provides the standard du utility, which scans your disk and tells you which
+directories contain the largest amounts of data. That can help you narrow your
+search to the things most worth deleting.
 
-However, that only tells you what's big. What you really want to
-know is what's too big. By itself, du won't let you distinguish
-between data that's big because you're doing something that needs
-it to be big, and data that's big because you unpacked it once and
-forgot about it.
+However, that only tells you what's big. What you really want to know is what's
+too big. By itself, du won't let you distinguish between data that's big because
+you're doing something that needs it to be big, and data that's big because you
+unpacked it once and forgot about it.
 
-Most Unix file systems, in their default mode, helpfully record
-when a file was last accessed. Not just when it was written or
-modified, but when it was even read. So if you generated a large
-amount of data years ago, forgot to clean it up, and have never
-used it since, then it ought in principle to be possible to use
-those last-access time stamps to tell the difference between that
-and a large amount of data you're still using regularly.
+Most Unix file systems, in their default mode, helpfully record when a file was
+last accessed. Not just when it was written or modified, but when it was even
+read. So if you generated a large amount of data years ago, forgot to clean it
+up, and have never used it since, then it ought in principle to be possible to
+use those last-access time stamps to tell the difference between that and a
+large amount of data you're still using regularly.
 
-agedu is a program which does this. It does basically the same sort
-of disk scan as du, but it also records the last-access times of
-everything it scans. Then it builds an index that lets it efficiently
-generate reports giving a summary of the results for each subdirectory,
-and then it produces those reports on demand.
+agedu does same disk scan as du, but also records the last-access times of
+everything. Then it builds an index that lets it efficiently generate reports
+giving a summary of the results for each subdirectory.
diff --git a/sysutils/bup/DESCR b/sysutils/bup/DESCR
index 5512feb9597..69824b2d487 100644
--- a/sysutils/bup/DESCR
+++ b/sysutils/bup/DESCR
@@ -1,41 +1,22 @@
-bup is a program that backs things up.  bup has a few advantages
-over other backup software:
-
-It uses a rolling checksum algorithm (similar to rsync) to split
-large files into chunks. The most useful result of this is you can
-backup huge virtual machine (VM) disk images, databases, and XML
-files incrementally, even though they're typically all in one huge
-file, and not use tons of disk space for multiple versions.
-
-It uses the packfile format from git (the open source version
-control system), so you can access the stored data even if you
-don't like bup's user interface.
-
-Unlike git, it writes packfiles directly (instead of having a
-separate garbage collection / repacking stage) so it's fast even
-with gratuitously huge amounts of data. bup's improved index formats
-also allow you to track far more filenames than git (millions) and
-keep track of far more objects (hundreds or thousands of gigabytes).
-
-Data is "automagically" shared between incremental backups without
-having to know which backup is based on which other one - even if
-the backups are made from two different computers that don't even
-know about each other. You just tell bup to back stuff up, and it
-saves only the minimum amount of data needed.
-
-You can back up directly to a remote bup server, without needing
-tons of temporary disk space on the computer being backed up.  And
-if your backup is interrupted halfway through, the next run will
-pick up where you left off. And it's easy to set up a bup server:
-just install bup on any machine where you have ssh access.
-
-Bup can use "par2" redundancy to recover corrupted backups even if
-your disk has undetected bad sectors.
-
-Even when a backup is incremental, you don't have to worry about
-restoring the full backup, then each of the incrementals in turn;
-an incremental backup acts as if it's a full backup, it just takes
-less disk space.
-
-You can mount your bup repository as a FUSE filesystem and access
-the content that way, and even export it over Samba.
+bup is a program that backs things up.  bup has a few advantages over other
+backup software:
+
+It uses a rolling checksum algorithm (similar to rsync) to split large files
+into chunks. The most useful result of this is you can backup huge virtual
+machine (VM) disk images, databases, and XML files incrementally, even though
+they're typically all in one huge file, and not use tons of disk space for
+multiple versions.
+
+It uses the packfile format from git (the open source version control system),
+so you can access the stored data even if you don't like bup's user interface.
+
+Unlike git, it writes packfiles directly (instead of having a separate garbage
+collection/repacking stage) so it's fast even with gratuitously huge amounts of 
+data. bup's improved index formats also allow you to track far more filenames
+than git (millions) and keep track of far more objects (hundreds or thousands of
+gigabytes).
+
+Data is "automagically" shared between incremental backups without having to
+know which backup is based on which other one - even if the backups are made
+from two different computers that don't even know about each other. You just
+tell bup to back stuff up, and it saves only the minimum amount of data needed.
diff --git a/sysutils/gkrellm-server/DESCR b/sysutils/gkrellm-server/DESCR
index 094dfd3f201..0928bcb7742 100644
--- a/sysutils/gkrellm-server/DESCR
+++ b/sysutils/gkrellm-server/DESCR
@@ -1,28 +1,24 @@
 With a single process, GKrellM manages multiple stacked monitors and supports
-applying themes to match the monitors appearance to your window manager,
-Gtk, or any other theme.
-
-  * SMP CPU, Disk, Proc, and active net interface monitors with LEDs.
-  * Internet monitor that displays current and charts historical port hits
-
-  * Memory and swap space usage meters and a system uptime monitor.
-  * File system meters show capacity/free space and can mount/umount.
-  * A mailbox monitor which can launch mail reader, remote mail fetch.
-  * Clock/calendar and hostname display.
-  * APM laptop battery monitor.
-  * CPU/motherboard temperature display if lm_sensors modules installed.
-
-  * Multiple monitors managed by a single process to reduce system load.
-  * A timer button that can execute PPP or ISDN logon/logoff scripts.
-  * Charts are autoscaling with configurable grid line resolution, or
-    can be set to a fixed scale mode.
-  * Separate colors for "in" and "out" data.  The in color is used for
-    CPU user time, disk read, forks, and net receive data.  The out color
-    is used for CPU sys time, disk write, load, and net transmit data.
-  * Commands can be configured to run when monitor labels are clicked.
-  * GKrellM is plugin capable so special interest monitors can be created.
-  * A different theme can be created with the GIMP.
-
-The gkrellm2-server package installs the monitoring part of GKrellM, which
-can be made to run as a daemon to be polled over the network by the GKrellM
-client as found in the gkrellm2 package.
+applying themes to match the monitors appearance to your window manager, Gtk, or
+any other theme.
+ * SMP CPU, Disk, Proc, and active net interface monitors with LEDs.
+ * Internet monitor that displays current and charts historical port hits
+ * Memory and swap space usage meters and a system uptime monitor.
+ * File system meters show capacity/free space and can mount/umount.
+ * A mailbox monitor which can launch mail reader, remote mail fetch.
+ * Clock/calendar and hostname display.
+ * APM laptop battery monitor.
+ * CPU/motherboard temperature display if lm_sensors modules installed.
+ * Multiple monitors managed by a single process to reduce system load.
+ * A timer button that can execute PPP or ISDN logon/logoff scripts.
+ * Charts are autoscaling with configurable grid line resolution, or can be set
+   to a fixed scale mode.
+ * Separate colors for "in" and "out" data.  The in color is used for CPU user
+   time, disk read, forks, and net receive data.  The out color is used for CPU
+   sys time, disk write, load, and net transmit data.
+ * Commands can be configured to run when monitor labels are clicked.
+ * GKrellM is plugin capable so special interest monitors can be created.
+ * A different theme can be created with the GIMP.
+The gkrellm2-server package installs the monitoring part of GKrellM, which can
+be made to run as a daemon to be polled over the network by the GKrellM client
+as found in the gkrellm2 package.
diff --git a/sysutils/gkrellm-share/DESCR b/sysutils/gkrellm-share/DESCR
index 9a5cc549218..4414758d43b 100644
--- a/sysutils/gkrellm-share/DESCR
+++ b/sysutils/gkrellm-share/DESCR
@@ -1,29 +1,24 @@
 With a single process, GKrellM manages multiple stacked monitors and supports
-applying themes to match the monitors appearance to your window manager,
-Gtk, or any other theme.
-
-  * SMP CPU, Disk, Proc, and active net interface monitors with LEDs.
-  * Internet monitor that displays current and charts historical port hits
-
-  * Memory and swap space usage meters and a system uptime monitor.
-  * File system meters show capacity/free space and can mount/umount.
-  * A mailbox monitor which can launch mail reader, remote mail fetch.
-  * Clock/calendar and hostname display.
-  * APM laptop battery monitor.
-  * CPU/motherboard temperature display if lm_sensors modules installed.
-
-  * Multiple monitors managed by a single process to reduce system load.
-  * A timer button that can execute PPP or ISDN logon/logoff scripts.
-  * Charts are autoscaling with configurable grid line resolution, or
-    can be set to a fixed scale mode.
-  * Separate colors for "in" and "out" data.  The in color is used for
-    CPU user time, disk read, forks, and net receive data.  The out color
-    is used for CPU sys time, disk write, load, and net transmit data.
-  * Commands can be configured to run when monitor labels are clicked.
-  * GKrellM is plugin capable so special interest monitors can be created.
-  * A different theme can be created with the GIMP.
-
-GKrellM can either monitor the host it is running on or poll a server
-over the network.  Both packages, gkrellm2 and gkrellm2-server, share a
-certain amount of data, notably i18n files which are included in the
-gkrellm2-share package.
+applying themes to match the monitors appearance to your window manager, Gtk, or
+any other theme.
+ * SMP CPU, Disk, Proc, and active net interface monitors with LEDs.
+ * Internet monitor that displays current and charts historical port hits
+ * Memory and swap space usage meters and a system uptime monitor.
+ * File system meters show capacity/free space and can mount/umount.
+ * A mailbox monitor which can launch mail reader, remote mail fetch.
+ * Clock/calendar and hostname display.
+ * APM laptop battery monitor.
+ * CPU/motherboard temperature display if lm_sensors modules installed.
+ * Multiple monitors managed by a single process to reduce system load.
+ * A timer button that can execute PPP or ISDN logon/logoff scripts.
+ * Charts are autoscaling with configurable grid line resolution, or can be set
+   to a fixed scale mode.
+ * Separate colors for "in" and "out" data.  The in color is used for CPU user
+   time, disk read, forks, and net receive data.  The out color is used for CPU
+   sys time, disk write, load, and net transmit data.
+ * Commands can be configured to run when monitor labels are clicked.
+ * GKrellM is plugin capable so special interest monitors can be created.
+ * A different theme can be created with the GIMP.
+GKrellM can either monitor the host it is running on or poll a server over the
+network. Both packages, gkrellm2 and gkrellm2-server, share a certain amount of
+data, notably i18n files which are included in the gkrellm2-share package.
diff --git a/sysutils/heirloom-doc/DESCR.common b/sysutils/heirloom-doc/DESCR.common
index 6157bca6b3f..0f85df7717c 100644
--- a/sysutils/heirloom-doc/DESCR.common
+++ b/sysutils/heirloom-doc/DESCR.common
@@ -1,4 +1,3 @@
-The Heirloom Project provides traditional implementations of standard
-Unix utilities. In many cases, they have been derived from original
-Unix material released as Open Source by Caldera and Sun.
-
+The Heirloom Project provides traditional implementations of standard Unix
+utilities. In many cases, they have been derived from original Unix material
+released as Open Source by Caldera and Sun.
diff --git a/sysutils/xenkernel41/DESCR b/sysutils/xenkernel41/DESCR
index db6df31f21a..a1e45de75cf 100644
--- a/sysutils/xenkernel41/DESCR
+++ b/sysutils/xenkernel41/DESCR
@@ -1,10 +1,9 @@
-Xen is a virtual machine monitor which supports running multiple
-guests operating systems on a single machine.  Guest OSes (also called "domains")
-require a modified kernel which supports Xen hypercalls in replacement
-to access to the physical hardware.  At boot, the xen kernel is loaded
-along with the guest kernel for the first domain (called domain0).
-domain0 has privileges to access the physical hardware (PCI
-and ISA devices), administrate other domains and provide virtual
-devices (disks and network) to other domains.
+Xen is a virtual machine monitor which supports running multiple guests
+operating systems on a single machine. Guest OSes (also called "domains")
+require a modified kernel which supports Xen hypercalls in replacement to access
+to the physical hardware. At boot, the xen kernel is loaded along with the guest
+kernel for the first domain (called domain0). domain0 has privileges to access
+the physical hardware (PCI and ISA devices), administrate other domains and
+provide virtual devices (disks and network) to other domains.
 
 This package contains the Xen4 kernel itself.