prun man pages: cleanup

Remove authors from prun.md, reformat
Remove copy-and-paste errors in pman.md

prun/pman.md

@@ -1,4 +1,4 @@
-% PTYPE(1) | Mariux Tools Documentation
+% PMAN(1) | Mariux Tools Documentation
 
 NAME
 ====
@@ -13,7 +13,7 @@ SYNOPSIS
 DESCRIPTION
 ===========
 
-**ptype** uses the PATH set in the package wrapper and tries to find a manual page in the package directory.
+**pman** uses the PATH set in the package wrapper and tries to find a manual page in the package directory.
 
 EXAMPLES
 ========

prun/prun.md

@@ -17,8 +17,7 @@ Runs applications, scripting languages, compilers, etc., from a dedicated direct
 
 The main usage is to run software in a specific version, or to provide a given environment. See **EXAMPLES** below.
 
-There are some advantages over so called 'virtual environments' and the like. Packages are immutable, once installed they never change, thereby increasing the chances that an old program/script will also run in a few years. The packages also 
-use a standardized call procedure, independent of personal (un-)settings, thus an existing pipeline may be shared between different users.
+There are some advantages over so called 'virtual environments' and the like. Packages are immutable, once installed they never change, thereby increasing the chances that an old program/script will also run in a few years. The packages also use a standardized call procedure, independent of personal (un-)settings, thus an existing pipeline may be shared between different users.
 
 The whole 'magic' behind **prun** is, that it transparently sets the PATH variable and possibly LD_LIBRARY_PATH for the actual call without spoiling the default environment.
 
@@ -89,11 +88,6 @@ BUGS
 
 See GitHub Issues: <https://github.molgen.mpg.de/mariux64/mxtools>
 
-AUTHORS
-=======
-
-D.Buczek, P.Marquardt, M.Tolzmann
-
 SEE ALSO
 ========