Index: generic/aolstub.c
===================================================================
diff -u -r62dc29237e6a643169841f002784c7dc0b29f201 -r83e2a1bc1e93733b0459e24666828c4a3f2bce63
--- generic/aolstub.c	(.../aolstub.c)	(revision 62dc29237e6a643169841f002784c7dc0b29f201)
+++ generic/aolstub.c	(.../aolstub.c)	(revision 83e2a1bc1e93733b0459e24666828c4a3f2bce63)
@@ -13,9 +13,9 @@
  * (a) Archiware Inc.
  *
  * (b) Vienna University of Economics and Business
- *     Institute of Information Systems and New Media
- *     A-1020, Welthandelsplatz 1
- *     Vienna, Austria
+ *      Institute of Information Systems and New Media
+ *      A-1020, Welthandelsplatz 1
+ *      Vienna, Austria
  *
  * This work is licensed under the MIT License https://www.opensource.org/licenses/MIT
  *
@@ -55,13 +55,13 @@
  *
  * NsNsf_Init --
  *
- *    Loads the package for the first time, i.e. in the startup thread.
+ *      Loads the package for the first time, i.e. in the startup thread.
  *
  * Results:
- *    Standard Tcl result
+ *      Standard Tcl result
  *
  * Side effects:
- *    Package initialized. Tcl commands created.
+ *      Package initialized. Tcl commands created.
  *
  *----------------------------------------------------------------------------
  */
@@ -98,42 +98,42 @@
  *
  * NsNsf_Init1 --
  *
- *    Loads the package in each thread-interpreter.
- *    This is needed since Nsf Class/Object commands are not copied
- *    from the startup thread to the connection (or any other) thread.
- *    during AOLserver initialization and/or thread creation times.
+ *      Loads the package in each thread-interpreter.
+ *      This is needed since Nsf Class/Object commands are not copied
+ *      from the startup thread to the connection (or any other) thread.
+ *      during AOLserver initialization and/or thread creation times.
  *
- *    Why ?
+ *      Why ?
  *
- *    Simply because these two commands declare a delete callback which is
- *    unsafe to call in any other thread but in the one which created them.
+ *      Simply because these two commands declare a delete callback which is
+ *      unsafe to call in any other thread but in the one which created them.
  *
- *    To understand this, you may need to get yourself acquainted with the
- *    mechanics of the AOLserver, more precisely, with the way Tcl interps
- *    are initialized (dive into nsd/tclinit.c in AOLserver distro).
+ *      To understand this, you may need to get yourself acquainted with the
+ *      mechanics of the AOLserver, more precisely, with the way Tcl interps
+ *      are initialized (dive into nsd/tclinit.c in AOLserver distro).
  *
- *    So, we made sure (by patching the AOLserver code) that no commands with
- *    delete callbacks declared, are ever copied from the startup thread.
- *    Additionally, we also made sure that AOLserver properly invokes any
- *    AtCreate callbacks. So, instead of activating those callbacks *after*
- *    running the Tcl-initialization script (which is the standard behavior)
- *    we activate them *before*. So we may get a chance to configure the
- *    interpreter correctly for any commands within the init script.
+ *      So, we made sure (by patching the AOLserver code) that no commands with
+ *      delete callbacks declared, are ever copied from the startup thread.
+ *      Additionally, we also made sure that AOLserver properly invokes any
+ *      AtCreate callbacks. So, instead of activating those callbacks *after*
+ *      running the Tcl-initialization script (which is the standard behavior)
+ *      we activate them *before*. So we may get a chance to configure the
+ *      interpreter correctly for any commands within the init script.
  *
- *    Proper Nsf usage would be to declare all resources (classes, objects)
- *    at server initialization time and let AOLserver machinery to copy them
+ *      Proper Nsf usage would be to declare all resources (classes, objects)
+ *      at server initialization time and let AOLserver machinery to copy them
  *    (or re-create them, better yet) in each new thread.
- *    Resources created within a thread are automatically garbage-collected
- *    on thread-exit time, so don't create any Nsf resources there.
- *    Create them in the startup thread and they will automatically be copied
- *    for you.
- *    Look in <serverroot>/modules/tcl/nsf for a simple example.
+ *      Resources created within a thread are automatically garbage-collected
+ *      on thread-exit time, so don't create any Nsf resources there.
+ *      Create them in the startup thread and they will automatically be copied
+ *      for you.
+ *      Look in <serverroot>/modules/tcl/nsf for a simple example.
  *
  * Results:
- *    Standard Tcl result.
+ *      Standard Tcl result.
  *
  * Side effects:
- *    Tcl commands created.
+ *      Tcl commands created.
  *
  *----------------------------------------------------------------------------
  */
@@ -163,13 +163,13 @@
  *
  * Ns_ModuleInit --
  *
- *    Called by the AOLserver when loading shared object file.
+ *      Called by the AOLserver when loading shared object file.
  *
  * Results:
- *    Standard AOLserver result
+ *      Standard AOLserver result
  *
  * Side effects:
- *    Many. Depends on the package.
+ *      Many. Depends on the package.
  *
  *----------------------------------------------------------------------------
  */