Update website to reflect new default calendar name.

docs/website/clients/Chandler-details.php

@@ -7,7 +7,7 @@ written in Python.</p>
 
 <ol>
 <li>Select "Subscribe" from the "Share" menu (or in older builds it was in 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>Enter a URL like: "http://calendar.example.net/caldav.php/username/calendar/" (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>

docs/website/clients/Evolution-details.php

@@ -5,7 +5,7 @@ was little in the way of a repository available to test against until recently.<
 
 <ol>
 <li>Select "File" then "New" then "Calendar" from the menus.</li>
-<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 DAViCal and click "OK".<img src="clients/Evolution-dialog1.png" /> <br />&nbsp;</li>
+<li>Choose a type of "CalDAV", enter a name, and a URL such as <code>caldav://server.domain.name/caldav.php/username/calendar/</code>, enter your user name for DAViCal 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>
 

docs/website/clients/Interoperability-details.php

@@ -10,13 +10,25 @@ that Mulberry does it.</p>
 <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 DAViCal 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>
+<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 DAViCal uses the first element of the 
+path as the user or 'princpal' 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>This means that in Evolution, Lightning and other software wanting a
+'calendar' URL you should specify a URL which is something like:</p>
 <pre>
-http://calendar.example.net/caldav.php/username/home/
+http://calendar.example.net/caldav.php/username/calendar/
 </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
-or Sunbird attempt to store to a non-existent collection.</p>
+
+<p>DAViCal creates two collections automatically when a user is created.  In
+recent versions these are called 'calendar' and 'addressbook'.  Some software
+also makes it easy to create more calendars and addressbooks, or you can create
+more through DAViCal's web interface, also.</p>
+
+<p>In older versions of DAViCal (pre 0.9.9.5) the default calendar was named 'home'
+and there was no default addressbook.</p> 

docs/website/clients/Mozilla-details.php

@@ -8,7 +8,7 @@
 <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>
-<li>Choose a format of "CalDAV" and enter a URL like: "http://calendar.example.net/caldav.php/username/home/" (click "Next")<img src="clients/Mozilla-dialog2.png" /> <br /> &nbsp;</li>
+<li>Choose a format of "CalDAV" and enter a URL like: "http://calendar.example.net/caldav.php/username/calendar/" (click "Next")<img src="clients/Mozilla-dialog2.png" /> <br /> &nbsp;</li>
 <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>

docs/website/clients/Other-details.php

@@ -6,3 +6,24 @@ against, but so far these are the only ones I have access to.</p>
 <p>If you want to point me at more free software that supports CalDAV, or
 send me free copies of such proprietary software, then I will add it to
 the list as well as make DAViCal work with it.</p>
+
+<p>In the general CalDAV terminology, client software will want to know
+several facts about the CalDAV server.  Some (like iCal and iOS) will try
+and discover these facts for themselves, and others (like Lightning and
+Evolution) will require you to enter some information.  When they ask for
+that information they will be asking for the following things:</p>
+<ol>
+<li>Where is the user's "home" collection?</li>
+<li>Where is the user's "calendar" collection?</li>
+<li>What is the server's domain name</li>
+</ol>
+
+<p>Typically the answers, in DAViCal's case, are:</p>
+<ol>
+<li>.../caldav.php/username/</li>
+<li>.../caldav.php/username/calendar/ (although in older versions the default calendar was called 'home' rather than 'calendar')</li>
+<li>I can't help here - whatever you called it, I guess!</li>
+</ol>
+
+<p>There could well be a wider range of information about many and varied client
+ software on the <a href="http://wiki.davical.org/" title="The DAViCal CalDAV Server Wiki">DAViCal Wiki</a> as well.