Polish Core Data class documentation

CoconutKit/Sources/CoreData/HLSManagedObjectCopying.h

@@ -9,7 +9,7 @@
 /**
  * NSManagedObject does not implement the NSCopying protocol. Instead, you can have your managed objects
  * implement the HLSManagedObjectCopying protocol. Objects implementing this protocol can be copied
- * (within a single context) using the HLSModelManager copyObject: method. Refer to the documentation
+ * (within a single context) using the HLSModelManager -copyObject: method. Refer to the documentation
  * of this method for the copy behavior which is applied
  */
 @protocol HLSManagedObjectCopying <NSObject>

CoconutKit/Sources/CoreData/NSManagedObject+HLSExtensions.h

@@ -79,7 +79,7 @@
  *     or more objects also implementing the HLSManagedObjectCopying protocol (ownership is assumed when the relationship
  *     deletion behavior is set to cascade)
  *
- * After the method successfully returns an object, you must still commit the changes by calling save: on the
+ * After the method successfully returns an object, you must still commit the changes by calling -save: on the
  * managed object context in which it was created.
  */
 - (id)duplicate;

CoconutKit/Sources/CoreData/NSManagedObject+HLSValidation.h

@@ -63,8 +63,8 @@
  *   - similarly, instead of implementing the -validateForDelete: method to perform checks when deleting
  *     an object, you now must implement a 'check' method with the following signature:
  *         - (BOOL)checkForDelete:(NSError **)pError
- * UITextField leverage this new set of validation methods by providing binding witg and model object fields. 
- * This makes synchronization and validation of forms very easy to implement. Refer to UITextField+HLSValidation.h
+ * UITextField leverage this new set of validation methods by providing binding with model object fields. This 
+ * makes synchronization and validation of forms very easy to implement. Refer to UITextField+HLSValidation.h
  * for more information.
  *
  * When validation has been performed and failed, errors are returned. There are only two cases to consider:
@@ -75,7 +75,7 @@
  *      storing the array of errors which have been generated.
  *
  * Core Data lets you implement validation logic both using the Core Data model editor and / or by implementing
- * validation methods, as described above. I you define validations both in the xcdatamodel file as well as in 
+ * validation methods, as described above. If you define validations both in the xcdatamodel file as well as in 
  * code, the errors generated by the xcdatamodel validation logic will always be combined with those generated 
  * by the manually implemented validations (as an NSValidationMultipleErrorsError) by Core Data. In general, 
  * though, I strongly suggest implementing validations for all fields using one of the following rules exclusively:
@@ -124,7 +124,7 @@
 - (BOOL)checkForConsistency:(NSError **)pError;
 
 /**
- * Same as checkForConsistency: (see above), but when an object deletion is committed
+ * Same as -checkForConsistency: (see above), but when an object deletion is committed
  */
 - (BOOL)checkForDelete:(NSError **)pError;