From efc225b22914bc9bd22bf1899a9e1fa1f5714970 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Tue, 15 Oct 2024 09:15:42 +0000 Subject: [PATCH] Update content of files --- data/web/core.telegram.org/gateway/verification-tutorial.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/web/core.telegram.org/gateway/verification-tutorial.html b/data/web/core.telegram.org/gateway/verification-tutorial.html index 74be36f426..61194f8665 100644 --- a/data/web/core.telegram.org/gateway/verification-tutorial.html +++ b/data/web/core.telegram.org/gateway/verification-tutorial.html @@ -141,7 +141,7 @@ if result: request_id = result.get('request_id') print(f"Request ID: {request_id}")
-

If the method indicates that the user can be contacted, you will be automatically charged in advance for the price of a message regardless of whether you eventually send one. If the method returns an error (e.g., because the user cannot receive codes), you will not be charged.

+

You will be automatically charged in advance for the price of one message if the method indicates that the user can be contacted – regardless of whether you eventually send one. If the method returns an error (e.g., because the user cannot receive codes), you will not be charged.

If the check succeeds and you ultimately decide to send a message, use the request_id returned by the checkSendAbility method to avoid paying the message fee again.

Revoking Codes