@@ -18,6 +18,52 @@ Your extension name (defined in [pxt.json](./pxt-json.md)) must adhere to the fo
 
 In other words, it should match the following regex: `^[a-z][a-z0-9\-_]+`.
 
+### ~ reminder
+
+#### Headings in the Extensions Gallery info pages
+
+To display the information page for an extension (when you click `Learn more` on an extension card in the Extensions Gallery) the Editor will inject portions of the `README.md` file from the extension's repository. A new top-level heading (`h1`), in addition to the one from the `README.md`, is generated for this page. The new heading might contain something like `theowner/pxt-laser-ray 1.2.3`, depending on the repository, owner, and version.
+
+The rendering process for the extension's information page will attempt to remove the original `h1` element that came from `README.md` in order to avoid name duplication in the page headings. This is done by looking for the heading from the `README.md` that contains the `name` entry from the `pxt.json` in the repository. If found, that heading is removed. However, if the heading from the `README.md` doesn't match the `name` from `pxt.json`, then that `h1` heading isn't removed and it will also display in the extension information page.
+
+If `pxt.json` file contains:
+
+```
+"name": "pxt-laser-ray",
+"version": "1.2.3",
+"description": "Generate light effects to simulate laser rays."
+```
+
+...but the `README.md` contains:
+
+```
+# Cool Laser Ray
+
+This extension contains blocks to create laser ray effects.
+
+...
+```
+
+...instead of:
+
+```
+# pxt-laser-ray
+
+This extension contains blocks to create laser ray effects.
+
+...
+```
+
+...then the information page will contain both:
+
+`<h1>theowner/pxt-laser-ray 1.2.3</h1>`
+
+and
+
+`<h1>Cool Laser Ray</h1>`
+
+### ~
+
 ## TypeScript conventions
 
 MakeCode follows the usual TypeScript naming conventions.