diff --git a/inbox/mix.xml b/inbox/mix.xml
index 040f1a3c..9c4a85b5 100644
--- a/inbox/mix.xml
+++ b/inbox/mix.xml
@@ -418,14 +418,6 @@
       <p></p>
         <example caption="" ><![CDATA[
 
-]]></example>
-    </section3>
-
-
-    <section3 topic='' anchor='usecase-admin-'>
-      <p></p>
-        <example caption="" ><![CDATA[
-
 ]]></example>
     </section3>
 
@@ -435,7 +427,7 @@
 
 <section1 topic='Configuration options' anchor='config'>
   <section2 topic='Transparency' anchor="config-transparency">
-    <p>TODO: SemiAnon/NonAnom</p>
+    <p>TODO: transparent vs. opaque conversations</p>
   </section2>
 </section1>
 
@@ -449,26 +441,35 @@
 </section1>
 <section1 topic='Accessibility Considerations' anchor='access'>
   <p>OPTIONAL.</p>
-</section1>
-<section1 topic='Internationalization Considerations' anchor='i18n'>
-  <p>OPTIONAL.</p>
 </section1>-->
+<section1 topic='Internationalization Considerations' anchor='i18n'>
+  <p>TBD.</p>
+  <p>Discuss normalization of nicknames.</p>
+</section1>
 <section1 topic='Security Considerations' anchor='security'>
-  <p>This specification doesn't add additional security considerations beyond those of its dependencies.</p>
+  <p>TBD.</p>
+  <p>Topics to cover:</p>
+  <ul>
+    <li>transparent vs. opaque conversations</li>
+    <li>nickname registration and security implications of normalization</li>
+  </ul>
 </section1>
 <section1 topic='IANA Considerations' anchor='iana'>
   <p>None.</p>
 </section1>
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
-  <p>Needs a namespace.</p>
+  <p>Register a namespace.</p>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>
   <p>TBD.</p>
 </section1>
+<section1 topic='Acknowledgements' anchor='ack'>
+  <p>Thanks to the participants in XMPP Summit 18 for their significant input during design sessions: Dave Cridland, Philipp Hancke, Waqas Hussain, Lance Stout, Sam Whited, and Matthew Wild.</p>
+</section1>
 </xep>
 
 <!--TODO: Query whole service for MAM. Provide data form for filtering by node ID.
 TODO: Two config nodes - one public read one private read?
 TODO: Open Issue: How many config nodes do you need? Do you do different access to different items within a node for reading? Writing?
-TODO: Subscription option to check conversation config (e.g. anonymity) before join.
+TODO: Subscription option to check conversation config (e.g. transparency of JIDs) before join.
 -->