nav/ask: Apply 2022 template

nav/ask.html

@@ -34,9 +34,9 @@
 <script src="about-data/translations.js"> </script>
 <script src="../javascript/doc-structure/article-dt.js"> </script>
 <script src="../javascript/boilerplate-text/boilerplate-en.js"></script><!--TRANSLATORS must change -en to the subtag for their language!-->
-<script src="../javascript/doc-structure/sitepage.js"> </script>
-<script src="../javascript/articletoc-html5.js"></script>
-<link rel="stylesheet" href="../style/sitepage-2016.css" />
+<script src="../javascript/doc-structure/sitepage-2022.js"> </script>
+<script src="../javascript/articletoc-2022.js"></script>
+<link rel="stylesheet" href="../style/sitepage-2022.css" />
 <link rel="copyright" href="#copyright"/>
 <style media="all">
 .articles { list-style-type: none; }
@@ -59,16 +59,21 @@ <h1>Ask for help or information</h1>
 <h2 id="i18n" class="notoc"><a href="#i18n">What is 'i18n'?</a></h2>
 <p>'i18n' is an industry standard abbreviation for 'internationalization' (because there are 18 letters between the 'i' and the 'n').</p>
 </section>
-<section>
-<h2 id="specreview"><a href="#specreview">How can I get you to review our spec?</a></h2>
+
+
+
+
+
+<section id="specreview">
+<h2>How can I get you to review our spec?</h2>
 <p>See our <a href="https://www.w3.org/International/review-request" class="eyecatcher">Request a review</a> page.</p>
 </section>
 
 
 
 
-<section>
-<h2 id="contact"><a href="#contact">How can I contact you for other things?</a></h2>
+<section id="contact">
+<h2>How can I contact you for other things?</h2>
 <p>Because it has many benefits, we try to conduct all discussions about documents or other technical questions via GitHub issues.</p>
 <p>If your question or comment relates to one of our articles or documents, please use the relevant github issues list. There should be a pointer to the appropriate issue list in the document or page itself.</p>
   <p>If you are in a W3C group and want to  ask us a question about one of your  documents, the best way to alert us is to add the question to an issue (or create an issue if needed), in your document's GitHub repo and add the <code class="kw" translate="no">i18n-tracking</code> label to it if it's not already there. We'll be notified. This approach is particularly useful since it keeps discussion threads linked to existing discussions and to appropriate repos.</p>
@@ -79,14 +84,14 @@ <h2 id="contact"><a href="#contact">How can I contact you for other things?</a><
 
 
 
-<section>
-<h2 id="contacts"><a href="#contacts">Who can I contact?</a></h2>
-			<ul>
-				<li><a href="mailto:addison@amazon.com">Addison Phillips (addison @ amazon.com)</a>, I18n Core Working Group Chair</li>
-				<li><a href="mailto:ishida@w3.org">Richard Ishida (ishida @ w3.org)</a>, Activity Lead, Staff Contact for Core Working Group</li>
+<section id="contacts">
+<h2>Who can I contact?</h2>
+<ul>
+    <li><a href="mailto:addison@amazon.com">Addison Phillips (addison @ amazon.com)</a>, I18n Core Working Group Chair</li>
+    <li><a href="mailto:ishida@w3.org">Richard Ishida (ishida @ w3.org)</a>, Activity Lead, Staff Contact for Core Working Group</li>
 <li><a href="mailto:duerst@it.aoyama.ac.jp">Martin Dürst (duerst @ it.aoyama.ac.jp)</a>, Interest Group Chair</li>
-				<li><a href="http://www.w3.org/International/Group/#liaison">Liaisons</a> (member only)</li>
-			</ul>
+    <li><a href="http://www.w3.org/International/Group/#liaison">Liaisons</a> (member only)</li>
+</ul>
 </section>