Update content of files

data/web/corefork.telegram.org/api/links.html

@@ -698,8 +698,7 @@ These links should be handled as follows:  </p>
 <pre><code>t.me/share?url=&lt;url&gt;
 t.me/share/url?url=&lt;url&gt;&amp;text=&lt;text&gt;</code></pre>
 <p><code>tg:</code> syntax:</p>
-<pre><code>tg://msg_url?url=&lt;url&gt;
-tg://msg_url?url=&lt;url&gt;&amp;text=&lt;text&gt;</code></pre>
+<pre><code>tg://msg_url?url=&lt;url&gt;&amp;text=&lt;text&gt;</code></pre>
 <p>Parameters:</p>
 <table class="table">
 <thead>
@@ -723,10 +722,10 @@ tg://msg_url?url=&lt;url&gt;&amp;text=&lt;text&gt;</code></pre>
 </tbody>
 </table>
 <h3><a class="anchor" href="#telegram-passport-links" id="telegram-passport-links" name="telegram-passport-links"><i class="anchor-icon"></i></a>Telegram Passport links</h3>
-<p><code>t.me</code> syntax:</p>
-<pre><code>t.me/passport?bot_id=&lt;bot_user_id&gt;&amp;scope=&lt;scope&gt;&amp;public_key=&lt;public_key&gt;&amp;nonce=&lt;nonce&gt;</code></pre>
+<p>See <a href="/docs/api/passport#uri-format">the Telegram documentation for parameters and usage »</a>.  </p>
 <p><code>tg:</code> syntax:</p>
-<pre><code>tg://resolve?domain=telegrampassport&amp;bot_id=&lt;bot_user_id&gt;&amp;scope=&lt;scope&gt;&amp;public_key=&lt;public_key&gt;&amp;nonce=&lt;nonce&gt;</code></pre>
+<pre><code>tg://passport?params
+tg://resolve?domain=telegrampassport&amp;params</code></pre>
 <h3><a class="anchor" href="#phone-confirmation-links" id="phone-confirmation-links" name="phone-confirmation-links"><i class="anchor-icon"></i></a>Phone confirmation links</h3>
 <p>Different from <a href="#login-code-links">login code links</a>.<br>
 These links are used to confirm ownership of the phone number, to prevent account deletion: see <a href="/api/account-deletion">the account deletion docs for more info on how to handle them »</a>.</p>

data/web/corefork.telegram.org/api/passport.html

@@ -348,8 +348,10 @@ Emails and phone numbers sent using telegram passport are <em>already verified</
 <h4><a class="anchor" href="#receiving-requests" id="receiving-requests" name="receiving-requests"><i class="anchor-icon"></i></a>Receiving requests</h4>
 <p>The process starts when your app receives an event from one of the <a href="/passport#sdk">SDKs</a>, or from a custom source.</p>
 <h4><a class="anchor" href="#uri-format" id="uri-format" name="uri-format"><i class="anchor-icon"></i></a>URI format</h4>
-<p>The SDKs trigger a passport authorization request by opening the following Telegram-specific URI:</p>
-<pre><code>tg://resolve?params</code></pre>
+<p>The SDKs trigger a passport authorization request by opening the following <a href="/api/links">deep links »</a>:</p>
+<p><code>tg:</code> syntax:</p>
+<pre><code>tg://passport?bot_id=&lt;bot_user_id&gt;&amp;scope=&lt;scope&gt;&amp;public_key=&lt;public_key&gt;&amp;nonce=&lt;nonce&gt;
+tg://resolve?domain=telegrampassport&amp;bot_id=&lt;bot_user_id&gt;&amp;scope=&lt;scope&gt;&amp;public_key=&lt;public_key&gt;&amp;nonce=&lt;nonce&gt;</code></pre>
 <p>With the following query string parameters:</p>
 <table class="table">
 <tbody>
@@ -357,41 +359,49 @@ Emails and phone numbers sent using telegram passport are <em>already verified</
 <td><strong>Parameters</strong></td>
 <td><strong>Type</strong></td>
 <td><strong>Required</strong></td>
+<td><strong>Description</strong></td>
 </tr>
 <tr>
 <td>domain</td>
 <td>String</td>
-<td>Yes</td>
+<td>Required only for <code>resolve</code> versions of the passport URI</td>
+<td>Always <code>telegrampassport</code> for Passport authorization requests.</td>
 </tr>
 <tr>
 <td>bot_id</td>
 <td>Integer</td>
 <td>Yes</td>
+<td>Unique identifier for the bot. You can get it from bot token. For example, for the bot token <code>1234567:4TT8bAc8GHUspu3ERYn-KGcvsvGB9u_n4ddy</code>, the bot id is <code>1234567</code>.</td>
 </tr>
 <tr>
 <td>scope</td>
 <td><a href="#uripassportscope">UriPassportScope</a></td>
 <td>Yes</td>
+<td>A more compact JSON-serialized object describing the data you want to request</td>
 </tr>
 <tr>
 <td>public_key</td>
 <td>String</td>
 <td>Yes</td>
+<td>Public key of the bot</td>
 </tr>
 <tr>
 <td>nonce</td>
 <td>String</td>
 <td>Yes</td>
+<td>Bot-specified nonce. <strong>Important:</strong> For security purposes it should be a cryptographically secure unique identifier of the request. In particular, it should be long enough and it should be generated using a cryptographically secure pseudorandom number generator. You should never accept credentials with the same nonce twice.</td>
 </tr>
 <tr>
 <td>callback_url</td>
 <td>String</td>
 <td>Optional</td>
+<td>Supported by some Telegram clients, specifies a callback URL to open once the process is finished or canceled.</td>
 </tr>
 <tr>
 <td>payload</td>
 <td>String</td>
 <td>Optional</td>
+<td><strong>Deprecated</strong> parameter from Telegram Passport 1.0 that had the same function of the <code>nonce</code> parameter.<br>Services that still use a legacy version of the SDK may provide this parameter instead of the <code>nonce</code>.<br>In some cases, both the <code>nonce</code> and the <code>payload</code> parameters may be found in a URI, for backwards compatibility: in this case, the <code>nonce</code> parameter should always be used instead of <code>payload</code>.</td>
 </tr>
 </tbody>
 </table>