[Httpunit-commit] CVS: httpunit/sitedocs tutorial.html,1.1,1.2

[Russell G. <rus...@us...>]

Update of /cvsroot/httpunit/httpunit/sitedocs
In directory sc8-pr-cvs1:/tmp/cvs-serv19527/sitedocs

Modified Files:
	tutorial.html 
Log Message:
site cleanup

Index: tutorial.html
===================================================================
RCS file: /cvsroot/httpunit/httpunit/sitedocs/tutorial.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- tutorial.html	18 May 2003 05:20:47 -0000	1.1
+++ tutorial.html	18 May 2003 13:32:29 -0000	1.2
@@ -24,29 +24,30 @@
 
 <p>We will identify the following uses of the system:</p>
 
-<p class="story-name">1.1 Administrator Opens Pool</p>
-<p class="story-contents">The administrator defines up to ten games, specifying the home and away team for each game. He also selects one of
-these games as the tie-breaker. Once the data is correct, the administrator opens the pool for betting.</p>
+<dl class="story-list"><dt>1.1 Administrator Opens Pool</dt>
+<dd>The administrator defines up to ten games, specifying the home and away team for each game. He also selects one of
+these games as the tie-breaker. Once the data is correct, the administrator opens the pool for betting.</dd>
 
-<p class="story-name">1.2 Administrator Closes Pool</p>
-<p class="story-contents">After the pool is open, the administrator may at any time close the pool, thus preventing any
-further bets or changes to existing bets.</p>
+<dt>1.2 Administrator Closes Pool</dt>
+<dd>After the pool is open, the administrator may at any time close the pool, thus preventing any
+further bets or changes to existing bets.</dd>
 
-<p class="story-name">1.3 Administrator Posts Results</p>
-<p class="story-contents">After the pool is closed, the administrator enters actual scores for each of the games played.
-Once all scores have been entered, the administrator posts the results.</p>
+<dt>1.3 Administrator Posts Results</dt>
+<dd>After the pool is closed, the administrator enters actual scores for each of the games played.
+Once all scores have been entered, the administrator posts the results.</dd>
 
-<p class="story-name">2.1 Users enters a bet</p>
-<p class="story-contents">After the pool is open, a user may sign on and create a bet, predicting the winner of each game
-and the total score of the tie-breaker game. The user may change his bet until the pool is closed.</p>
+<dt>2.1 Users enters a bet</dt>
+<dd>After the pool is open, a user may sign on and create a bet, predicting the winner of each game
+and the total score of the tie-breaker game. The user may change his bet until the pool is closed.</dd>
 
-<p class="story-name">2.2 User views results</p>
-<p class="story-contents">Once the results have been posted, a user may examine his own bet to see how well he did. The
-system will indicate the correct predictions and the user's rank in the pool.</p>
+<dt>2.2 User views results</dt>
+<dd>Once the results have been posted, a user may examine his own bet to see how well he did. The
+system will indicate the correct predictions and the user's rank in the pool.</dd>
 
-<p class="story-name">2.3 User views standings</p>
-<p class="story-contents">Once the results have been posted, a user may view a list of all bidders ranked by number of
-correct predictions.</p>
+<dt>2.3 User views standings</dt>
+<dd>Once the results have been posted, a user may view a list of all bidders ranked by number of
+correct predictions.</dd>
+</dl>
 
 <p>This application is fairly simple, and hardly robust, but contains more than enough interactions to allow us to
 explore development and testing with HttpUnit.