diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html
index 5a44971e8c..2f1c3cffc6 100644
--- a/data/corefork.telegram.org/api/config.html
+++ b/data/corefork.telegram.org/api/config.html
@@ -51,7 +51,7 @@
 <a href='/method/help.getConfig'>help.getConfig</a>#c4f9186b = <a href='/type/Config'>Config</a>;
 <a href='/method/help.getNearestDc'>help.getNearestDc</a>#1fb33026 = <a href='/type/NearestDc'>NearestDc</a>;</code></pre>
 <p>The huge <a href="/constructor/config">config</a> constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the <a href="/constructor/config">constructor page</a> for more information.</p>
-<h2><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a>Client configuration</h2>
+<h3><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a>Client configuration</h3>
 <pre><code><a href='/constructor/jsonObjectValue'>jsonObjectValue</a>#c0de1bd9 key:<a href='/type/string'>string</a> value:<a href='/type/JSONValue'>JSONValue</a> = <a href='/type/JSONObjectValue'>JSONObjectValue</a>;
 
 <a href='/constructor/jsonNull'>jsonNull</a>#3f6d7b68 = <a href='/type/JSONValue'>JSONValue</a>;
diff --git a/data/corefork.telegram.org/api/folders.html b/data/corefork.telegram.org/api/folders.html
index ef41365ad0..d046347576 100644
--- a/data/corefork.telegram.org/api/folders.html
+++ b/data/corefork.telegram.org/api/folders.html
@@ -60,7 +60,7 @@ In the API, folders are called "dialog filters"; in the UI, they are typically r
 <a href='/method/messages.updateDialogFiltersOrder'>messages.updateDialogFiltersOrder</a>#c563c1e4 order:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/int'>int</a>&gt; = <a href='/type/Bool'>Bool</a>;
 
 <a href='/method/help.getAppConfig'>help.getAppConfig</a>#98914110 = <a href='/type/JSONValue'>JSONValue</a>;</code></pre>
-<h2><a class="anchor" href="#folders" id="folders" name="folders"><i class="anchor-icon"></i></a>Folders</h2>
+<h3><a class="anchor" href="#folders" id="folders" name="folders"><i class="anchor-icon"></i></a>Folders</h3>
 <p>On startup, clients call:  </p>
 <ul>
 <li><a href="/method/messages.getDialogFilters">messages.getDialogFilters</a> to fetch a list of previously configured folders.</li>
@@ -76,7 +76,7 @@ Folders can also have unlimited pinned chats, as determined by the <code>pinned_
 <p>To delete folders, use <a href="/method/messages.updateDialogFilter">messages.updateDialogFilter</a> without populating the <code>filter</code> flag field.  </p>
 <p>Clients can receive <a href="/constructor/updateDialogFilter">updateDialogFilter</a>, <a href="/constructor/updateDialogFilterOrder">updateDialogFilterOrder</a> updates with new filter information, generated by other clients when modifying folder info.<br>
 Clients can also receive <a href="/constructor/updateDialogFilters">updateDialogFilters</a>, in which case folder info should be refetched manually using <a href="/method/messages.getDialogFilters">messages.getDialogFilters</a>.</p>
-<h2><a class="anchor" href="#peer-folders" id="peer-folders" name="peer-folders"><i class="anchor-icon"></i></a>Peer folders</h2>
+<h3><a class="anchor" href="#peer-folders" id="peer-folders" name="peer-folders"><i class="anchor-icon"></i></a>Peer folders</h3>
 <p>The API also has another method for identifying groups of peers, typically used only by archived chats.</p>
 <p>Scheme:</p>
 <pre><code><a href='/constructor/inputDialogPeer'>inputDialogPeer</a>#fcaafeb7 peer:<a href='/type/InputPeer'>InputPeer</a> = <a href='/type/InputDialogPeer'>InputDialogPeer</a>;
diff --git a/data/corefork.telegram.org/api/layers.html b/data/corefork.telegram.org/api/layers.html
index b7778cefb0..93599a9f9c 100644
--- a/data/corefork.telegram.org/api/layers.html
+++ b/data/corefork.telegram.org/api/layers.html
@@ -760,7 +760,7 @@ Layer…">
 <li>Added <a href="/method/messages.getChatInviteImporters">messages.getChatInviteImporters</a> - Get info about the users that joined the chat using a specific chat invite</li>
 <li>Added <a href="/method/messages.setHistoryTTL">messages.setHistoryTTL</a> - Set maximum Time-To-Live of all messages in the specified chat</li>
 <li>Added <a href="/method/account.reportProfilePhoto">account.reportProfilePhoto</a> - Report a profile photo of a dialog</li>
-<li>Added <a href="/method/channels.convertToGigagroup">channels.convertToGigagroup</a> - Convert a <a href="/api/channel">supergroup</a> to a <a href="/api/channel">gigagroup</a></li>
+<li>Added <a href="/method/channels.convertToGigagroup">channels.convertToGigagroup</a> - Convert a <a href="/api/channel">supergroup</a> to a <a href="/api/channel">gigagroup</a>, when requested by <a href="/api/config#channel-suggestions">channel suggestions</a>.</li>
 <li>Added <a href="/method/messages.checkHistoryImportPeer">messages.checkHistoryImportPeer</a> - Check whether chat history exported from another chat app can be imported into a specific Telegram chat.</li>
 </ul>
 <h5><a class="anchor" href="#changed-methods" id="changed-methods" name="changed-methods"><i class="anchor-icon"></i></a>Changed Methods</h5>
diff --git a/data/corefork.telegram.org/method/channels.convertToGigagroup b/data/corefork.telegram.org/method/channels.convertToGigagroup
index c63a545d76..174fc28465 100644
--- a/data/corefork.telegram.org/method/channels.convertToGigagroup
+++ b/data/corefork.telegram.org/method/channels.convertToGigagroup
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>channels.convertToGigagroup</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Convert a supergroup to a gigagroup">
+    <meta property="description" content="Convert a supergroup to a gigagroup, when requested by channel suggestions.">
     <meta property="og:title" content="channels.convertToGigagroup">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Convert a supergroup to a gigagroup">
+    <meta property="og:description" content="Convert a supergroup to a gigagroup, when requested by channel suggestions.">
     <link rel="shortcut icon" href="/favicon.ico?4" type="image/x-icon" />
 
     <link href="/css/bootstrap.min.css?3" rel="stylesheet">
@@ -39,7 +39,7 @@
   <div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a  href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/methods" >All Methods</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/method/channels.convertToGigaGroup" >channels.convertToGigagroup</a></li></ul></div>
   <h1 id="dev_page_title">channels.convertToGigagroup</h1>
   
-  <div id="dev_page_content"><p>Convert a <a href="/api/channel">supergroup</a> to a <a href="/api/channel">gigagroup</a></p>
+  <div id="dev_page_content"><p>Convert a <a href="/api/channel">supergroup</a> to a <a href="/api/channel">gigagroup</a>, when requested by <a href="/api/config#channel-suggestions">channel suggestions</a>.</p>
 <p>{scheme}</p>
 <h3><a class="anchor" href="#parameters" id="parameters" name="parameters"><i class="anchor-icon"></i></a>Parameters</h3>
 <table class="table">
@@ -62,7 +62,9 @@
 <p><a href="/type/Updates">Updates</a></p>
 <h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
 <h4><a class="anchor" href="#channels" id="channels" name="channels"><i class="anchor-icon"></i></a><a href="/api/channel">Channels</a></h4>
-<p>How to handle channels, supergroups, groups, and what's the difference between them.</p></div>
+<p>How to handle channels, supergroups, groups, and what's the difference between them.</p>
+<h4><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a><a href="/api/config">Client configuration</a></h4>
+<p>The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.</p></div>
   
 </div>
           
diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html
index 351f3d88b5..c309db3af8 100644
--- a/data/corefork.telegram.org/methods.html
+++ b/data/corefork.telegram.org/methods.html
@@ -748,7 +748,7 @@
 </tr>
 <tr>
 <td><a href="/method/channels.convertToGigagroup">channels.convertToGigagroup</a></td>
-<td>Convert a <a href="/api/channel">supergroup</a> to a <a href="/api/channel">gigagroup</a></td>
+<td>Convert a <a href="/api/channel">supergroup</a> to a <a href="/api/channel">gigagroup</a>, when requested by <a href="/api/config#channel-suggestions">channel suggestions</a>.</td>
 </tr>
 </tbody>
 </table>