Mostly whitespace fixes

Removed tab characters and trailing spaces and added spaces between
"if(", "for(", "while(" and "switch(".

3 files changed, 15 insertions, 15 deletions

diff --git a/docs/FAQ.txt b/docs/FAQ.txt
index 6adfb2b3..5a3baace 100644
--- a/docs/FAQ.txt
+++ b/docs/FAQ.txt
@@ -69,7 +69,7 @@ A: There are a lot of ways:
    
    - If you're a programmer, an artist or just willing to help in any way, you
      can become part of the development team. Send an e-mail to
-     blame582@gmail.com explaining what you want to do, or join our irc
+     irarice@gmail.com explaining what you want to do, or join our irc
      channel: #aethyra @ irc.freenode.net.
    
    - You can be a beta tester. Just play with Aethyra and report
diff --git a/docs/INSTALL/win32.txt b/docs/INSTALL/win32.txt
index 2fd12f8c..34d26e3f 100644
--- a/docs/INSTALL/win32.txt
+++ b/docs/INSTALL/win32.txt
@@ -46,7 +46,7 @@ This tutorial is written and tested with the latest beta version, which is
 the old stable version, so don't do that. Get Dev-C++ here:
 
   http://www.bloodshed.net/
- 
+
 After you have fetched it, simply run and install as prompted.
 
 
diff --git a/docs/packages.txt b/docs/packages.txt
index f29fbe8c..e29112c0 100644
--- a/docs/packages.txt
+++ b/docs/packages.txt
@@ -136,23 +136,23 @@ are needed, and unloaded as they become unused.  In order to ensure the
 autonomous functioning of this process reference counting is the agreed upon 
 technique for managing loaded resources in Aethyra.  
 
-For those unfamiliar with the practice of reference counting, it involves 
+For those unfamiliar with the practice of reference counting, it involves
 every resource object having a variable containing the number of references to
 the object. When a reference is added the function addRef() is called and when
-it is removed the function release() is called. When the reference count 
-reaches zero the object will automatically delete itself, thus handling the 
+it is removed the function release() is called. When the reference count
+reaches zero the object will automatically delete itself, thus handling the
 cleanup of resources.
 
 Reference counting will form the core of the resource management system.  Each
 resource object will have the functionality of a reference counted object. The
-resource manager will hold ResourceEntry objects.  The resource entry object 
-contains a pointer to the resource as well as the location of the path of the 
+resource manager will hold ResourceEntry objects.  The resource entry object
+contains a pointer to the resource as well as the location of the path of the
 file the resource was loaded from.  This would look something like:
 
   /**
    * A generic reference counted resource object.
    */
-  class Resource { 
+  class Resource {
       public:
           /**
            * Loads the resource from the specified path.
@@ -165,17 +165,17 @@ file the resource was loaded from.  This would look something like:
            * Increments the reference counted of this object.
            */
           void addRef() { ++referenceCount; }
- 
+
           /**
            * Decrements the reference count and deletes the object
            * if no references are left.
            * @return <code>true</code> if the object was deleted
            * <code>false</code> otherwise.
            */
-          void release() { 
+          void release() {
               --referenceCount;
 
-              if(!referenceCount)
+              if (!referenceCount)
               {
                   delete this;
                   return true;
@@ -190,14 +190,14 @@ file the resource was loaded from.  This would look something like:
   /**
    * A resource entry descriptor.
    */
-  struct ResourceEntry { 
-      Resource*   resource; 
-      std::string filePath; 
+  struct ResourceEntry {
+      Resource*   resource;
+      std::string filePath;
   };
   ...
 
 The resource manager would then hold a mapping containing the resource entry as
-well as the string defining its resource identification path. The resource 
+well as the string defining its resource identification path. The resource
 manager would thus look something like this:
 
   /**