diff --git a/FAQ.md b/FAQ.md
index 0e830a8..509a7e3 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -163,8 +163,9 @@ or simply use a debugger: Place a breakpoint after the Messages_GetAllChats call
 
 Here is a list of common issues and how to fix them so that your program work correctly:
 1) Are you using the Nuget package or the library source code?  
-It is not recommended to copy/compile the source code of the library for a normal usage.  
-When built in DEBUG mode, the source code connects to Telegram test servers. So you can either:
+It is not recommended to copy/compile the source code of the library for a normal usage.
+When built in DEBUG mode, the source code connects to Telegram test servers (see also [FAQ #6](#wrong-server)).  
+So you can either:
     - **Recommended:** Use the [official Nuget package](https://www.nuget.org/packages/WTelegramClient) or the [private nuget feed of development builds](https://dev.azure.com/wiz0u/WTelegramClient/_packaging?_a=package&feed=WTelegramClient&package=WTelegramClient&protocolType=NuGet)
     - Build your code in RELEASE mode
     - Modify your config callback to reply to "server_address" with the IP address of Telegram production servers (as found on your API development tools)
diff --git a/README.md b/README.md
index 9910be7..e81ef42 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,8 @@ Then it will attempt to sign-in as a user for which you must enter the **phone_n
 
 If the verification succeeds but the phone number is unknown to Telegram, the user might be prompted to sign-up (accepting the Terms of Service) and enter their **first_name** and **last_name**.
 
-And that's it, you now have access to the [full range of Telegram services](https://corefork.telegram.org/methods), mainly through calls to `await client.Some_TL_Method(...)`
+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(...)`
 
 # Saved session
 If you run this program again, you will notice that only **api_id** and **api_hash** are requested, the other prompts are gone and you are automatically logged-on and ready to go.