diff --git a/.github/dev.yml b/.github/dev.yml
index f9d623c..cd48873 100644
--- a/.github/dev.yml
+++ b/.github/dev.yml
@@ -2,7 +2,7 @@ pr: none
 trigger:
 - master
 
-name: 2.1.2-dev.$(Rev:r)
+name: 2.1.3-dev.$(Rev:r)
 
 pool:
   vmImage: ubuntu-latest
diff --git a/README.md b/README.md
index 3b41ea4..f04fdb8 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,10 @@ Those api hash/id represent your application and one can be used for handling ma
 
 Then it will attempt to sign-in *(login)* as a user for which you must enter the **phone_number** and the **verification_code** that will be sent to this user (for example through SMS or another Telegram client app the user is connected to).
 
-If the verification succeeds but the phone number is unknown to Telegram, the user might be prompted to sign-up *(register their account by accepting the Terms of Service)* and provide their **first_name** and **last_name**.
+If the verification succeeds but the phone number is unknown to Telegram, the user might be prompted to sign-up
+*(register their account by accepting the Terms of Service)* and provide their **first_name** and **last_name**.  
+If the account already exists and has enabled two-step verification (2FA) a **password** might be required.  
+All these login scenarios are handled automatically within the call to `LoginUserIfNeeded`.
 
 And that's it, you now have access to the **[full range of Telegram Client APIs](https://corefork.telegram.org/methods)**. 
 All those API methods are available *(with an underscore in the method name, instead of a dot)*, like this: `await client.Method_Name(...)`