diff --git a/html/rakudoc.html b/html/rakudoc.html
index 397e9c3..2736126 100644
--- a/html/rakudoc.html
+++ b/html/rakudoc.html
@@ -5,22 +5,22 @@
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <title>RakuDoc</title>
 <link rel="icon" href="https://irclogs.raku.org/favicon.ico">
-<style>span.basis{font-weight:800}span.important{font-style:italic}span.unusual{text-decoration:underline}span.code{font-weight:500;background-color:linen;display:inline-block;margin:2px;padding:2px}span.overstrike{text-decoration:line-through}span.high{vertical-align:super}span.junior{vertical-align:sub}span.replace{font-style:small-caps;text-shadow:-1px 1px}span.indexed{text-shadow:1px 1px orange}span.indexed:hover::before{content:attr(data-index-text);translate:0 -1.5em;position:absolute;opacity:75%;background-color:#40e0d0;color:indigo}span.keyboard{text-shadow:1px 1px}span.terminal{text-decoration:overline underline}span.footnote{vertical-align:super}span.developer-version{display:none;color:red}span.developer-version span.developer-note{font-family:"Brush Script MT",cursive}span.developer-version:hover{display:inline-block;transform:translate(50px, 100px);z-index:5}span.bad-markdown{text-shadow:1px 1px red}pre.code-block{background-color:#eee;margin:1rem;padding:0 1rem 1rem 1rem}pre.input-block{background-color:#eee;margin:1rem;padding:0 1rem 1rem 1rem}pre.input-block::before{content:"--- input ---";display:block;text-shadow:-2px -2px 4px #000;color:#fff;padding-bottom:1rem}pre.output-block{background-color:#eee;margin:1rem;padding:0 1rem 1rem 1rem}pre.output-block::before{content:"--- output ---";display:block;text-shadow:2px 2px 4px #000;color:#fff;padding-bottom:1rem}div.defn-text{margin-left:1rem}div.defn-term{font-weight:bold;font-style:italic}div.id-target{display:none}div.nested{margin-left:5rem}div.toc .toc-item{margin-left:calc(var(--level)*1rem)}div.toc .toc-item::before{content:attr(data-bullet)}div.toc .toc-item a{padding-left:.4rem}div.index-section{margin-left:calc((var(--level) - 1)*1rem)}div.index-section[data-index-level="1"]{text-shadow:1px 1px orange}div.index-section>a.index-ref{white-space:nowrap;display:inline-block;width:1em}div.index-section>a.index-ref+span{display:none;width:0}div.index-section>a.index-ref:hover+span{display:inline-block;position:absolute;width:auto;z-index:5;background-color:#fff5ee}span.developer-note{display:none;width:0;color:blue;text-shadow:2px 2px 5px green}span.developer-version{display:none;width:0;color:red;text-shadow:2px 2px 5px green}.delta::before,span.developer-text::before{content:"ℹ";vertical-align:super}.delta:hover .developer-version,span.developer-text:hover .developer-version{display:inline-block;position:absolute;width:100%;z-index:5;transform:translate(0.5rem, -1rem)}.delta:hover .developer-note,span.developer-text:hover .developer-note{display:inline-block;position:absolute;width:auto;z-index:5;margin-left:1rem}span.developer-text:hover{text-decoration:overline}div.footer{border-top:2px dashed;margin:1rem 0;padding:2rem}div.footer .footer-field{display:inline-block}div.footer .footer-line{display:block}.heading>a{color:maroon;text-decoration:none}h.title{font-size:larger}table,th,td{border:1px solid;border-collapse:collapse}tbody.procedural tr.procedural .procedural-cell-left{text-align:left}tbody.procedural tr.procedural .procedural-cell-centre{text-align:center}tbody.procedural tr.procedural .procedural-cell-center{text-align:center}tbody.procedural tr.procedural .procedural-cell-right{text-align:right}tbody.procedural tr.procedural .procedural-cell-top{vertical-align:text-top}tbody.procedural tr.procedural .procedural-cell-middle{vertical-align:baseline}tbody.procedural tr.procedural .procedural-cell-bottom{vertical-align:text-bottom}tbody.procedural tr.procedural .procedural-cell-label{font-weight:bold}li.item{padding-left:.4rem;margin-left:calc(var(--level)*1rem)}li.item::marker{content:attr(data-bullet)}div.rakudoc-image-placement{display:flex;flex-direction:column;align-items:center}.rakudoc-placement-error{display:flex;justify-content:sapace-around;align-items:center;color:red;font-weight:bold}.raku-anchor{font-size:.9em;text-decoration:none;visibility:hidden}.heading:hover .raku-anchor{visibility:visible;padding-left:5px}
+<style>/*! Vanilla CSS */span.basis{font-weight:800}span.important{font-style:italic}span.unusual{text-decoration:underline}span.code{font-weight:500;background-color:linen;display:inline-block;margin:2px;padding:2px}span.overstrike{text-decoration:line-through}span.high{vertical-align:super}span.junior{vertical-align:sub}span.replace{font-style:small-caps;text-shadow:-1px 1px}span.indexed{text-shadow:1px 1px orange}span.indexed:hover::before{content:attr(data-index-text);translate:0 -1.5em;position:absolute;opacity:75%;background-color:#40e0d0;color:indigo}span.keyboard{text-shadow:1px 1px}span.terminal{text-decoration:overline underline}span.footnote{vertical-align:super}span.developer-version{display:none;color:red}span.developer-version span.developer-note{font-family:"Brush Script MT",cursive}span.developer-version:hover{display:inline-block;transform:translate(50px, 100px);z-index:5}span.bad-markdown{text-shadow:1px 1px red}pre.code-block{background-color:#eee;margin:1rem;padding:0 1rem 1rem 1rem}pre.input-block{background-color:#eee;margin:1rem;padding:0 1rem 1rem 1rem}pre.input-block::before{content:"--- input ---";display:block;text-shadow:-2px -2px 4px #000;color:#fff;padding-bottom:1rem}pre.output-block{background-color:#eee;margin:1rem;padding:0 1rem 1rem 1rem}pre.output-block::before{content:"--- output ---";display:block;text-shadow:2px 2px 4px #000;color:#fff;padding-bottom:1rem}div.defn-text{margin-left:1rem}div.defn-term{font-weight:bold;font-style:italic}div.id-target{display:none}div.nested{margin-left:5rem}div.toc .toc-item{margin-left:calc(var(--level)*1rem)}div.toc .toc-item::before{content:attr(data-bullet)}div.toc .toc-item a{padding-left:.4rem}div.index-section{margin-left:calc((var(--level) - 1)*1rem)}div.index-section[data-index-level="1"]{text-shadow:1px 1px orange}div.index-section>a.index-ref{white-space:nowrap;display:inline-block;width:1em}div.index-section>a.index-ref+span{display:none;width:0}div.index-section>a.index-ref:hover+span{display:inline-block;position:absolute;width:auto;z-index:5;background-color:#fff5ee}span.developer-note{display:none;width:0;color:blue;text-shadow:2px 2px 5px green}span.developer-version{display:none;width:0;color:red;text-shadow:2px 2px 5px green}.delta::before,span.developer-text::before{content:"ℹ";vertical-align:super}.delta:hover .developer-version,span.developer-text:hover .developer-version{display:inline-block;position:absolute;width:100%;z-index:5;transform:translate(0.5rem, -1rem)}.delta:hover .developer-note,span.developer-text:hover .developer-note{display:inline-block;position:absolute;width:auto;z-index:5;margin-left:1rem}span.developer-text:hover{text-decoration:overline}div.footer{border-top:2px dashed;margin:1rem 0;padding:2rem}div.footer .footer-field{display:inline-block}div.footer .footer-line{display:block}.heading>a{color:maroon;text-decoration:none}h.title{font-size:larger}table,th,td{border:1px solid;border-collapse:collapse}tbody.procedural tr.procedural .procedural-cell-left{text-align:left}tbody.procedural tr.procedural .procedural-cell-centre{text-align:center}tbody.procedural tr.procedural .procedural-cell-center{text-align:center}tbody.procedural tr.procedural .procedural-cell-right{text-align:right}tbody.procedural tr.procedural .procedural-cell-top{vertical-align:text-top}tbody.procedural tr.procedural .procedural-cell-middle{vertical-align:baseline}tbody.procedural tr.procedural .procedural-cell-bottom{vertical-align:text-bottom}tbody.procedural tr.procedural .procedural-cell-label{font-weight:bold}li.item{padding-left:.4rem;margin-left:calc(var(--level)*1rem)}li.item::marker{content:attr(data-bullet)}div.rakudoc-image-placement{display:flex;flex-direction:column;align-items:center}.rakudoc-placement-error{display:flex;justify-content:sapace-around;align-items:center;color:red;font-weight:bold}.raku-anchor{font-size:.9em;text-decoration:none;visibility:hidden}.heading:hover .raku-anchor{visibility:visible;padding-left:5px}
 </style>
 <style>/* bulma */
 #page-nav{width:25%;position:fixed}#page-nav .panel-block .toc{overflow-y:scroll;height:65vh}#page-nav .panel-block .index{overflow-y:scroll;height:65vh}.main-footer{z-index:1;position:relative}.toc-item:hover{background:var(--bulma-background)}.toc-item a{text-decoration:none;color:var(--bulma-text)}
 </style>
 <style>/* bulma */
-.content p+ul.item-list{margin-top:0}.content p+ol.item-list{margin-top:0}.delta:hover{border:var(--bulma-border-hover) 1px solid}.navbar-start{margin-bottom:1rem}
+.content p+ul.item-list{margin-top:0}.content p+ol.item-list{margin-top:0}.delta:hover{border:var(--bulma-border-hover) 1px solid}.navbar-start{margin-bottom:1rem}table{width:fit-content;margin:auto}table caption{font-weight:bold}
 </style>
 <style>/* bulma */
-label.chyronToggle input#navbar-toc-toggle{opacity:0;height:0;width:0}label.chyronToggle span.checkmark{top:1rem;position:relative;cursor:pointer}label.chyronToggle input[type=checkbox]{position:absolute;opacity:0;cursor:pointer;height:0;width:0}label.chyronToggle span.checkmark::before{content:"[⇨";color:gray;font-weight:800;line-height:.5rem;font-size:1.75rem;margin-right:.25rem}label.chyronToggle:hover span.checkmark::before{content:"[ ⇨"}label.chyronToggle input[type=checkbox]:checked+.checkmark::before{content:"[ ⇦"}label.chyronToggle:hover input[type=checkbox]:checked+.checkmark::before{content:"[⇦"}
+label.chyronToggle input#navbar-toc-toggle{opacity:0;height:0;width:0}label.chyronToggle span.checkmark{top:1rem;position:relative;cursor:pointer}label.chyronToggle input[type=checkbox]{position:absolute;opacity:0;cursor:pointer;height:0;width:0}label.chyronToggle span.checkmark::before{content:"[⇨";color:gray;font-weight:800;line-height:.5rem;font-size:1.75rem;margin-right:.25rem;width:3rem;display:inline-block}label.chyronToggle:hover span.checkmark::before{content:"[ ⇨"}label.chyronToggle input[type=checkbox]:checked+.checkmark::before{content:"[ ⇦"}label.chyronToggle:hover input[type=checkbox]:checked+.checkmark::before{content:"[⇦"}
 </style>
 <style>/* graphviz */
 div.graphviz{display:flex;justify-content:space-around;align-items:center;margin:auto;margin-bottom:1rem}.graphviz-error{display:flex;justify-content:space-around;align-items:center;color:red;font-weight:bold}.graphviz-error span.data{color:green}
 </style>
 <style>/* hilite */
-.raku-code{position:relative;margin:1rem 0}.raku-code button.copy-code{cursor:pointer;opacity:0;padding:0 .25rem .25rem .25rem;position:absolute}.raku-code:hover button.copy-code{opacity:.5}.raku-code label{float:right;font-size:xx-small;font-style:italic;height:auto;padding-right:50px}.raku-code pre.browser-hl{padding:7px}.raku-code .code-name{padding-top:.75rem;padding-left:1.25rem;font-weight:500}.raku-code pre{display:inline-block;overflow:scroll;width:96%}.raku-code .rakudoc-in-code{padding:1.25rem 1.5rem}.raku-code .section{padding:0rem}.raku-code .rainbow-name_scalar{color:var(--bulma-link-40);font-weight:500}.raku-code .rainbow-name_array{color:var(--bulma-link);font-weight:500}.raku-code .rainbow-name_hash{color:var(--bulma-link-60);font-weight:500}.raku-code .rainbow-name_code{color:var(--bulma-info);font-weight:500}.raku-code .rainbow-keyword{color:var(--bulma-primary);font-weight:500}.raku-code .rainbow-operator{color:var(--bulma-success);font-weight:500}.raku-code .rainbow-type{color:var(--bulma-danger-60);font-weight:500}.raku-code .rainbow-routine{color:var(--bulma-info-30);font-weight:500}.raku-code .rainbow-string{color:var(--bulma-info-40);font-weight:500}.raku-code .rainbow-string_delimiter{color:var(--bulma-primary-40);font-weight:500}.raku-code .rainbow-escape{color:var(--bulma-black-60);font-weight:500}.raku-code .rainbow-text{color:var(--bulma-black);font-weight:500}.raku-code .rainbow-comment{color:var(--bulma-success-30);font-weight:500}.raku-code .rainbow-regex_special{color:var(--bulma-success-60);font-weight:500}.raku-code .rainbow-regex_literal{color:var(--bulma-black-60);font-weight:500}.raku-code .rainbow-regex_delimiter{color:var(--bulma-primary-60);font-weight:500}.raku-code .rainbow-rakudoc_text{color:var(--bulma-success-40);font-weight:500}.raku-code .rainbow-rakudoc_markup{color:var(--bulma-danger-40);font-weight:500}
+.raku-code{position:relative;margin:1rem 0}.raku-code button.copy-code{cursor:pointer;opacity:0;padding:0 .25rem .25rem .25rem;position:absolute}.raku-code:hover button.copy-code{opacity:.5}.raku-code label{float:right;font-size:xx-small;font-style:italic;height:auto;padding-right:0}.raku-code pre.browser-hl{padding:7px}.raku-code .code-name{padding-top:.75rem;padding-left:1.25rem;font-weight:500}.raku-code pre{display:inline-block;overflow:scroll;width:100%}.raku-code .rakudoc-in-code{padding:1.25rem 1.5rem}.raku-code .section{padding:0rem}.raku-code .rainbow-name_scalar{color:var(--bulma-link-40);font-weight:500}.raku-code .rainbow-name_array{color:var(--bulma-link);font-weight:500}.raku-code .rainbow-name_hash{color:var(--bulma-link-60);font-weight:500}.raku-code .rainbow-name_code{color:var(--bulma-info);font-weight:500}.raku-code .rainbow-keyword{color:var(--bulma-primary);font-weight:500}.raku-code .rainbow-operator{color:var(--bulma-success);font-weight:500}.raku-code .rainbow-type{color:var(--bulma-danger-60);font-weight:500}.raku-code .rainbow-routine{color:var(--bulma-info-30);font-weight:500}.raku-code .rainbow-string{color:var(--bulma-info-40);font-weight:500}.raku-code .rainbow-string_delimiter{color:var(--bulma-primary-40);font-weight:500}.raku-code .rainbow-escape{color:var(--bulma-black-60);font-weight:500}.raku-code .rainbow-text{color:var(--bulma-black);font-weight:500}.raku-code .rainbow-comment{color:var(--bulma-success-30);font-weight:500}.raku-code .rainbow-regex_special{color:var(--bulma-success-60);font-weight:500}.raku-code .rainbow-regex_literal{color:var(--bulma-black-60);font-weight:500}.raku-code .rainbow-regex_delimiter{color:var(--bulma-primary-60);font-weight:500}.raku-code .rainbow-rakudoc_text{color:var(--bulma-success-40);font-weight:500}.raku-code .rainbow-rakudoc_markup{color:var(--bulma-danger-40);font-weight:500}
 </style>
 <style>/* latexformula */
 div.latex-equation{display:flex;justify-content:space-around;align-items:center}div.latex-equation a.logo{align-self:flex-last}span.latex-formula{display:inline-block;cursor:crosshair}span.latex-formula a{display:none}span.latex-formula:hover>a{display:inline-block;position:absolute;transform:translate(-3rem, -2rem);background:#faebd7}.latex-render-error{color:red;font-weight:bold}
@@ -354,10 +354,6 @@
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#Implementor_considerations">Implementor considerations</a></div>
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#AUTHORS_0">AUTHORS</a></div>
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#Summary">Summary</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Directives_0">Directives</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Blocks">Blocks</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Metadata_options">Metadata options</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Markup_instructions_0">Markup instructions</a></div>
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#LICENSE">LICENSE</a></div>
 </div>
 
@@ -473,10 +469,6 @@
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#Implementor_considerations">Implementor considerations</a></div>
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#AUTHORS_0">AUTHORS</a></div>
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#Summary">Summary</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Directives_0">Directives</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Blocks">Blocks</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Metadata_options">Metadata options</a></div>
-<div class="toc-item" style="--level:1;" data-bullet="▹"><a href="#Markup_instructions_0">Markup instructions</a></div>
 <div class="toc-item" style="--level:0;" data-bullet=""><a href="#LICENSE">LICENSE</a></div>
 </div>
 
@@ -506,7 +498,7 @@
 
         <div class="content px-4">
         
-<div class="id-target" id="VERSION&amp;nbsp&amp;nbsp&amp;nbsp&amp;nbsp2.10.4"></div><h1 id="VERSION" class="heading py-2 "><a href="#" title="go to top of document">VERSION&nbsp&nbsp&nbsp&nbsp2.10.4</a><a class="raku-anchor" title="direct link" href="#VERSION&amp;nbsp&amp;nbsp&amp;nbsp&amp;nbsp2.10.4">§</a></h1>
+<div class="id-target" id="VERSION&amp;nbsp&amp;nbsp&amp;nbsp&amp;nbsp2.11.1"></div><h1 id="VERSION" class="heading py-2 "><a href="#" title="go to top of document">VERSION&nbsp&nbsp&nbsp&nbsp2.11.1</a><a class="raku-anchor" title="direct link" href="#VERSION&amp;nbsp&amp;nbsp&amp;nbsp&amp;nbsp2.11.1">§</a></h1>
 <p id="b25d5ab">RakuDoc is a markup language with simple instructions for simple tasks and more complex structures to suit larger projects. There is a clear distinction between documenting intended to help maintain and develop the software, and the visually presentations needed by a newcomer to understand how to use software. </p>
 <h1 id="SYNOPSIS" class="heading py-2 "><a href="#" title="go to top of document">SYNOPSIS</a><a class="raku-anchor" title="direct link" href="#SYNOPSIS">§</a></h1>
 <p id="67e0153">Consider the two ways in which documentation is used. </p>
@@ -603,7 +595,7 @@ <h1 id="Components" class="heading py-2 "><a href="#" title="go to top of docume
 <li class="item" data-bullet="•" style="--level:0;"> <p id="6a4f7c6"><span class="basis">=end</span> specifies the end of a delimited block </p></li>
 <li class="item" data-bullet="•" style="--level:0;"> <p id="d01d69d"><span class="basis">=for</span> specifies the start of an extended block </p></li>
 <li class="item" data-bullet="•" style="--level:0;"> <p id="dbb40c8"><span class="basis">=finish</span> ends ambient code and is followed by text </p></li>
-<li class="item" data-bullet="•" style="--level:0;"> <p id="3a7af55"><span class="basis">=alias</span> specifies a text substitution available in subsequent <span class="code">A&lt;...|&gt;</span> markup instructions. The general syntax for an alias directive is: </p>
+<li class="item" data-bullet="•" style="--level:0;"> <p id="621000b"><span class="basis">=alias</span> specifies a text substitution available in subsequent <span class="code">A&lt;...&gt;</span> markup instructions. The general syntax for an alias directive is: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -793,10 +785,10 @@ <h1 id="Components" class="heading py-2 "><a href="#" title="go to top of docume
             <h1 id="Directives" class="heading py-2 "><a href="#" title="go to top of document">Directives</a><a class="raku-anchor" title="direct link" href="#Directives">§</a></h1>
 <p id="a6cf5a8">Directives are similar in form to <span class="important">block</span> instructions, but they do not have the extended or delimited forms. If a directive name is preceded by a <span class="code">=begin</span>, <span class="code">=for</span> or <span class="code">=end</span>, then an error will be thrown. </p>
 <h2 id="Aliases" class="heading py-2 "><a href="#" title="go to top of document">Aliases</a><a class="raku-anchor" title="direct link" href="#Aliases">§</a></h2>
-<p id="85cf9ca">The <span class="code">=alias</span> directive provides a way to define block-scoped synonyms for longer RakuDoc sequences, (meta)object declarators from the code, or even entire chunks of ambient source. These synonyms can then be inserted into subsequent RakuDoc using the <a href="#Alias_placements"><span class="code">A&lt;|&gt; formatting code</span></a>. </p>
+<p id="9e406c0">The <span class="code">=alias</span> directive provides a way to define block-scoped synonyms for longer RakuDoc sequences, (meta)object declarators from the code, or even entire chunks of ambient source. These synonyms can then be inserted into subsequent RakuDoc using the <a href="#Alias_placements"><span class="code">A&lt;&gt; formatting code</span></a>. </p>
 <p id="f28ef43">An <span class="code">=alias</span> is scoped from immediately after its declaration up to the end of the innermost surrounding RakuDoc block. </p>
 <p id="fb34b07">The alias directive takes two arguments. The first is an identifier (which is usually specified in uppercase, though this is not mandatory). The second argument consists of one or more lines of replacement text. </p>
-<p id="ed20983">Each <span class="code">=alias</span> directive creates a block-scoped RakuDoc macro that can be invoked during document generation by placing the identifier (i.e. the first argument of the alias) in an <span class="code">A&lt;|&gt;</span> formatting code. This formatting code is then replaced by the text returned by the new macro. </p>
+<p id="46495cd">Each <span class="code">=alias</span> directive creates a block-scoped RakuDoc macro that can be invoked during document generation by placing the identifier (i.e. the first argument of the alias) in an <span class="code">A&lt;&gt;</span> formatting code. This formatting code is then replaced by the text returned by the new macro. </p>
 <p id="f51d8b1">The replacement text returned by the alias macro begins at the first non-whitespace character after the alias's identifier, and continues to the end of the line. You can extend the replacement text over multiple lines by starting the following line(s) with an <span class="code">=</span> (at the same level of indentation as the <span class="code">=alias</span> directive itself) followed by at least one whitespace. Each additional line of replacement text uses the original line's (virtual) left margin, as specified by the indentation of the replacement text on the <span class="code">=alias</span> line. </p>
 <p id="c82f38e">For example: </p>
 
@@ -962,7 +954,7 @@ <h2 id="Config" class="heading py-2 "><a href="#" title="go to top of document">
 <div class="id-target" id="Placement from external sources"></div><h2 id="Placement_from_external_sources" class="heading py-2 "><a href="#" title="go to top of document">Placement from external sources</a><a class="raku-anchor" title="direct link" href="#Placement from external sources">§</a></h2>
 <p id="3eb6881">The <span class="code">=place</span> instruction is a directive that tells the renderer to obtain text, information, or an object from another source. </p>
 <p id="c908858">The rendered version of the data placed in the text is considered to form its own block scope. </p>
-<p id="4fdd0cb">An in-line version of <span class="code">=place</span> is <span class="code">P&lt;...|&gt;</span>, which is described in more detail in the section on markup codes. </p>
+<p id="207c136">An in-line version of <span class="code">=place</span> is <span class="code">P&lt;...&gt;</span>, which is described in more detail in the section on markup codes. </p>
 <p id="7c0037b">The schema of the URL specified in a <span class="code">=place</span> directive specifies where to look for the external content: </p>
 <table class="table is-striped is-bordered">	<thead>
 		<tr><th>Schema</th><th>Where to look for the resource</th></tr>
@@ -1348,7 +1340,7 @@ <h3 id="Sections" class="heading py-2 "><a href="#" title="go to top of document
             <p id="92559e9">In this example, the two embedded <span class="code">K&lt;...&gt;</span> sequences would be recognized as inline mark-up and rendered appropriately (i.e. as keyboard input). </p>
 
 <div class="id-target" id="Markup within verbatim blocks"></div><h3 id="Markup_within_verbatim_blocks" class="heading py-2 "><a href="#" title="go to top of document">Markup within verbatim blocks</a><a class="raku-anchor" title="direct link" href="#Markup within verbatim blocks">§</a></h3>
-<p id="de1d066">Although <span class="code">=code</span> blocks automatically disregard all markup instructions, occasionally you may still need to specify some markup within a code block. For example, you may wish to emphasize a particular keyword in an example (using a <span class="code">B&lt;&gt;</span> code). Or you may want to indicate that part of the example is metasyntactic (using the <span class="code">R&lt;&gt;</span> code). Or you might need to insert a non-ASCII character (using the <span class="code">E&lt;|&gt;</span> code). </p>
+<p id="3b96c6e">Although <span class="code">=code</span> blocks automatically disregard all markup instructions, occasionally you may still need to specify some markup within a code block. For example, you may wish to emphasize a particular keyword in an example (using a <span class="code">B&lt;&gt;</span> code). Or you may want to indicate that part of the example is metasyntactic (using the <span class="code">R&lt;&gt;</span> code). Or you might need to insert a non-ASCII character (using the <span class="code">E&lt;&gt;</span> code). </p>
 <p id="a081e72">You can specify a list of <a href="#Display_only_codes">display only</a> markup instructions (B C H I J K N O R S T U V) that should still be recognized within a code block using the <span class="code">:allow</span> option. The value of the <span class="code">:allow</span> option must be a list of the (single-letter) names of one or more markup instructions. Those codes will then remain active inside the code block. For example: </p>
 
                 <div class="raku-code">
@@ -1984,9 +1976,8 @@ <h2 id="Tables" class="heading py-2 "><a href="#" title="go to top of document">
 </div>
                 </div>
             <p id="33c7d15">... produces the following table: </p>
-
-<div class="id-target" id="Experimental data"></div><h1 id="Experimental_data" class="heading py-2 "><a href="#" title="go to top of document">Experimental data</a><a class="raku-anchor" title="direct link" href="#Experimental data">§</a></h1>
-<table class="table is-striped is-bordered"><tbody class="procedural">
+<div id="Experimental_data"></div>
+<table class="table is-striped is-bordered"><caption>Experimental data</caption><tbody class="procedural">
 <tr class="procedural"><th rowspan="2" class="">Date</th><th colspan="3" class="">Samples</th><th rowspan="2" class="">Mean</th></tr>
 <tr class="procedural"><th class=""><p id="be4f23a"><span class="important">Sample 1</span> </p></th><th class=""><p id="ea75ec8"><span class="important">Sample 2</span> </p></th><th class=""><p id="7932f80"><span class="important">Sample 3</span> </p></th></tr>
 <tr class="procedural"><td class="">2023-03-08</td><td class="">0.4</td><td class="">0.1</td><td class="">0.3</td><td class="">0.26667</td></tr>
@@ -2317,10 +2308,10 @@ <h2 id="Tables" class="heading py-2 "><a href="#" title="go to top of document">
 </div>
                 </div>
             <h2 id="Formulae" class="heading py-2 "><a href="#" title="go to top of document">Formulae</a><a class="raku-anchor" title="direct link" href="#Formulae">§</a></h2>
-<p id="43640de">RakuDoc v.2 provides a built-in block <span class="code">=formula</span> and an inline markup code <span class="code">F&lt;|&gt;</span> to contain text that will be rendered as formulae. </p>
-<p id="8f3be60">There are several markup languages for expressing mathematical expressions, so the RakuDoc v.2 specification <span class="important">recommends</span> the currently most widespread markup syntax for <span class="code">=formula</span> and <span class="code">F&lt;|&gt;</span>, namely the <a href="https://en.wikibooks.org/wiki/LaTeX/Mathematics">LaTeX mathematical notation</a>, including the extensions specified in the <a href="https://en.wikipedia.org/wiki/AMS-LaTeX">AMSMath package</a> </p>
+<p id="25a3ec4">RakuDoc v.2 provides a built-in block <span class="code">=formula</span> and an inline markup code <span class="code">F&lt;&gt;</span> to contain text that will be rendered as formulae. </p>
+<p id="26b45ae">There are several markup languages for expressing mathematical expressions, so the RakuDoc v.2 specification <span class="important">recommends</span> the currently most widespread markup syntax for <span class="code">=formula</span> and <span class="code">F&lt;&gt;</span>, namely the <a href="https://en.wikibooks.org/wiki/LaTeX/Mathematics">LaTeX mathematical notation</a>, including the extensions specified in the <a href="https://en.wikipedia.org/wiki/AMS-LaTeX">AMSMath package</a> </p>
 <p id="adabb7d">This does not preclude the development of custom blocks to support other mathematical markup languages, eg., a <span class="code">=MathML</span> custom block to support another syntax. </p>
-<p id="1077aed">Implementors of renderers are <span class="basis"><span class="important">not</span></span> required to render the contents of these instructions; it is acceptable for a renderer to render the contents of a <span class="code">=formula</span> or <span class="code">F&lt;|&gt;</span> in some other way than as a fully realized mathematical equation. </p>
+<p id="80f14b4">Implementors of renderers are <span class="basis"><span class="important">not</span></span> required to render the contents of these instructions; it is acceptable for a renderer to render the contents of a <span class="code">=formula</span> or <span class="code">F&lt;&gt;</span> in some other way than as a fully realized mathematical equation. </p>
 <p id="e8ddc67">For example, the following two formulae: </p>
 
                 <div class="raku-code">
@@ -2356,8 +2347,8 @@ <h1 id="Formula_cannot_be_rendered_0" class="heading py-2 "><div class="latex-eq
 <div class="nested"><p id="a837896">We will use the identity: <span class="unusual">\sum \frac{1}{n^{2}} = \frac{\pi^{2}}{6}</span> </p>
 <p id="38cef2a">... where the value of pi can be inferred from Euler’s Identity: </p>
 <p id="be2a575"><span class="unusual">e^{i\pi}+1=0</span> </p></div>
-<p id="f2cb7af">Both <span class="code">=formula</span> and <span class="code">F&lt;|&gt;</span> may take explicit ALT texts, so that the author can decide how their formula should be rendered in cases where the renderer cannot handle the specification. </p>
-<p id="b122766">That is, the <span class="code">=formula</span> block accepts an <span class="code">:alt</span> metaoption, and the syntax for the <span class="code">F&lt;|&gt;</span> instruction is either <span class="code">F&lt; FORMULA |&gt;</span> or <span class="code">F&lt; ALT | FORMULA &gt;</span>. </p>
+<p id="912459f">Both <span class="code">=formula</span> and <span class="code">F&lt;&gt;</span> may take explicit ALT texts, so that the author can decide how their formula should be rendered in cases where the renderer cannot handle the specification. </p>
+<p id="bb10145">That is, the <span class="code">=formula</span> block accepts an <span class="code">:alt</span> metaoption, and the syntax for the <span class="code">F&lt;&gt;</span> instruction is either <span class="code">F&lt; FORMULA &gt;</span> or <span class="code">F&lt; ALT | FORMULA &gt;</span>. </p>
 <p id="e8ae512">Using the ALT text options, the document author can supply a suitable explicit alternative rendering to renderers that cannot handle the full formula syntax: </p>
 
                 <div class="raku-code">
@@ -2375,15 +2366,14 @@ <h1 id="Formula_cannot_be_rendered_0" class="heading py-2 "><div class="latex-eq
 </div>
                 </div>
             <p id="a683400">An ALT text allows an author to rely on getting an “accurate” representation under those renderers that fully support formulas, and to be able to fall back on a range of reasonable alternatives under those renderers that don’t: </p>
-
-<div class="id-target" id="Fallback options"></div><h1 id="Fallback_options" class="heading py-2 "><a href="#" title="go to top of document">Fallback options</a><a class="raku-anchor" title="direct link" href="#Fallback options">§</a></h1>
-<table class="table is-striped is-bordered"><tbody class="procedural">
+<div id="Fallback_options"></div>
+<table class="table is-striped is-bordered"><caption>Fallback options</caption><tbody class="procedural">
 <tr class="procedural"><th class="">Fall back on</th><th class="">Example</th></tr>
 <tr class="procedural"><td class="">Plaintext</td><td class=""><p id="016ce04">F<&nbsp;&nbsp;Euler's Identity | e^{i\pi}+1=0 > </p></td></tr>
 <tr class="procedural"><td class="">RakuDoc</td><td class=""><p id="9844e7f">F<&nbsp;&nbsp;eH&lt;iπ&gt; + 1 = 0 | e^{i\pi}+1=0 > </p></td></tr>
 <tr class="procedural"><td class="">Unicode</td><td class=""><p id="e04dd62">F<&nbsp;&nbsp;eⁱᐢ + 1 = 0 | e^{i\pi}+1=0 > </p></td></tr>
-<tr class="procedural"><td class="">Image</td><td class=""><p id="3e27cfb">F<&nbsp;&nbsp;P&lt;file:EulerID.jpg|&gt; | e^{i\pi}+1=0 > </p></td></tr>
-<tr class="procedural"><td class="">Link</td><td class=""><p id="1b1acc6">F<&nbsp;&nbsp;L&lt;https://en.wikipedia.org/wiki/Euler%27s_identity|&gt; | e^{i\pi}+1=0 > </p></td></tr>
+<tr class="procedural"><td class="">Image</td><td class=""><p id="7079cd9">F<&nbsp;&nbsp;P&lt;file:EulerID.jpg&gt; | e^{i\pi}+1=0 > </p></td></tr>
+<tr class="procedural"><td class="">Link</td><td class=""><p id="3ea4ae1">F<&nbsp;&nbsp;L&lt;https://en.wikipedia.org/wiki/Euler%27s_identity&gt; | e^{i\pi}+1=0 > </p></td></tr>
 </tbody></table>
 <p id="4ede661">It is also possible to <span class="basis">stack</span> the fallback options. For example, they could try for an “accurate” rendering of a formula, but fall back on the placement of a pre-rendered image, or (failing to find that) fall back again to a RakuDoc representation with an outgoing link: </p>
 
@@ -2442,7 +2432,7 @@ <h1 id="Formula_cannot_be_rendered_0" class="heading py-2 "><div class="latex-eq
 <p id="8b0f947">A semantic block may be defined, but omitted from the text in the place it is written. This is because sections about Authors, or Licensing, are sometimes required at the end, or at the beginning, or in the meta section of an HTML document. </p>
 <p id="5a8cc81">A renderer is expected to gather the contents of a semantic block for it to be accessible by an external program. </p>
 <p id="50c1021">If the metadata option <span class="code">:hidden</span> is associated with a semantic block (by using a <span class="code">=config</span> directive, or as a metadata option with the <span class="important">extended</span> or <span class="important">abbreviated</span> forms) then the renderer will not render the semantic block at the position it is placed in the RakuDoc document. It will be placed in a data structure by the renderer and the contents can be rendered at a place defined by a <a href="#Placement_links">Placement instruction</a>. </p>
-<p id="47968b1">The block name of a rendered semantic block will be placed in the <a href="#Table_of_Contents_and_Index"><span class="important">Table of Contents</span></a> table in the position that it is rendered, unless the <span class="code">:toc</span>, <span class="code">:headlevel</span>, and or <span class="code">:caption</span> options are set. A <span class="code">:hidden</span> metadata option will also remove the block's entry from the ToC. But if it is placed by a <span class="code">P&lt;semantic:|&gt;</span> instruction, the block entry will be placed at the appropriate point in the ToC. </p>
+<p id="10cd625">The block name of a rendered semantic block will be placed in the <a href="#Table_of_Contents_and_Index"><span class="important">Table of Contents</span></a> table in the position that it is rendered, unless the <span class="code">:toc</span>, <span class="code">:headlevel</span>, and or <span class="code">:caption</span> options are set. A <span class="code">:hidden</span> metadata option will also remove the block's entry from the ToC. But if it is placed by a <span class="code">P&lt;semantic:&gt;</span> instruction, the block entry will be placed at the appropriate point in the ToC. </p>
 
 <div class="id-target" id="User-defined blocks"></div><h2 id="User-defined_blocks" class="heading py-2 "><a href="#" title="go to top of document">User-defined blocks</a><a class="raku-anchor" title="direct link" href="#User-defined blocks">§</a></h2>
 <p id="f138bf4">When a block name contains both an upper case and a lower case character, as specified <a href="#Naming_rules">in the naming rules below</a>, it is interpreted as a developer-defined block. The naming rules are to ensure that built-in blocks, semantic blocks, and custom blocks are never mixed up. </p>
@@ -2467,7 +2457,7 @@ <h1 id="Formula_cannot_be_rendered_0" class="heading py-2 "><div class="latex-eq
 <li class="item" data-bullet="•" style="--level:0;"> <p id="d564ad9">Custom markup codes (e.g. <span class="code">Æ</span>, <span class="code">Ø</span>, <span class="code">ß</span>) </p></li>
 <li class="item" data-bullet="▹" style="--level:1;"> names must consist of exactly one uppercase Unicode character (i.e. with the Upper property)</li>
 <li class="item" data-bullet="▹" style="--level:1;"> names may not be a character in the ASCII range (these are reserved for current and future built-in markup codes)</li>
-<li class="item" data-bullet="▹" style="--level:1;"> <p id="acea5e8">the built-in markup instruction <a href="#Markup_extras"><span class="code">M&lt;|&gt;</span></a> is also provided for custom markup </p></li>
+<li class="item" data-bullet="▹" style="--level:1;"> <p id="af0097c">the built-in markup instruction <a href="#Markup_extras"><span class="code">M&lt;&gt;</span></a> is also provided for custom markup </p></li>
 </ul>
 
 <div class="id-target" id="Implied code and indentation"></div><h2 id="Implied_code_and_indentation" class="heading py-2 "><a href="#" title="go to top of document">Implied code and indentation</a><a class="raku-anchor" title="direct link" href="#Implied code and indentation">§</a></h2>
@@ -2587,7 +2577,7 @@ <h2 id="Anchors" class="heading py-2 "><a href="#" title="go to top of document"
 </div>
                 </div>
             <p id="50fd2ae">...is rendered, it is also associated with an anchor, so that when a link of the form <span class="code">L&lt;link to an internal heading|#Table of Contents and Index&gt;</span> is rendered, the renderer will place a link to the correct heading in the output format. The anchor will also be used in the Table of Contents. </p>
-<p id="bfaaf60">Note that the text in the <span class="code">L&lt;...|&gt;</span> before the <span class="code">|</span> is the display text, and the tag after the <span class="code">|</span> is the content of the target <span class="code">=head</span> block. </p>
+<p id="b4d5ebd">Note that the text in the <span class="code">L&lt;...&gt;</span> before the <span class="code">|</span> is the display text, and the tag after the <span class="code">|</span> is the content of the target <span class="code">=head</span> block. </p>
 <p id="97b3eee">In order for a link to work correctly, the anchor must be unique. The renderer is free to chose the algorithm it uses for the internal anchor. This is because different outputs, such as Markdown and HTML, have different formats for anchors. </p>
 <p id="b8f1aff">An author may want to shorten an internal link to a title, and also to place an anchor on every block. </p>
 <p id="a370d22">The <span class="code">:id&lt;name of a link&gt;</span> metadata option can be attached to any block. For example: </p>
@@ -2626,8 +2616,8 @@ <h2 id="Anchors" class="heading py-2 "><a href="#" title="go to top of document"
                 </div>
             
 <div class="id-target" id="Table of Contents and Index"></div><h2 id="Table_of_Contents_and_Index" class="heading py-2 "><a href="#" title="go to top of document">Table of Contents and Index</a><a class="raku-anchor" title="direct link" href="#Table of Contents and Index">§</a></h2>
-<p id="c0c6c48">When a renderer parses a file containing RakuDoc, heading and <span class="code">X&lt;|&gt;</span> markup information is collected. This information can be rendered using <a href="#Placement_links">a <span class="code">P&lt;|&gt;</span> markup instruction</a>, or may be used in another way by the renderer (e.g. to create a sidebar with the Table of Contents). </p>
-<p id="6323407">Named blocks are considered by default to be equivalent to <span class="code">=head</span> for the purposes of a Table of Contents. The exceptions are <span class="code">para</span>, <span class="code">nested</span>, <span class="code">code</span>, <span class="code">input</span> and <span class="code">output</span> blocks. </p>
+<p id="bb7889c">When a renderer parses a file containing RakuDoc, heading and <span class="code">X&lt;&gt;</span> markup information is collected. This information can be rendered using <a href="#Placement_links">a <span class="code">P&lt;&gt;</span> markup instruction</a>, or may be used in another way by the renderer (e.g. to create a sidebar with the Table of Contents). </p>
+<p id="6278640">Builtin, semantic and custom blocks are considered by default to be equivalent to <span class="code">=head</span> for the purposes of a Table of Contents. The following are considered to be equivalent to paragraphs (not included in a Table of Contents) by default: <span class="code">=para</span>, <span class="code">=nested</span>, <span class="code">=code</span>, <span class="code">=input</span>, <span class="code">=output</span>, &lt;=table&gt;, <span class="code">=defn</span>, <span class="code">=item</span>, <span class="code">=alias</span>, and their <span class="important">num</span> variants if they exist. </p>
 <p id="8d20559">This default can be changed with the <span class="code">:toc</span> and <span class="code">:headlevel</span> meta tabs. </p>
 <p id="085688f">Setting <span class="code">:toc</span> on a block will include the contents of the block in the Table of Contents. Including the entire block contents is usually not desirable, so the <span class="code">:caption&lt;...&gt; </span> meta tab can be used to provide a text for the Table of Contents. </p>
 <p id="642e0fb">Setting <span class="code">:!toc</span> will prevent a block's information from being included in the Table of Contents. </p>
@@ -2635,7 +2625,7 @@ <h2 id="Anchors" class="heading py-2 "><a href="#" title="go to top of document"
 
 <div class="id-target" id="Developer or delta notes"></div><h2 id="Developer_or_delta_notes" class="heading py-2 "><a href="#" title="go to top of document">Developer or delta notes</a><a class="raku-anchor" title="direct link" href="#Developer or delta notes">§</a></h2>
 <p id="d0a71d0">When a set of source files is related to a project with versions (such as the Raku language), documentation may get out of date, or may only apply to features of a future release. </p>
-<p id="6f8e81a">A delta note can be attached to a block using the <span class="code">:delta</span> metadata tab, or specified inline with the <span class="code"> Δ&lt; ... |&gt; </span> markup instruction. Both the metadata tab and the markup instruction have two arguments: the first is the version specification, and the second is an optional text note. </p>
+<p id="82490b3">A delta note can be attached to a block using the <span class="code">:delta</span> metadata tab, or specified inline with the <span class="code"> Δ&lt; ... &gt; </span> markup instruction. Both the metadata tab and the markup instruction have two arguments: the first is the version specification, and the second is an optional text note. </p>
 <div class="nested"><p id="8d0409f"><span class="basis">Note:</span> This is an example of a built in markup code that uses a Unicode Upper character. The mnemonic is <span class="important">Delta</span>, which is commonly used to indicate an incremental component. </p></div>
 <p id="bdadcf2">The version specification is summarised as follows: </p>
 <table class="table is-striped is-bordered">	<thead>
@@ -2698,7 +2688,7 @@ <h2 id="Anchors" class="heading py-2 "><a href="#" title="go to top of document"
 <div class="id-target" id="Instructions with side effects"></div><h2 id="Instructions_with_side_effects" class="heading py-2 "><a href="#" title="go to top of document">Instructions with side effects</a><a class="raku-anchor" title="direct link" href="#Instructions with side effects">§</a></h2>
 <p id="34fe50c">Markup instructions, including all customisable instructions, will typically have associated metadata. </p>
 <h3 id="Links" class="heading py-2 "><a href="#" title="go to top of document">Links</a><a class="raku-anchor" title="direct link" href="#Links">§</a></h3>
-<p id="6d91c85">To create a link, enclose it in <span class="code">L&lt; |&gt;</span>. RakuDoc links are more general than the conventional HTML links. </p>
+<p id="fe0675f">To create a link, enclose it in <span class="code">L&lt; &gt;</span>. RakuDoc links are more general than the conventional HTML links. </p>
 <div class="rakudoc-section "><p id="2d06b12">The general syntax is <span class="code"> L&lt; <span class="replace">LABEL</span> | <span class="replace">TARGET</span> &gt; </span> </p>
 </div>
 <p id="98a0dab">where the optional label is text that is rendered and the target may include a schema. If the label is omitted, then the target is used as the label. Whitespace on either side of the bar is not significant. </p>
@@ -2774,17 +2764,17 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
                     <label><b>allow</b> styling</label>
                     <div><pre class="nohighlights">
     I&lt;ACM Transactions on Programming Languages and Systems&gt;
-    is a registered serial publication (L&lt;<span class="basis">issn:0164-0925</span>|&gt;)
+    is a registered serial publication (L&lt;<span class="basis">issn:0164-0925</span>&gt;)
 
-    This module implements the standard Unix L&lt;<span class="basis">man:find(1)</span>|&gt; facilities.
+    This module implements the standard Unix L&lt;<span class="basis">man:find(1)</span>&gt; facilities.
 
-    Please forward bug reports to L&lt;<span class="basis">mailto:abyss@example.org</span>|&gt;
+    Please forward bug reports to L&lt;<span class="basis">mailto:abyss@example.org</span>&gt;
 
     This module needs the L&lt;LAME library|<span class="basis">http://www.mp3dev.org/mp3/</span>&gt;.
 
     You could also write the code L&lt;in gibberish|<span class="basis">RakuDoc:Acme::Anguish</span>&gt;
 
-    Also see: L&lt;<span class="basis">man:bash(1)#Compound Commands</span>|&gt;,
+    Also see: L&lt;<span class="basis">man:bash(1)#Compound Commands</span>&gt;,
 
     =defn lexiphania
     An unfortunate proclivity for
@@ -2793,17 +2783,17 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
     =defn glossoligation
     Restraint of the tongue (voluntary or otherwise)
 
-    To treat his chronic L&lt;<span class="basis">defn:lexiphania</span>|&gt; the doctor prescribed an immediate L&lt;<span class="basis">defn:glossoligation</span>|&gt;
+    To treat his chronic L&lt;<span class="basis">defn:lexiphania</span>&gt; the doctor prescribed an immediate L&lt;<span class="basis">defn:glossoligation</span>&gt;
     or, if that proved ineffective, a complete cephalectomy.
 </pre>
 </div>
                 </div>
             
 <div class="id-target" id="Placement links"></div><h3 id="Placement_links" class="heading py-2 "><a href="#" title="go to top of document">Placement links</a><a class="raku-anchor" title="direct link" href="#Placement links">§</a></h3>
-<p id="f3f50ff">A second kind of link — the <span class="code">P&lt;|&gt;</span> or <span class="basis">placement link</span> — works in the opposite direction. Instead of directing focus out to another document, it allows you to assimilate the contents of another document into your own. </p>
-<p id="34ccddc">In other words, the <span class="code">P&lt;|&gt;</span> markup instruction takes a URI and (where possible) inserts the contents of the corresponding document inline in place of the code itself. </p>
+<p id="4a59dfa">A second kind of link — the <span class="code">P&lt;&gt;</span> or <span class="basis">placement link</span> — works in the opposite direction. Instead of directing focus out to another document, it allows you to assimilate the contents of another document into your own. </p>
+<p id="c1364be">In other words, the <span class="code">P&lt;&gt;</span> markup instruction takes a URI and (where possible) inserts the contents of the corresponding document inline in place of the code itself. </p>
 <p id="6ec7d1b">A URI meets the regex pattern <span class="code">\w+:\S+</span>, where the word characters before <span class="code">:</span> are called the <span class="important">schema</span>. There may not be any spaces in a URI. </p>
-<p id="755da80"><span class="code">P&lt;|&gt;</span> markup is handy for breaking out standard elements of your documentation set into reusable components that can then be incorporated directly into multiple documents. For example: </p>
+<p id="015c407"><span class="code">P&lt;&gt;</span> markup is handy for breaking out standard elements of your documentation set into reusable components that can then be incorporated directly into multiple documents. For example: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -2818,7 +2808,7 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
 <div class="nested">This document is copyright (c) MegaGigaTeraPetaCorp, 2006. All rights reserved.</div>
 <p id="f449656"><span class="basis">Disclaimer</span> </p>
 <div class="nested"><p id="345b51d">ABSOLUTELY NO WARRANTY IS IMPLIED. NOT EVEN OF ANY KIND. WE HAVE SOLD YOU THIS SOFTWARE WITH NO HINT OF A SUGGESTION THAT IT IS EITHER USEFUL OR USABLE. AS FOR GUARANTEES OF CORRECTNESS...DON'T MAKE US LAUGH! AT SOME TIME IN THE FUTURE WE MIGHT DEIGN TO SELL YOU UPGRADES THAT PURPORT TO ADDRESS SOME OF THE APPLICATION'S MANY DEFICIENCIES, BUT NO PROMISES THERE EITHER. WE HAVE MORE LAWYERS ON STAFF THAN YOU HAVE TOTAL EMPLOYEES, SO DON'T EVEN *THINK* ABOUT SUING US. HAVE A NICE DAY. </p></div></div>
-<p id="21b401c">The <span class="code">P&lt;|&gt;</span> markup code can also be specified with an optional display text, which will be rendered if the renderer cannot find or access the external data source for the placement link. For example: </p>
+<p id="3e538b2">The <span class="code">P&lt;&gt;</span> markup code can also be specified with an optional display text, which will be rendered if the renderer cannot find or access the external data source for the placement link. For example: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -2850,7 +2840,7 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
 <li class="item" data-bullet="•" style="--level:0;"> <p id="cb1c020"><span class="code">index:</span> </p></li>
 <li class="item" data-bullet="•" style="--level:0;"> <p id="d605d2f"><span class="code">semantic:</span> </p></li>
 </ul>
-<p id="643aae5">The <span class="code">toc:</span> form is a special pseudo-scheme that inserts a table of contents in place of the <span class="code">P&lt;|&gt;</span> code. After the colon, list the block types that you wish to include in the table of contents. For example, to place a table of contents listing only top- and second-level headings: </p>
+<p id="4cd1e3d">The <span class="code">toc:</span> form is a special pseudo-scheme that inserts a table of contents in place of the <span class="code">P&lt;&gt;</span> code. After the colon, list the block types that you wish to include in the table of contents. For example, to place a table of contents listing only top- and second-level headings: </p>
 <div class="rakudoc-section ">
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -2872,13 +2862,13 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
                 </div>
 </div>
 <p id="dc5d9b0">In order to include the whole table of contents, use <span class="code">toc:*</span>. The <span class="code">*</span> is needed to make this term a valid URI. </p>
-<p id="165ae03">A document may have as many <span class="code">P&lt;toc:...|&gt;</span> placements as necessary. </p>
-<p id="ae81cdd">The <span class="code">index:*</span> form is a special pseudo-scheme that inserts an index table in place of the <span class="code">P&lt;|&gt;</span> code. </p>
-<div class="rakudoc-section "><p id="9df2f28">The <span class="code">semantic:<span class="replace">NAME</span></span> form places the <span class="replace">NAME</span> semantic block at the position of the <span class="code">P&lt;|&gt;</span> instruction. </p>
+<p id="ead43de">A document may have as many <span class="code">P&lt;toc:...&gt;</span> placements as necessary. </p>
+<p id="534e14f">The <span class="code">index:*</span> form is a special pseudo-scheme that inserts an index table in place of the <span class="code">P&lt;&gt;</span> code. </p>
+<div class="rakudoc-section "><p id="e01c765">The <span class="code">semantic:<span class="replace">NAME</span></span> form places the <span class="replace">NAME</span> semantic block at the position of the <span class="code">P&lt;&gt;</span> instruction. </p>
 </div>
 
 <div class="id-target" id="Alias placement"></div><h3 id="Alias_placement" class="heading py-2 "><a href="#" title="go to top of document">Alias placement</a><a class="raku-anchor" title="direct link" href="#Alias placement">§</a></h3>
-<p id="d7fddf0">A variation on the placement instruction is the <span class="code">A&lt;|&gt;</span> instruction, which is replaced by the contents of the named alias or object specified within its delimiters. For example: </p>
+<p id="756846b">A variation on the placement instruction is the <span class="code">A&lt;&gt;</span> instruction, which is replaced by the contents of the named alias or object specified within its delimiters. For example: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -2889,7 +2879,7 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
 </div>
                 </div>
             <p id="e360240">Any Raku object after the Check Phase, such as an object that starts with a sigil, is available within an alias placement. Unless the object is already a string type, it is converted to a string during document-generation by implicitly calling <span class="code">.raku</span> on it. </p>
-<p id="1756281">So, for example, a document can refer to its own filename (as <span class="code">A&lt;$?FILE|&gt;</span>), or to the subroutine inside which the specific RakuDoc is nested (as <span class="code">A&lt;&?ROUTINE|&gt;</span>), or to the current class (as <span class="code">A&lt;$?CLASS|&gt;</span>). Similarly, the value of any program constants defined with sigils can be easily reproduced in documentation: </p>
+<p id="282de66">So, for example, a document can refer to its own filename (as <span class="code">A&lt;$?FILE&gt;</span>), or to the subroutine inside which the specific RakuDoc is nested (as <span class="code">A&lt;&?ROUTINE&gt;</span>), or to the current class (as <span class="code">A&lt;$?CLASS&gt;</span>). Similarly, the value of any program constants defined with sigils can be easily reproduced in documentation: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -2899,26 +2889,26 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
 </pre>
 </div>
                 </div>
-            <p id="82af644">Non-mutating method calls on these objects are also allowed, so a document can reproduce the surrounding subroutine's signature (<span class="code">A&lt;&?ROUTINE.signature|&gt;</span>) or the type of a constant (<span class="code">A&lt;$GROWTH_RATE.WHAT|&gt;</span>). </p>
+            <p id="c847cf9">Non-mutating method calls on these objects are also allowed, so a document can reproduce the surrounding subroutine's signature (<span class="code">A&lt;&?ROUTINE.signature&gt;</span>) or the type of a constant (<span class="code">A&lt;$GROWTH_RATE.WHAT&gt;</span>). </p>
 <p id="51fc984">See <a href="#Alias_blocks">Aliases</a> for further details of the aliasing macro mechanism. </p>
 
 <div class="id-target" id="Inline definitions"></div><h3 id="Inline_definitions" class="heading py-2 "><a href="#" title="go to top of document">Inline definitions</a><a class="raku-anchor" title="direct link" href="#Inline definitions">§</a></h3>
-<p id="8a320ec">A <span class="code">D&lt;|&gt;</span> formatting code marks a piece of text as being the <span class="important">“inline definition”</span> of a term. That is: it’s like a <span class="code">=defn</span> block, but it’s not a list item; it’s just part of the regular text. Well-written documentation often includes sentences/paragraphs that introduce a new term, and define it. Typically we want to visually distinguish those newly defined terms, and to be able to link back to the paragraph where they’re defined. </p>
+<p id="602217e">A <span class="code">D&lt;&gt;</span> formatting code marks a piece of text as being the <span class="important">“inline definition”</span> of a term. That is: it’s like a <span class="code">=defn</span> block, but it’s not a list item; it’s just part of the regular text. Well-written documentation often includes sentences/paragraphs that introduce a new term, and define it. Typically we want to visually distinguish those newly defined terms, and to be able to link back to the paragraph where they’re defined. </p>
 <p id="c82f38e">For example: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
                     <label><b>allow</b> styling</label>
                     <div><pre class="nohighlights">
-    There ensued a terrible moment of <span class="basis">D&lt;coyotus interruptus|&gt;</span>: a brief
+    There ensued a terrible moment of <span class="basis">D&lt;coyotus interruptus&gt;</span>: a brief
     suspension of the effects of gravity, accompanied by a sudden
     to-the-camera realization of imminent downwards acceleration.
 </pre>
 </div>
                 </div>
-            <p id="6eb0ea2">The contents of the <span class="code">D&lt;|&gt;</span> represent the term being defined, the location of the <span class="code">D&lt;|&gt;</span> implies a link target location, and the paragraph containing the <span class="code">D&lt;|&gt;</span> suggests a suitable pop-up definition of the term (if a renderer supports such). </p>
-<p id="2176533">The definition term in a <span class="code">D&lt;|&gt;</span> is rendered distinctly (typically in <span class="basis"><span class="important">bold italics</span></span>), and the <span class="code">D&lt;|&gt;</span> sets up a link target to that term, and possibly a pop-up for the corresponding <span class="code">L&lt;|&gt;</span> link to display the entire paragraph in which the <span class="code">D&lt;|&gt;</span> appeared. For this reason, the term is rendered verbatim, including any attempted markup codes. </p>
-<p id="9c1102b">In other words, when rendered to HTML, a <span class="code">D&lt;term being defined|&gt;</span> would be translated to something like: </p>
+            <p id="dbe4ab8">The contents of the <span class="code">D&lt;&gt;</span> represent the term being defined, the location of the <span class="code">D&lt;&gt;</span> implies a link target location, and the paragraph containing the <span class="code">D&lt;&gt;</span> suggests a suitable pop-up definition of the term (if a renderer supports such). </p>
+<p id="23be9d2">The definition term in a <span class="code">D&lt;&gt;</span> is rendered distinctly (typically in <span class="basis"><span class="important">bold italics</span></span>), and the <span class="code">D&lt;&gt;</span> sets up a link target to that term, and possibly a pop-up for the corresponding <span class="code">L&lt;&gt;</span> link to display the entire paragraph in which the <span class="code">D&lt;&gt;</span> appeared. For this reason, the term is rendered verbatim, including any attempted markup codes. </p>
+<p id="20c8114">In other words, when rendered to HTML, a <span class="code">D&lt;term being defined&gt;</span> would be translated to something like: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -2928,7 +2918,7 @@ <h4 id="Examples" class="heading py-2 "><a href="#" title="go to top of document
 </pre>
 </div>
                 </div>
-            <p id="42f525f">And a <span class="code">L&lt;defn:term being defined|&gt;</span> link would be translated to something like: </p>
+            <p id="0fb18bd">And a <span class="code">L&lt;defn:term being defined&gt;</span> link would be translated to something like: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -3054,7 +3044,7 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
 </pre></div>
 
 <div class="id-target" id="Unicode and HTML references"></div><h3 id="Unicode_and_HTML_references" class="heading py-2 "><a href="#" title="go to top of document">Unicode and HTML references</a><a class="raku-anchor" title="direct link" href="#Unicode and HTML references">§</a></h3>
-<p id="19089f4">Unicode codepoint names or numbers may be included in a RakuDoc document by enclosing them in <span class="code">E&lt; |&gt;</span>. When <span class="code">E&lt; |&gt;</span> encloses a number, it is treated as the Unicode value for the code point using binary, octal, decimal, or hexadecimal numbers using the Raku notations for explicitly based numbers. Numbers without an explicit base, as per Raku convention, are decimal. </p>
+<p id="5a5b173">Unicode codepoint names or numbers may be included in a RakuDoc document by enclosing them in <span class="code">E&lt; &gt;</span>. When <span class="code">E&lt; &gt;</span> encloses a number, it is treated as the Unicode value for the code point using binary, octal, decimal, or hexadecimal numbers using the Raku notations for explicitly based numbers. Numbers without an explicit base, as per Raku convention, are decimal. </p>
 <p id="8c5a941">For example, each of the following: </p>
 
                 <div class="raku-code">
@@ -3079,7 +3069,7 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
                 </div>
             <p id="23cc02d">will be rendered as: </p>
 <div class="nested"><p id="fc97552">« 🇺🇦 Ukraine » </p></div>
-<p id="c419492">Since emojis are graphemes that can be described by Unicode, <span class="code">E&lt; |&gt;</span> will also generate emojis. For example: </p>
+<p id="4bac910">Since emojis are graphemes that can be described by Unicode, <span class="code">E&lt; &gt;</span> will also generate emojis. For example: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -3102,7 +3092,7 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
 </div>
                 </div>
             <p id="07af582">also yields: Raku makes considerable use of the « and » characters. </p>
-<p id="a2c6e5b">The <span class="code">E&lt;|&gt;</span> markup may be used for a list of characters separated by <span class="code">;</span> </p>
+<p id="4a66adf">The <span class="code">E&lt;&gt;</span> markup may be used for a list of characters separated by <span class="code">;</span> </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
@@ -3113,7 +3103,7 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
 </div>
                 </div>
             <p id="48e311c">This would yield: Raku code often contains the ｢｣ bracketing characters to avoid using quotes. </p>
-<p id="27d514f">The <span class="code">E&lt;|&gt;</span> code can also be specified with an alternate display text (before the entity specification and separated from it by a <span class="code">|</span>). When an alternate text is specified, it is used if the specified entity cannot be represented by the renderer (e.g. if the renderer only supports ASCII). </p>
+<p id="1df448c">The <span class="code">E&lt;&gt;</span> code can also be specified with an alternate display text (before the entity specification and separated from it by a <span class="code">|</span>). When an alternate text is specified, it is used if the specified entity cannot be represented by the renderer (e.g. if the renderer only supports ASCII). </p>
 <p id="c82f38e">For example: </p>
 
                 <div class="raku-code">
@@ -3143,7 +3133,7 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
 </div>
                 </div>
             <p id="4b08248">Note, however that the <span class="code">V&lt;&gt;</span> code only changes the way its contents are parsed, <span class="important">not</span> the way they are rendered. That is, the contents are still wrapped and formatted like plain text, and the effects of any markup instructions surrounding the <span class="code">V&lt;&gt;</span> code are still applied to its contents. For example the previous example is rendered as: </p>
-<div class="nested"><p id="496c253">The <span class="basis"> V&lt;&gt; </span> markup instruction disarms other codes such as  I&lt;&gt;, C&lt;&gt;, B&lt;&gt;, and M&lt;|&gt; . </p></div>
+<div class="nested"><p id="8b7526a">The <span class="basis"> V&lt;&gt; </span> markup instruction disarms other codes such as  I&lt;&gt;, C&lt;&gt;, B&lt;&gt;, and M&lt;&gt; . </p></div>
 <p id="6fa69fe">Note that <span class="code">C&lt;&gt;</span> also by default keeps its contents verbatim, the difference between <span class="code">C&lt;&gt;</span> and <span class="code">V&lt;&gt;</span> is that <span class="code">C&lt;&gt;</span> 'colors' the contents to show that it is code, whilst <span class="code">V&lt;&gt;</span> uses the default text presentation. </p>
 <p id="abb77c3">The default behaviors of both <span class="code">V&lt;&gt;</span> and <span class="code">C&lt;&gt;</span> can be changed using a <span class="code">=config</span> directive, e.g., </p>
 
@@ -3157,14 +3147,14 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
                 </div>
             
 <div class="id-target" id="Indexing terms"></div><h3 id="Indexing_terms" class="heading py-2 "><a href="#" title="go to top of document">Indexing terms</a><a class="raku-anchor" title="direct link" href="#Indexing terms">§</a></h3>
-<p id="b21b227">Anything enclosed in an <span class="code">X&lt;|&gt;</span> code is an <span class="basis">index entry</span>. The contents of the code are both formatted into the document and used as the (case-insensitive) index entry: </p>
+<p id="4dc9ca8">Anything enclosed in an <span class="code">X&lt;&gt;</span> code is an <span class="basis">index entry</span>. The contents of the code are both formatted into the document and used as the (case-insensitive) index entry: </p>
 
                 <div class="raku-code">
                     <button class="copy-code" title="Copy code"><i class="far fa-clipboard"></i></button>
                     <label><b>allow</b> styling</label>
                     <div><pre class="nohighlights">
-An <span class="basis">X&lt;array|&gt;</span> is an ordered list of scalars indexed by number,
-starting with 0. A <span class="basis">X&lt;hash|&gt;</span> is an unordered collection of scalar
+An <span class="basis">X&lt;array&gt;</span> is an ordered list of scalars indexed by number,
+starting with 0. A <span class="basis">X&lt;hash&gt;</span> is an unordered collection of scalar
 values indexed by their associated string key.
 </pre>
 </div>
@@ -3222,7 +3212,7 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
 <div class="id-target" id="Markup extras"></div><h3 id="Markup_extras" class="heading py-2 "><a href="#" title="go to top of document">Markup extras</a><a class="raku-anchor" title="direct link" href="#Markup extras">§</a></h3>
 <p id="90e7fce">In order to allow for renderers to add customisable markup code, whilst at the same time abiding by the <a href="#Naming_rules">naming rules</a>, the markup instruction <span class="code">M&lt; visible text | list-of-strings &gt;</span> is defined as a <span class="important">built-in</span> markup instruction. </p>
 <p id="889a949">The <span class="replace">visible text</span> is shown in the text, and may be blank. </p>
-<p id="9e8b8a9">The <span class="replace">list-of-strings</span> is specified in the same way as the <span class="code">X&lt;|&gt;</span> markup instruction for <a href="#Indexing_entries">indexing</a>. The semantics of the string is defined by the renderer. If a renderer does not recognise the list of strings, it is expected that the visible text will be rendered and marked in some way (such as with a border or highlight color), and at least the first string will be made available in the same way as the <span class="code">D&lt;|&gt;</span> markup instruction. It is also recommended that the first string is used by the renderer to identify the functionality being provided. </p>
+<p id="c36b132">The <span class="replace">list-of-strings</span> is specified in the same way as the <span class="code">X&lt;&gt;</span> markup instruction for <a href="#Indexing_entries">indexing</a>. The semantics of the string is defined by the renderer. If a renderer does not recognise the list of strings, it is expected that the visible text will be rendered and marked in some way (such as with a border or highlight color), and at least the first string will be made available in the same way as the <span class="code">D&lt;&gt;</span> markup instruction. It is also recommended that the first string is used by the renderer to identify the functionality being provided. </p>
 <p id="ee4ec60">For example, suppose a RakuDoc document is used to create part of a website in which a button is to be styled that accesses the API of a payment service (e.g. 'PayMe'). A developer can then create some functionality according to the rules of a RakuDoc renderer, and present it to the service point. In an HTML document, this might be coded as a <span class="code"> &lt;button class="PayMeApp" data-token="vendor-id" data-price="$0.99"&gt; </span> with a specific class and structure. The RakuDoc instruction might then be: </p>
 
                 <div class="raku-code">
@@ -3331,9 +3321,8 @@ <h3 id="Replaceable" class="heading py-2 "><a href="#" title="go to top of docum
 
 
 <h1 id="Summary" class="heading py-2 "><a href="#" title="go to top of document">Summary</a><a class="raku-anchor" title="direct link" href="#Summary">§</a></h1>
-
-<div class="id-target" id="Directives"></div><h2 id="Directives_0" class="heading py-2 "><a href="#" title="go to top of document">Directives</a><a class="raku-anchor" title="direct link" href="#Directives">§</a></h2>
-<table class="table is-striped is-bordered"><tbody class="procedural">
+<div id="Directives_0"></div>
+<table class="table is-striped is-bordered"><caption>Directives</caption><tbody class="procedural">
 <tr class="procedural"><th class="">Directive</th><th class="">Specifies</th></tr>
 <tr class="procedural"><td class=""><p id="97bb7d2">=alias </p></td><td class="">Define a RakuDoc macro</td></tr>
 <tr class="procedural"><td class=""><p id="c680290">=begin </p></td><td class="">Start of an explicitly terminated block</td></tr>
@@ -3344,8 +3333,8 @@ <h1 id="Summary" class="heading py-2 "><a href="#" title="go to top of document"
 <tr class="procedural"><td class=""><p id="9da80e9">=for </p></td><td class="">Start of an implicitly (blank-line) terminated block</td></tr>
 <tr class="procedural"><td class=""><p id="464ac6b">=row </p></td><td class="">Start a new row in a procedural table</td></tr>
 </tbody></table>
-<h2 id="Blocks" class="heading py-2 "><a href="#" title="go to top of document">Blocks</a><a class="raku-anchor" title="direct link" href="#Blocks">§</a></h2>
-<table class="table is-striped is-bordered"><tbody class="procedural">
+<div id="Blocks"></div>
+<table class="table is-striped is-bordered"><caption>Blocks</caption><tbody class="procedural">
 <tr class="procedural"><th class="">Block typename</th><th class="">Specifies</th></tr>
 <tr class="procedural"><td class=""><p id="2bcef59">=cell </p></td><td class="">Contents of a table cell, only valid in a procedural table context</td></tr>
 <tr class="procedural"><td class=""><p id="a75b87f">=code </p></td><td class="">Verbatim pre-formatted sample source code</td></tr>
@@ -3372,9 +3361,8 @@ <h2 id="Blocks" class="heading py-2 "><a href="#" title="go to top of document">
 <tr class="procedural"><td class="">RESERVED</td><td class="">Semantic blocks (SYNOPSIS, TITLE, etc.)</td></tr>
 <tr class="procedural"><td class="">CustomName</td><td class="">User-defined block</td></tr>
 </tbody></table>
-
-<div class="id-target" id="Metadata options"></div><h2 id="Metadata_options" class="heading py-2 "><a href="#" title="go to top of document">Metadata options</a><a class="raku-anchor" title="direct link" href="#Metadata options">§</a></h2>
-<table class="table is-striped is-bordered"><tbody class="procedural">
+<div id="Metadata_options"></div>
+<table class="table is-striped is-bordered"><caption>Metadata options</caption><tbody class="procedural">
 <tr class="procedural"><th class="">Metadata option</th><th class="">Blocks applied to</th><th class="">Description</th></tr>
 <tr class="procedural"><td rowspan="4" class="procedural-cell-middle "><p id="8231a83"><span class="code">:allow</span> </p></td><td class=""><p id="4630a00"><span class="code">=code</span> </p></td><td rowspan="4" class="procedural-cell-middle ">Change default of verbatim blocks</td></tr>
 <tr class="procedural"><td class=""><p id="15d964d"><span class="code">=input</span> </p></td></tr>
@@ -3414,7 +3402,7 @@ <h2 id="Blocks" class="heading py-2 "><a href="#" title="go to top of document">
 <tr class="procedural"><td class=""><p id="9181c50"><span class="code">=table</span> </p></td></tr>
 <tr class="procedural"><td class=""><p id="4eab40d"><span class="code">=formula</span> </p></td></tr>
 <tr class="procedural"><td class=""><p id="068023f"><span class="code">=place</span> </p></td></tr>
-<tr class="procedural"><td class=""><p id="7c857a9"><span class="code">:hidden</span> </p></td><td class="">Semantic block</td><td class=""><p id="16e74a4">Remove block from rendered text and ToC (use <span class="code">P&lt;semantic: ...|&gt;</span> to inject elsewhere) </p></td></tr>
+<tr class="procedural"><td class=""><p id="7c857a9"><span class="code">:hidden</span> </p></td><td class="">Semantic block</td><td class=""><p id="bef4323">Remove block from rendered text and ToC (use <span class="code">P&lt;semantic: ...&gt;</span> to inject elsewhere) </p></td></tr>
 <tr class="procedural"><td rowspan="4" class=""><p id="f3fe198"><span class="code">:header</span> </p></td><td class=""><p id="7ad3351"><span class="code">=table</span> (procedural semantics only) </p></td><td rowspan="4" class="">Specify rows, columns, or cells to be rendered as headers</td></tr>
 <tr class="procedural"><td class=""><p id="392c0ce"><span class="code">=cell</span> </p></td></tr>
 <tr class="procedural"><td class=""><p id="ad2996f"><span class="code">=row</span> directive </p></td></tr>
@@ -3440,29 +3428,28 @@ <h2 id="Blocks" class="heading py-2 "><a href="#" title="go to top of document">
 <tr class="procedural"><td class=""><p id="3e4e666"><span class="code">=numheadN</span> </p></td></tr>
 <tr class="procedural"><td class="">Semantic block</td></tr>
 <tr class="procedural"><td class="">Custom block</td></tr>
-<tr class="procedural"><td class=""><p id="04309b4"><span class="code">:bullet&lt;CHAR&gt;</span> </p></td><td class=""><p id="addd10d"><span class="code">=itemN</span> </p></td><td class=""><p id="be2beac">Replace the default bullet with one or more characters, or entities specified with <span class="code">E&lt; |&gt;</span> </p></td></tr>
+<tr class="procedural"><td class=""><p id="04309b4"><span class="code">:bullet&lt;CHAR&gt;</span> </p></td><td class=""><p id="addd10d"><span class="code">=itemN</span> </p></td><td class=""><p id="2f53082">Replace the default bullet with one or more characters, or entities specified with <span class="code">E&lt; &gt;</span> </p></td></tr>
 </tbody></table>
-
-<div class="id-target" id="Markup instructions"></div><h2 id="Markup_instructions_0" class="heading py-2 "><a href="#" title="go to top of document">Markup instructions</a><a class="raku-anchor" title="direct link" href="#Markup instructions">§</a></h2>
-<table class="table is-striped is-bordered"><tbody class="procedural">
+<div id="Markup_instructions_0"></div>
+<table class="table is-striped is-bordered"><caption>Markup instructions</caption><tbody class="procedural">
 <tr class="procedural"><th class="">Markup instruction</th><th class="">Specifies</th></tr>
-<tr class="procedural"><td class=""><p id="0d06a81">A&lt;...|...|&gt; </p></td><td class=""><p id="7794551">Alias to be replaced by contents of specified =alias directive </p></td></tr>
+<tr class="procedural"><td class=""><p id="d7ff7d0">A&lt;...|...&gt; </p></td><td class=""><p id="7794551">Alias to be replaced by contents of specified =alias directive </p></td></tr>
 <tr class="procedural"><td class=""><p id="0849280">B&lt;...&gt; </p></td><td class="">Basis/focus of sentence (typically rendered bold)</td></tr>
 <tr class="procedural"><td class=""><p id="d75ee78">C&lt;...&gt; </p></td><td class="">Code (typically rendered fixed-width)</td></tr>
-<tr class="procedural"><td class=""><p id="347ef79">D&lt;...|&gt; </p></td><td class=""><p id="139ccf8">Definition inline (D&lt;term being defined|synonym1; synonym2|&gt;) </p></td></tr>
-<tr class="procedural"><td class=""><p id="095b809">Δ&lt;...|...;...|&gt; </p></td><td class=""><p id="72c231a">Delta note (Δ&lt;visible text|version; Notification text|&gt;) </p></td></tr>
+<tr class="procedural"><td class=""><p id="41b26c6">D&lt;...&gt; </p></td><td class=""><p id="e64371d">Definition inline (D&lt;term being defined|synonym1; synonym2&gt;) </p></td></tr>
+<tr class="procedural"><td class=""><p id="48ead63">Δ&lt;...|...;...&gt; </p></td><td class=""><p id="ee9cd9b">Delta note (Δ&lt;visible text|version; Notification text&gt;) </p></td></tr>
 <tr class="procedural"><td class=""><p id="17404a2"> E&lt;...|...;...&gt; </p></td><td class=""><p id="27c2b6a">Entity (HTML or Unicode) description ( E&lt;entity1;entity2; multi,glyph;...&gt;) </p></td></tr>
-<tr class="procedural"><td class=""><p id="b29528f">F&lt;...|...|&gt; </p></td><td class=""><p id="c9ad74d">Inline content for a formula (F&lt;ALT|LaTex notation|&gt;) </p></td></tr>
+<tr class="procedural"><td class=""><p id="1d1bdee">F&lt;...|...&gt; </p></td><td class=""><p id="d876e61">Inline content for a formula (F&lt;ALT|LaTex notation&gt;) </p></td></tr>
 <tr class="procedural"><td class=""><p id="a64e5e6">G&lt;...&gt; </p></td><td class="">(This markup code is not yet defined, but is reserved for future use)</td></tr>
 <tr class="procedural"><td class=""><p id="db9161f">H&lt;...&gt; </p></td><td class="">High text (typically rendered superscript)</td></tr>
 <tr class="procedural"><td class=""><p id="4ddef78">I&lt;...&gt; </p></td><td class="">Important (typically rendered in italics)</td></tr>
 <tr class="procedural"><td class=""><p id="54b222c">J&lt;...&gt; </p></td><td class="">Junior text (typically rendered subscript)</td></tr>
 <tr class="procedural"><td class=""><p id="c4e911d">K&lt;...&gt; </p></td><td class="">Keyboard input (typically rendered fixed-width)</td></tr>
-<tr class="procedural"><td class=""><p id="3be6f31">L&lt;...|...|&gt; </p></td><td class=""><p id="427d844">Link (L&lt;display text|destination URI|&gt;) </p></td></tr>
-<tr class="procedural"><td class=""><p id="6a65897">M&lt;...|..,..;...|&gt; </p></td><td class=""><p id="7b1ea07">Markup extra (M&lt;display text|functionality;param,sub-type;...|&gt;) </p></td></tr>
+<tr class="procedural"><td class=""><p id="611b767">L&lt;...|...&gt; </p></td><td class=""><p id="23e7b87">Link (L&lt;display text|destination URI&gt;) </p></td></tr>
+<tr class="procedural"><td class=""><p id="ce68e29">M&lt;...|..,..;...&gt; </p></td><td class=""><p id="b928fc8">Markup extra (M&lt;display text|functionality;param,sub-type;...&gt;) </p></td></tr>
 <tr class="procedural"><td class=""><p id="4500809">N&lt;...&gt; </p></td><td class="">Note (not rendered inline, but visible in some way: footnote, sidenote, pop-up, etc.))</td></tr>
 <tr class="procedural"><td class=""><p id="1c73c4f">O&lt;...&gt; </p></td><td class="">Overstrike or strikethrough</td></tr>
-<tr class="procedural"><td class=""><p id="00bd7ca">P&lt;...|...|&gt; </p></td><td class="">Placement link</td></tr>
+<tr class="procedural"><td class=""><p id="f1583b7">P&lt;...|...&gt; </p></td><td class="">Placement link</td></tr>
 <tr class="procedural"><td class=""><p id="5198805">Q&lt;...&gt; </p></td><td class="">(This markup code is not yet defined, but is reserved for future use)</td></tr>
 <tr class="procedural"><td class=""><p id="554002e">R&lt;...&gt; </p></td><td class="">Replaceable component or metasyntax</td></tr>
 <tr class="procedural"><td class=""><p id="9aef84b">S&lt;...&gt; </p></td><td class="">Space characters to be preserved</td></tr>
@@ -3470,7 +3457,7 @@ <h2 id="Blocks" class="heading py-2 "><a href="#" title="go to top of document">
 <tr class="procedural"><td class=""><p id="128bc17">U&lt;...&gt; </p></td><td class="">Unusual (typically rendered with underlining)</td></tr>
 <tr class="procedural"><td class=""><p id="9ed6f84">V&lt;...&gt; </p></td><td class="">Verbatim (internal markup instructions ignored)</td></tr>
 <tr class="procedural"><td class=""><p id="7544071">W&lt;...&gt; </p></td><td class="">(This markup code is not yet defined, but is reserved for future use)</td></tr>
-<tr class="procedural"><td class=""><p id="b368fe2">X&lt;...|..,..;...|&gt; </p></td><td class=""><p id="ad2482f">Index entry (X&lt;display text|entry,subentry;...|&gt;) </p></td></tr>
+<tr class="procedural"><td class=""><p id="aaa3427">X&lt;...|..,..;...&gt; </p></td><td class=""><p id="a7ffbf1">Index entry (X&lt;display text|entry,subentry;...&gt;) </p></td></tr>
 <tr class="procedural"><td class=""><p id="9958cde">Y&lt;...&gt; </p></td><td class="">(This markup code is not yet defined, but is reserved for future use)</td></tr>
 <tr class="procedural"><td class=""><p id="3de4df1">Z&lt;...&gt; </p></td><td class="">Zero-width comment (contents never rendered)</td></tr>
 </tbody></table>
@@ -3492,22 +3479,22 @@ <h2 class="footnote-caption">Footnotes</h2>
     <div class="container px-4">
         <nav class="level">
             <div class="level-item">
-                Rendered from <span class="footer-field">./rakudoc_draft_3.rakudoc/rakudoc_draft_3
+                Rendered from <span class="footer-field">./rakudoc_v2.rakudoc/rakudoc_v2
             </div>
             <div class="level-item">
-                Rendered at 14:44 UTC on 2024-12-30
+                Rendered at 10:50 UTC on 2025-01-15
             </div>
             <div class="level-item">
-                Source last modified at 14:42 UTC on 2024-12-30
+                Source last modified at 22:38 UTC on 2025-01-13
             </div>
         </nav>
     </div>
     <div class="section"><div class="container px-4 warnings">    <div class="warnings">
     <h2 class="warnings-caption">Warnings</h2>
         <ol>
-        <li>Unknown or as yet undeclared alias ｢this program ｣ in block ｢rakudoc｣ with heading ｢Aliases｣</li>
-<li>Unknown or as yet undeclared alias ｢our company ｣ in block ｢rakudoc｣ with heading ｢Aliases｣</li>
-<li>Unknown or as yet undeclared alias ｢(Please visit our website) ｣ in block ｢rakudoc｣ with heading ｢Aliases｣</li>
+        <li>Unknown or as yet undeclared alias ｢ SOFTWARE｣ in block ｢rakudoc｣ with heading ｢Aliases｣ over-riden by ｢this program ｣</li>
+<li>Unknown or as yet undeclared alias ｢ COMPANY｣ in block ｢rakudoc｣ with heading ｢Aliases｣ over-riden by ｢our company ｣</li>
+<li>Unknown or as yet undeclared alias ｢ OURTERMS｣ in block ｢rakudoc｣ with heading ｢Aliases｣ over-riden by ｢(Please visit our website) ｣</li>
 <li>Definition ｢AAA｣ has been redefined in block ｢rakudoc｣ with heading ｢Numbered definitions｣.</li>
 <li>Definition ｢BBB｣ has been redefined in block ｢rakudoc｣ with heading ｢Numbered definitions｣.</li>
 <li>Definition ｢XXX｣ has been redefined in block ｢rakudoc｣ with heading ｢Numbered definitions｣.</li>