Update content of files

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

@@ -131,7 +131,7 @@ After the entire file is successfully saved, the final method may be called and
 <p>Use <a href="/method/messages.editMessage">messages.editMessage</a> to edit or replace a media file sent using <a href="/method/messages.sendMedia">messages.sendMedia</a> and <a href="/method/messages.sendMultiMedia">messages.sendMultiMedia</a>.  </p>
 <p>If one wishes to edit only the <code>spoiler</code>, <code>ttl_seconds</code> or <code>query</code> attributes of the media, this may be done without reuploading the entire media file, by simply passing the old media to the <code>id</code> parameter of <a href="/constructor/inputMediaPhoto">inputMediaPhoto</a>, <a href="/constructor/inputMediaDocument">inputMediaDocument</a> and updating the values of the <code>spoiler</code>/<code>ttl_seconds</code>/<code>query</code> attributes as needed.  </p>
 <p>If one wishes to edit any other attribute (for example, the file name specified in <a href="/constructor/documentAttributeFilename">documentAttributeFilename</a>, any other <a href="/type/DocumentAttribute">DocumentAttribute</a> or any flag different from <code>spoiler</code>/<code>ttl_seconds</code>/<code>query</code>) <strong>a full reupload of the file is required</strong>, in order to be able to specify the new attributes in <a href="/constructor/inputMediaUploadedPhoto">inputMediaUploadedPhoto</a>/<a href="/constructor/inputMediaUploadedDocument">inputMediaUploadedDocument</a>.  </p>
-<p>The only exception to this rule is when editing the <a href="/constructor/documentAttributeVideo">documentAttributeVideo</a>.<code>video_start_ts</code> attribute of video <a href="/api/stories">stories</a>, in which case <a href="/method/inputMediaDocument">inputMediaDocument</a> may still be used with <a href="/constructor/inputFileStoryDocument">inputFileStoryDocument</a> instead of <a href="/constructor/inputFile">inputFile</a> without reuploading the entire story video, see <a href="/api/stories#editing-stories">here »</a> for more info on the full flow.</p>
+<p>The only exception to this rule is when editing the <a href="/constructor/documentAttributeVideo">documentAttributeVideo</a>.<code>video_start_ts</code> attribute of video <a href="/api/stories">stories</a>, in which case <a href="/constructor/inputMediaDocument">inputMediaDocument</a> may still be used with <a href="/constructor/inputFileStoryDocument">inputFileStoryDocument</a> instead of <a href="/constructor/inputFile">inputFile</a> without reuploading the entire story video, see <a href="/api/stories#editing-stories">here »</a> for more info on the full flow.</p>
 <h4><a class="anchor" href="#streamed-uploads" id="streamed-uploads" name="streamed-uploads"><i class="anchor-icon"></i></a>Streamed uploads</h4>
 <p>The API also supports streamed uploads, in cases where the length of the file is not known before starting the upload.  </p>
 <p>This is useful for example when converting a video, to avoid buffering the entire converted video on the filesystem, each part is uploaded immediately as soon as it is produced by the encoder.  </p>

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

@@ -86,7 +86,7 @@ Note that if any of the conditions changes in the period between the call to <a
 <p>The parameters of <a href="/method/stories.sendStory">stories.sendStory</a> are fully described on the <a href="/method/stories.sendStory">method page »</a>, here are some of the most important ones:</p>
 <ul>
 <li><code>peer</code>: The peer to send the story as.</li>
-<li><code>media</code>:  The story media.</li>
+<li><code>media</code>:  The story media (a vertical photo or a vertical video, max 30 MB).</li>
 <li><code>media_areas</code>: <a href="/api/stories#media-areas">Media areas</a> associated to the story, see <a href="/api/stories#media-areas">here »</a> for more info.</li>
 <li><code>privacy_rules</code>: A set of <a href="/api/privacy#privacy-rules">privacy rules »</a> for the story as an array of <a href="/type/InputPrivacyRule">InputPrivacyRule</a> constructors, indicating who can or can't view the story.</li>
 <li><code>expire</code>: Period after which the story is moved to <a href="#pinned-or-archived-stories">archive</a> (and <a href="#pinned-or-archived-stories">to the profile</a> if <code>pinned</code> is set), in seconds; must be one of <code>6 * 3600</code>, <code>12 * 3600</code>, <code>86400</code>, or <code>2 * 86400</code> for Telegram Premium users, and <code>86400</code> otherwise.</li>