Update content of files

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

@@ -266,7 +266,7 @@ While <a href="/method/help.getConfig">help.getConfig</a> returns MTProto-specif
 <h4><a class="anchor" href="#emojies-send-dice-success" id="emojies-send-dice-success" name="emojies-send-dice-success"><i class="anchor-icon"></i></a><code>emojies_send_dice_success</code></h4>
 <p>For <a href="/api/dice">animated dice</a> emojis other than the basic <img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB2.png" width="20" height="20" alt="🎲" />, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks <img class="emoji" src="//telegram.org/img/emoji/40/F09F8E86.png" width="20" height="20" alt="🎆" /> (object with emoji keys and object values, containing <code>value</code> and <code>frame_start</code> float values)</p>
 <h4><a class="anchor" href="#emojies-sounds" id="emojies-sounds" name="emojies-sounds"><i class="anchor-icon"></i></a><code>emojies_sounds</code></h4>
-<p>A map of soundbites to be played when the user clicks on the specified <a href="/api/animated-emojis">animated emoji</a>; the <a href="/api/file_reference">file reference field</a> should be base64-decoded before <a href="/api/files">downloading the file</a> (map of <a href="/api/files">file IDs</a>, with emoji string keys)</p>
+<p>A map of soundbites to be played when the user clicks on the specified <a href="/api/animated-emojis">animated emoji</a>; the <a href="/api/file_reference">file reference field</a> should be base64-decoded before <a href="/api/files">downloading the file</a> (map of <a href="/api/files">file IDs</a> (<a href="/constructor/inputDocument">inputDocument</a>.id), with emoji string keys)</p>
 <h4><a class="anchor" href="#gif-search-branding" id="gif-search-branding" name="gif-search-branding"><i class="anchor-icon"></i></a><code>gif_search_branding</code></h4>
 <p>Specifies the name of the service providing GIF search through <a href="#mtproto-configuration">gif_search_username</a> (string)</p>
 <h4><a class="anchor" href="#gif-search-emojies" id="gif-search-emojies" name="gif-search-emojies"><i class="anchor-icon"></i></a><code>gif_search_emojies</code></h4>

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

@@ -107,7 +107,7 @@
 </tr>
 </tbody>
 </table>
-<p>Note that <a href="#message-links">chat invite links</a> have the same syntax, but <code>&lt;phone_number&gt;</code> is not a valid phone number.  </p>
+<p>Note that <a href="#message-links">chat invite links</a> have the same syntax, but <code>&lt;phone_number&gt;</code> won't be a valid phone number.  </p>
 <h3><a class="anchor" href="#chat-invite-links" id="chat-invite-links" name="chat-invite-links"><i class="anchor-icon"></i></a>Chat invite links</h3>
 <p>Used to invite users to private groups and channels, see <a href="/api/invites#invite-links">here for more info on how to generate such links »</a>.  </p>
 <p><code>t.me</code> syntax:</p>
@@ -229,7 +229,7 @@ t.me/share/url?url=&lt;url&gt;&amp;text=&lt;text&gt;</code></pre>
 <h3><a class="anchor" href="#video-chatlivestream-links" id="video-chatlivestream-links" name="video-chatlivestream-links"><i class="anchor-icon"></i></a>Video chat/Livestream links</h3>
 <p>Used to join video/voice chats in groups, and livestreams in channels.<br>
 Such links are generated using <a href="/method/phone.exportGroupCallInvite">phone.exportGroupCallInvite</a>.<br>
-Note that <code>voicechat</code> links are deprecated, the API will always export <code>videochat</code> links even for voice chats, clients should support parsing the old link format only for backwards compatibility.  </p>
+Note that <code>voicechat</code> links are deprecated, the API will always export <code>videochat</code> links for video and voice chats in groups, clients should support parsing the old link format only for backwards compatibility.  </p>
 <p><code>t.me</code> syntax:</p>
 <pre><code>t.me/&lt;username&gt;?videochat
 t.me/&lt;username&gt;?videochat=&lt;invite_hash&gt;

data/web/corefork.telegram.org/api/web-events.html

@@ -179,11 +179,11 @@ The GamingCommunication and bot web apps libraries by default will use <code>'*'
 Credit card details will be handled only by the payment system, see the <a href="/api/payments">payment documentation for more info »</a>.  </p>
 <h4><a class="anchor" href="#share-score" id="share-score" name="share-score"><i class="anchor-icon"></i></a><code>share_score</code></h4>
 <p>No event payload.</p>
-<p>Will be called by games when the user explicitly clicks on the <strong>share score</strong> button to share the game, along with his score.<br>
+<p>Will be called by games when the user explicitly clicks on the <strong>share score</strong> button to share the game, along with their score.<br>
 Typically done by using <a href="/method/messages.forwardMessages">messages.forwardMessages</a> on the game message with the <code>with_my_score</code> flag.  </p>
 <h4><a class="anchor" href="#share-game" id="share-game" name="share-game"><i class="anchor-icon"></i></a><code>share_game</code></h4>
 <p>No event payload.</p>
-<p>Will be called by games when the user explicitly clicks on the <strong>share game</strong> button to share the game, without sharing his score.<br>
+<p>Will be called by games when the user explicitly clicks on the <strong>share game</strong> button to share the game, without sharing their score.<br>
 Typically done by using <a href="/method/messages.forwardMessages">messages.forwardMessages</a> on the game message without the <code>with_my_score</code> flag, or by sharing the game's <a href="/api/links#game-links">deep link</a>.</p>
 <h4><a class="anchor" href="#game-over" id="game-over" name="game-over"><i class="anchor-icon"></i></a><code>game_over</code></h4>
 <p>No event payload.</p>