diff --git a/Classes/BITAuthenticator.h b/Classes/BITAuthenticator.h
index ab8c721a16..c14cf9bd7c 100644
--- a/Classes/BITAuthenticator.h
+++ b/Classes/BITAuthenticator.h
@@ -328,6 +328,9 @@ typedef NS_ENUM(NSUInteger, BITAuthenticatorAppRestrictionEnforcementFrequency)
 /**
  * Returns YES if this app is identified according to the setting in `identificationType`.
  *
+ * Since the identification process is done asynchronously (contacting the server),
+ * you need to observe the value change via KVO.
+ *
  * @see identificationType
  */
 @property (nonatomic, assign, readonly, getter = isIdentified) BOOL identified;
diff --git a/docs/HowTo-Authenticating-Users-on-iOS-template.md b/docs/HowTo-Authenticating-Users-on-iOS-template.md
index 90533d4da4..d3eece6de0 100644
--- a/docs/HowTo-Authenticating-Users-on-iOS-template.md
+++ b/docs/HowTo-Authenticating-Users-on-iOS-template.md
@@ -217,4 +217,4 @@ As an alternative, you can implement your own workflow with following two method
 
 2. Validate that the user is still a tester, member, or developer of your app. This will show an alert and a modal view only if the user could not be validated. Otherwise, the process will succeed without showing a message or view:
 
-        - (void) validateWithCompletion:(void(^)(BOOL validated, NSError *error)) completion;
\ No newline at end of file
+        - (void) validateWithCompletion:(void(^)(BOOL validated, NSError *error)) completion;