3 files changed, 35 insertions, 53 deletions

diff --git a/lang/cli/pkg-descr b/lang/cli/pkg-descr
index d458a58a8328..18b848fc0367 100644
--- a/lang/cli/pkg-descr
+++ b/lang/cli/pkg-descr
@@ -1,18 +1,15 @@
-The Common Language Infrastructure (CLI) is the ECMA standard that describes
-the core of the .NET Framework world. The Shared Source CLI is a a working
-implementation of the ECMA CLI and the ECMA C# language specification.
-
-This implementation is released under a shared source initiative. Please see
-the accompanying license.
-
-The Shared Source CLI goes beyond the printed specification of the ECMA
-standards, providing a working implementation for CLI developers to explore
-and understand. It will be of interest to academics and researchers wishing to
-teach and explore modern programming language concepts, and to .NET developers
-interested in how the technology works. 
+	The Common Language Infrastructure (CLI) is the ECMA standard that
+describes the core of the .NET Framework world. The Shared Source CLI is a a
+working implementation of the ECMA CLI and the ECMA C# language specification.
+	This implementation is released under a shared source initiative. Please
+see the accompanying license.
+	The Shared Source CLI goes beyond the printed specification of the ECMA
+standards, providing a working implementation for CLI developers to explore and
+understand. It will be of interest to academics and researchers wishing to teach
+and explore modern programming language concepts, and to .NET developers
+interested in how the technology works.
 
 Features:
-
 o An implementation of the runtime for the Common Language Infrastructure
   (ECMA-335);
 o Compilers that work with the Shared Source CLI for C# (ECMA-334) and JScript;
@@ -24,5 +21,4 @@ o The Platform Adaptation Layer (PAL) used to port the Shared Source CLI from
 o Build environment tools (nmake, build, and others);
 o Documentation for the implementation;
 o Test suites used to verify the implementation.
-
 WWW: http://msdn.microsoft.com/net/sscli/
diff --git a/lang/p5-Tcl/pkg-descr b/lang/p5-Tcl/pkg-descr
index 5142825a6362..27cf53cfeaa6 100644
--- a/lang/p5-Tcl/pkg-descr
+++ b/lang/p5-Tcl/pkg-descr
@@ -1,26 +1,20 @@
-The Tcl extension module gives access to the Tcl library
-with functionality and interface similar to the C
-functions of Tcl.  In other words, you can
+The Tcl extension module gives access to the Tcl library with functionality and
+interface similar to the C functions of Tcl.  In other words, you can:
 
 create Tcl interpreters
-        The Tcl interpreters so created are Perl objects
-        whose destructors delete the interpreters cleanly
-        when appropriate.
+	The Tcl interpreters so created are Perl objects whose destructors
+	delete the interpreters cleanly when appropriate.
 
 execute Tcl code in an interpreter
-        The code can come from strings, files or Perl
-        filehandles.
+        The code can come from strings, files or Perl filehandles.
 
 bind in new Tcl procedures
-        The new procedures can be either C code (with
-        addresses presumably obtained using dl_open and
-        dl_find_symbol) or Perl subroutines (by name,
-        reference or as anonymous subs). The (optional)
-        deleteProc callback in the latter case is another
-        perl subroutine which is called when the command
-        is explicitly deleted by name or else when the
-        destructor for the interpreter object is
-        explicitly or implicitly called.
+	The new procedures can be either C code (with addresses presumably
+	obtained using dl_open and dl_find_symbol) or Perl subroutines (by name,
+	reference or as anonymous subs). The (optional) deleteProc callback in
+	the latter case is another perl subroutine which is called when the
+	command is explicitly deleted by name or else when the destructor for
+	the interpreter object is explicitly or implicitly called.
 
 Manipulate the result field of a Tcl interpreter
 
diff --git a/lang/scm/pkg-descr b/lang/scm/pkg-descr
index dd26869dd6d5..5dfd428c9aba 100644
--- a/lang/scm/pkg-descr
+++ b/lang/scm/pkg-descr
@@ -1,32 +1,24 @@
-Scm conforms to Revised^5 Report on the Algorithmic Language Scheme
-and the IEEE P1178 specification.  Scm is written in C and runs under
-Amiga, Atari-ST, MacOS, MS-DOS, OS/2, NOS/VE, Unicos, VMS, Unix and
-similar systems.  ASCII and EBCDIC are supported.
+Scm conforms to Revised^5 Report on the Algorithmic Language Scheme and the IEEE
+P1178 specification.  Scm is written in C and runs under Amiga, Atari-ST, MacOS,
+MS-DOS, OS/2, NOS/VE, Unicos, VMS, Unix and similar systems.  ASCII and EBCDIC
+are supported.
 
-Documentation is included explaining the many Scheme Language
-extensions in scm, the internal representation and how to extend or
-include scm in other programs.
+Documentation is included explaining the many Scheme Language extensions in scm,
+the internal representation and how to extend or include scm in other programs.
 
 SLIB is a portable Scheme library which SCM uses.
 
 SLIB-PSD is a portable debugger for Scheme (requires emacs editor).
 
--------------------Readme.FreeBSD------------------------
+The init file is hard-coded as /usr/local/share/scm/Init.scm.  Alternatively,
+one can set the environment variable SCM_INIT_PATH to the pathname of Init.scm.
 
-1.  Pathname dependencies:
-	The init file is hardcoded as /usr/local/share/scm/Init.scm.
-	Alternatively, one can set the environment variable SCM_INIT_PATH to
-	the pathname of Init.scm.
+The library files are in /usr/local/share/scm/slib.  Alternatively, one can set
+the environment variable SCHEME_LIBRARY_PATH to the slib directory.  Remember to
+use a trailing / on the pathname.
 
-	The library files are in /usr/local/share/scm/slib.  Alternatively,
-	one can set the environment variable SCHEME_LIBRARY_PATH to
-	the slib directory.  Remember to use a trailing / on the
-	pathname.
-
-2.  I have -DSICP turn on by default, since I expect this to be the major
-reason for this port.  This means test.scm will fail on 3 tests in section 6.1.
-If strict R4S compliance is important to you, recompile w/o the SICP flag.
-
-							Jeffrey Hsu
+By default -DSICP is turned on, with the expectation that this is the major
+reason for this port.  This means test.scm will fail on three tests in section
+6.1.  Where strict R4S compliance is important, recompile without the SICP flag.
 
 WWW: http://swissnet.ai.mit.edu/~jaffer/SCM.html