diff --git a/ConfigurationControlSpecification.html b/ConfigurationControlSpecification.html
index 1334db9..00bfa3d 100644
--- a/ConfigurationControlSpecification.html
+++ b/ConfigurationControlSpecification.html
@@ -2,8 +2,8 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
 	"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
+<head>
+ <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8" />
  <title>Configuration-Control Specification - work-in-progress</title>
 
 <style type="text/css">  <!-- only for WIP -->
@@ -54,12 +54,12 @@ a:hover {
    Editor: Iang<br />
    Status: 20100420 <i>WIP</i> <br />
   </td><td align="right">
-   <a href="//www.cacert.org/policy/PolicyOnPolicy.html"><img src="Images/cacert-draft.png" alt="CCS Status - work-in-progress" height="31" width="88" style="border-style: none;" /></a>
+   <a href="//www.cacert.org/policy/PolicyOnPolicy.html"><img src="Images/cacert-wip.png" alt="CCS Status - work-in-progress" height="31" width="88" style="border-style: none;" /></a>
   </td>
  </tr>
 </table>
 
-<h3> <a name="s1">1</a> <a name="Introduction"> Introduction </a> </h3>
+<h3 id="s1"> 1. Introduction </h3>
 
 <!-- This section from A.1.a through A.1.c -->
 
@@ -180,11 +180,11 @@ Critical software is defined by Security Policy.
 </p>
 
 <ul class="q">
-<li>One thing that is not so well covered by CAcert is the last bullet point of A.1.i
-<li>"communicating with subscribers and with the general public."
-<li>website is under SP;  maillists,blogs,etc are not.
-<li>as community has deliberately gone this direction, I suggest we argue it that way.
-<li> What is far more problematic is the failure to do CCA & Challenge notification.
+<li>One thing that is not so well covered by CAcert is the last bullet point of A.1.i</li>
+<li>"communicating with subscribers and with the general public."</li>
+<li>website is under SP;  maillists,blogs,etc are not.</li>
+<li>as community has deliberately gone this direction, I suggest we argue it that way.</li>
+<li> What is far more problematic is the failure to do CCA &amp; Challenge notification.</li>
 </ul>
 
 <h4> <a name="s4.2">4.2</a> <a name="soft_change"> Change </a> </h4>
