Merge pull request steipete#22 from ryanworl/master

Fixed typos in README and Aspects.m

Aspects.h

@@ -55,15 +55,15 @@ typedef NS_OPTIONS(NSUInteger, AspectOptions) {
 /// @note Hooking static methods is not supported.
 /// @return A token which allows to later deregister the aspect.
 + (id<AspectToken>)aspect_hookSelector:(SEL)selector
-                      withOptions:(AspectOptions)options
-                       usingBlock:(id)block
-                            error:(NSError **)error;
+                           withOptions:(AspectOptions)options
+                            usingBlock:(id)block
+                                 error:(NSError **)error;
 
 /// Adds a block of code before/instead/after the current `selector` for a specific instance.
 - (id<AspectToken>)aspect_hookSelector:(SEL)selector
-                      withOptions:(AspectOptions)options
-                       usingBlock:(id)block
-                            error:(NSError **)error;
+                           withOptions:(AspectOptions)options
+                            usingBlock:(id)block
+                                 error:(NSError **)error;
 
 @end
 

Aspects.m

@@ -217,7 +217,7 @@ static BOOL aspect_isCompatibleBlockSignature(NSMethodSignature *blockSignature,
     }
 
     if (!signaturesMatch) {
-        NSString *description = [NSString stringWithFormat:@"Blog signature %@ doesn't match %@.", blockSignature, methodSignature];
+        NSString *description = [NSString stringWithFormat:@"Block signature %@ doesn't match %@.", blockSignature, methodSignature];
         AspectError(AspectErrorIncompatibleBlockSignature, description);
         return NO;
     }

README.md

@@ -47,7 +47,7 @@ When to use Aspects
 Aspect-oriented programming (AOP) is used to encapsulate "cross-cutting" concerns. These are the kind of requirements that *cut-accross* many modules in your system, and so cannot be encapsulated using normal Object Oriented programming. Some examples of these kinds of requirements: 
 
 * *Whenever* a user invokes a method on the service client, security should be checked. 
-* *Whenever* a useer interacts with the store, a genius suggestion should be presented, based on their interaction. 
+* *Whenever* a user interacts with the store, a genius suggestion should be presented, based on their interaction. 
 * *All* calls should be logged. 
 
 If we implemented the above requirements using regular OO there'd be some drawbacks: