diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html
index 659262fd04..6a953c1840 100644
--- a/data/web/corefork.telegram.org/api/forum.html
+++ b/data/web/corefork.telegram.org/api/forum.html
@@ -92,7 +92,7 @@ To fetch information about one or more topics by their ID, use message thread of the messageActionTopicCreate service message that created that topic.
This means that topics should be treated similarly to message threads by the client.
To send messages to these topics, pass the topic ID to the reply_msg_id
parameter of messages.sendMessage, messages.sendMedia et cetera.
-Replies to messages within a topic work as usual, however, since message threads can't have nested message threads, topics (except for the "General" topic) also can't have message threads (so replies to messages within topics won't generate further message threads).
reply_msg_id
, ignoring the topic ID), however, since message threads can't have nested message threads, topics (except for the "General" topic) also can't have message threads (so replies to messages within topics won't generate further message threads).
Topics have a name (title
) and an icon: the icon can be a custom emoji specified by the icon_emoji_id
, or a default chat icon if icon_emoji_id
is not set, filled with the color specified in icon_color
.
Topics can be temporarily closed
, preventing further messages from being sent to the topic.
Additionally, the "General" topic may also be hidden
.
diff --git a/data/web/corefork.telegram.org/constructor/dialog.html b/data/web/corefork.telegram.org/constructor/dialog.html
index 5f6b33d3b7..f4594503fb 100644
--- a/data/web/corefork.telegram.org/constructor/dialog.html
+++ b/data/web/corefork.telegram.org/constructor/dialog.html
@@ -129,7 +129,7 @@