Tweak varoius bits to be consistent.

docs/website/clients/Chandler-details.php

@@ -2,14 +2,17 @@
 <p>The <a href="http://www.osafoundation.org/">Open Source Applications Foundation</a> are developing <a href="http://cosmo.osafoundation.org/">Cosmo</a>, which is a CalDAV server
 written in Java and <a href="http://chandler.osafoundation.org/">Chandler</a>, which is a CalDAV capable mail and calendaring application
 written in Python.</p>
+
 <p>Basic setup is as follows:</p>
+
 <ol>
 <li>Select "Subscribe" from the "Collection" menu.</li>
 <li>Enter a URL like: "http://calendar.example.net/caldav.php/username/home/" (click "Subscribe") <img src="clients/Chandler-dialog1.png" /> <br /> &nbsp;</li>
 <li>You will then be prompted for a username/password with in an expanded dialog.  Enter these and click "Subscribe" again. <img src="clients/Chandler-dialog2.png" /> <br /> &nbsp;</li>
 <li>You should now have a new calendar showing.</li>
 </ol>
-<h3>Caveats</h3>
+
+<h2>Caveats</h2>
 <p><img align="right" src="clients/Chandler-dialog3.png" />At version 0.7alpha3 the calendar is subscribed and displayed, but the 'displayname' property
 which the server sends is not used and the calendar is displayed with a blank name.  Double-click
 on your new calendar and enter a name in the space available. </p>

docs/website/clients/Evolution-details.php

@@ -8,10 +8,12 @@ was little in the way of a repository available to test against until recently.<
 <li>Choose a type of "CalDAV", enter a name, and a URL such as <code>caldav://server.domain.name/caldav.php/username/home/</code>, enter your user name for RSCDS and click "OK".<img src="clients/Evolution-dialog1.png" /> <br />&nbsp;</li>
 <li>You should now be prompted for a password for that username.  Enter the password and your calendar should now show.</li>
 </ol>
+
+<h2>Caveats</h2>
 <p>If you have problems with Evolution, you will need to quit evolution, remove the cache file which will be in ~/.evolution/cache/calendar/ and
 restart.  If you still have problems try doing that, but killing evolution-data-server in addition.
 </p>
-<p>Sometimes evolution writes error messages into the cache file, so if you have ongoing problems you may want to
+<p>Sometimes Evolution writes error messages into the cache file, so if you have ongoing problems you may want to
 take a look inside that.</p>
 <p>There are some quirks with Evolution's handling of CalDAV too, so perhaps take a look at the following
 bugs:</p>

docs/website/clients/Interoperability-details.php

@@ -3,17 +3,19 @@
 then you should attempt to structure the URLs which they use to access the system in the way
 that Mulberry does it.</p>
 <p>Basically, Mulberry breaks the URL into three parts:</p>
+
 <ul>
 <li>The host name</li>
 <li>The root path</li>
 <li>Calendar namespace</li>
 </ul>
+
 <p>The host name is, of course, up to you.  The 'root path' should be <code>/caldav.php/</code> and anything following that is the calendar namespace.</p>
 <p>Within the calendar namespace RSCDS uses the first element of the path as the user or resource name, so that a client connecting at the root path
 can see all of the (accessible) users and resources available to them (Mulberry displays this hierarchy) with any calendars below that.</p>
 <p>Effectively this means that in Evolution, Sunbird and Lightning you should really specify a calendar URL which is something like:</p>
 <pre>
-caldav://calendar.example.net/caldav.php/username/home/
+http://calendar.example.net/caldav.php/username/home/
 </pre>
 <p>Then, when more calendar client software sees it as useful to be able to browse that hierarchy, you won't be up for any heavy database manipulation.</p>
 <p>I may well enforce this standard in some way before release 1.0, as well as auto-creating the <code>collection</code> records when Evolution, Lightning

docs/website/clients/Mozilla-details.php

@@ -4,6 +4,7 @@
  application, and <em><a href="http://www.mozilla.org/projects/calendar/lightning/">Lightning</a></em> is a Thunderbird extension.
  The two are essentially the same, as far as RSCDS is
  concerned, and these instructions should work for either of them.</p>
+
 <ol>
 <li>Select "New Calendar" from the "File" menu.</li>
 <li>Choose "On the Network" (click "Next")<img src="clients/Mozilla-dialog1.png" /> <br /> &nbsp;</li>
@@ -11,6 +12,7 @@
 <li>Give the calendar an appropriate display name, and choose a colour for events on this calendar. (click "Next")<img src="clients/Mozilla-dialog3.png" /> <br /> &nbsp;</li>
 <li>click "Finish"</li>
 </ol>
+
 <h2>Caveats</h2>
 <p>At version 0.3 the Mozilla calendar does not automatically refresh the calendar view, so if someone else has
 added a meeting you will have to manually refresh the view to see that.</p>

docs/website/clients/Mulberry-details.php

@@ -19,7 +19,7 @@ PROPFIND requests.</p>
 <li>Once you have a calendar created, you need to <em>subscribe to it.  One way is to right-click on it and choose 'Subscribe'.</em></li>
 </ol>
 
-<h3>Caveats</h3>
+<h2>Caveats</h2>
 <p>Unfortunately Mulberry is not (yet) open-source, though it is free, so we must wait on the developer to fix
 the user interface niggles when he gets around to it.</p>
 <p>Note that Mulberry has a complex user interface.  When I wrote this I went back into Mulberry and initially