diff --git a/data/web/corefork.telegram.org/constructor/forumTopic.html b/data/web/corefork.telegram.org/constructor/forumTopic.html
index 033c2f5d7e..80e37a95a8 100644
--- a/data/web/corefork.telegram.org/constructor/forumTopic.html
+++ b/data/web/corefork.telegram.org/constructor/forumTopic.html
@@ -89,7 +89,7 @@
 <tr>
 <td><strong>short</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.5?<a href="/constructor/true">true</a></td>
-<td> </td>
+<td>Whether this constructor is a reduced version of the full topic information. <br>If set, only the <code>my</code>, <code>closed</code>, <code>id</code>, <code>date</code>, <code>title</code>, <code>icon_color</code>, <code>icon_emoji_id</code> and <code>from_id</code> parameters will contain valid information. <br>Reduced info is usually only returned in topic-related <a href="/api/recent-actions">admin log events »</a> and in the <a href="/constructor/messages.channelMessages">messages.channelMessages</a> constructor: if needed, full information can be fetched using <a href="/method/channels.getForumTopicsByID">channels.getForumTopicsByID</a>.</td>
 </tr>
 <tr>
 <td><strong>hidden</strong></td>
diff --git a/data/web/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html b/data/web/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html
index 59e9fbbab3..b558ed2021 100644
--- a/data/web/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html
+++ b/data/web/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html
@@ -79,7 +79,7 @@
 <tr>
 <td><strong>auto_setting_from</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.0?<a href="/type/long">long</a></td>
-<td>If set, notifies the participants of the chat that the user ID specified in <code>auto_setting_from</code> has changed their <a href="/method/messages.setDefaultHistoryTTL">default TTL settings »</a>. The service message will be automatically emitted <em>before</em> the first message sent by the user <code>auto_setting_from</code> in the current chat, after changing the default TTL settings.</td>
+<td>If set, the chat TTL setting was set not due to a manual change by one of participants, but automatically because one of the participants has the <a href="/method/messages.setDefaultHistoryTTL">default TTL settings enabled »</a>. For example, when a user writes to us for the first time and we have set a default messages TTL of 1 week, this service message (with <code>auto_setting_from=our_userid</code>) will be emitted before our first message.</td>
 </tr>
 </tbody>
 </table>