Update ServerTests/basic_auth.php

Fixed a small spelling mistake on line 15
Fixed PUT requests issue
Removed synthesizers, added a demo of image decompression in background
Modernization
Fixed some warnings
Fixed background loading of images, by @merowing_
Dispatch async added to another call
Added retina display support
Fixed scaling call
Saving to cache happens on a background GCD queue, yay for performance, esp images
Cache directory name is now within a dispatch_once block
Minro fixes
Removed iOS 4 support, no fall backs, always use NSJSONSerialization
Added a not modified handler
Deprecated onCompletion:onError method in favour of addCompletionHandler:errorHandler: method
Updated readme
fix line breaks.

add and remove line breaks in front of documentation blocks for better readability.
Merge pull request #213 from yep/master

fix line breaks
From: http://stackoverflow.com/questions/4995254/nsmutablestring-as-retain-copy/5002646#5002646
The recommendation is to use copy for classes that are part of a class cluster that have mutable/immutable pairs; such as NSString/NSMutableString NSArray/NSMutableArray NSDictionary/NSMutableDictionary NSSet/NSMutableSet.
The reason for this is that it is possible to have a property that is declared as an immutable type (such as NSString) yet pass it a mutable type (such as NSMutableString). In which case it is possible to change the property from outside the class as Taskinoor describes.
Using copy is recommended, because it behaves sensibly with class clusters. sending copy to a mutable class returns an immutable copy of the object (i.e. sending a copy message to an NSMutableString returns an NSString). But, sending copy to an immutable counterpart is equivalent to sending it a retain message.
Merge pull request #215 from Hout/master

Use copy property attribute for immutable types