diff --git a/content/posts/spoiler-element.md b/content/posts/spoiler-element.md
index e1872f9..3c4adb1 100644
--- a/content/posts/spoiler-element.md
+++ b/content/posts/spoiler-element.md
@@ -83,7 +83,7 @@ An image marked sensitive on Firefish (a Fediverse server) shows a blurred place
{{}}{{}}
-More special syntax for spoilers:[^2]
+More special syntax for spoilers:
{{}}
@@ -95,6 +95,8 @@ More special syntax for spoilers:[^2]
{{}}
+[BBCode](https://www.bbcode.org/posting-a-spoiler-with-bbcode.php) is the oldest example of dedicated spoiler syntax I know of.
+
@@ -221,8 +223,6 @@ Thanks to {{}}Matrix Specification Client-Server API, section 11.2.2.6: “Spoiler messages”{{}} specifies the spoiler syntax, semantics, and recommended client behavior.
-[^2]: [BBCode](https://www.bbcode.org/posting-a-spoiler-with-bbcode.php) is the oldest example of dedicated spoiler syntax I know of.
-
[^3]: Note that `summary` was originally specified as a block-level button, not an inline element. This may require changes to the definition of `summary`. I don't believe that the changes should significantly impact conformant pages, but non-conforming pages that incorrectly use `summary` elements without the required `details` parent may be impacted. Perhaps we really do need a new element for spoiler summaries.
[^4]: I came up with the idea of this attribute when I was browsing some Wikipedia articles on medical topics and ended up on the article for "maggot therapy". I had uBlock Origin configured to make large media click-to-load, and the figure captions told me which ones would be safe to load when others were in the room. However, [figure captions aren't a replacement for alt-text]({{}}).