minor tweaks for new group guide

tools/new-group.html

@@ -51,15 +51,15 @@ <h1>How to setup a new Working Group or Interest Group</h1></div>
   </p>
 
 
-<h2 id="administrivia">Administriva repository</h2>
+<h2 id="administrivia">Administrivia repository</h2>
 
 <p>
   Having an administrivia repository allows to track and maintain potential
   non-technical documents used by the group, such as:
 </p>
 <ul>
   <li>group process/policies</li>
-  <li>meeting agendas, minutes, logitics</li>
+  <li>meeting agendas, minutes, logistics</li>
   <li>invited expert expectations</li>
   <li>milestones</li>
   <li>homepage</li>
@@ -90,7 +90,7 @@ <h2 id="repositories">Github repositories</h2>
 
 <p>
   All GitHub repositories used by the group must indicate so, using the <a href="https://w3c.github.io/w3c.json.html"><code>w3c.json</code> file</a> in those repositories. If you do not use the GitHub 'w3c' organization,
-  make sure the Team associates your GitHub organization in the 'Version Control' entry of the Tools page (Team may modify those entries using the w3.org/admin interface) and the tooling
+  make sure the Team associates your GitHub organization in the 'Version Control' entry of the Tools page (Team may modify those entries using the <a href="https://w3.org/admin">admin</a> interface) and the tooling
   will associate <em>by default</em> all of the repositories in your GitHub organization to your group.
 </p>
 <p>
@@ -163,7 +163,8 @@ <h2 id="agenda">Agenda</h2>
 
 <h2 id="chairs-and-tcs">Chairs and Team Contacts</h2>
 <p>
-  The Team must ensure that Chairs and Team Contacts are appropriately identify in the <a href='https://www.w3.org/groups/'>Group pages</a>.
+  The Team must ensure that Chairs and Team Contacts are appropriately identify in the <a href='https://www.w3.org/groups/'>Group pages</a>
+  (Team should use the <a href="https://w3.org/admin">admin</a> interface to do so).
   Chairs and Team Contacts may want to schedule a regular (weekly, bi-weekly, monthly, quaterly?) meeting to sync-up and track group progress.
 </p>
 <p>
@@ -180,7 +181,7 @@ <h2 id="invited-experts">Invited Experts</h2>
 <p>
   Invited expert approvals may include a paragraph or two to clarify the expectations to maintain the status, such as:
 </p>
-<p>In <code>.github/ISSUE_TEMPLATE/invited-experts.md</code>:</p>
+<p>In <code>invited-experts.md</code>:</p>
 <div class="example">
   <p>We generally welcome anyone interested in working on and improving [topic] on the Web.
     However, we expect [group] participants to contribute, which can take the form of participating