diff --git a/development/miscdocuments/ServerToolsUseCases.html b/development/miscdocuments/ServerToolsUseCases.html
index b0a4dbf..3e8fb49 100644
--- a/development/miscdocuments/ServerToolsUseCases.html
+++ b/development/miscdocuments/ServerToolsUseCases.html
@@ -40,16 +40,19 @@
   </tr>
 <tr>
 <td>
-<p><b>Principle:</b> We'll consider starting point naive end users who know nothing of
-servers, and they don't care, just want one installed installed so they
-can focus on their web development. We'll consider three levels: 1) User
-does near nothing, 2) user doesn't do much, but may have to provide some
-config values and/or import config values. 3) User has to provide many configvalues, and in the worst cases, actually write ant scripts. </p>
-<p><b>Principle:</b> In addition to "end user" use cases, 
+<p>The purpose of this document is to list explicit use cases for the server tools component. These uses cases can be used to both help guide design (to make sure minimal API is sufficient to support these listed, and only these listed, use cases) and to help guide testing (both unit tests, and milestone/release testing).</p>
+			<P><B>Principle:</B> We'll consider starting point naive end users who
+			know nothing of servers, and they don't care, just want one installed
+			installed so they can focus on their web development. We'll consider
+			three levels: 1) User does near nothing, 2) user doesn't do much, but
+			may have to provide some configuration values and/or import
+			configuration values. 3) User has to provide many configuration
+			values, and in the worst cases, actually write ant scripts.</P>
+			<p><b>Principle:</b> In addition to "end user" use cases, 
 we'll specify &quot;client code&quot; uses-case that may
-simply be specifiying details of function needed for end-user use cases, but
-will always have a unit test associated with it. Also, we'll specfiy "service provider" 
-use cases which can be used to defind SPI's. </p>
+simply be specifying details of function needed for end-user use cases, but
+will always have a unit test associated with it. Also, we'll specify "service provider" 
+use cases which can be used to define SPI's. </p>
 </td>
 </tr>
 <tr> 
@@ -102,7 +105,7 @@
 			(name, version, whether installed or not, etc)</td>
 		</tr>
 		<tr>
-			<td style="width: 108px">run on server</td>
+			<td style="width: 108px">run on J2EE server</td>
 			<td style="width: 60px">1</td>
 			<td style="width: 78px">End-user</td>
 			<td style="width: 360px">user can select a JSP and &quot;run on
@@ -136,7 +139,13 @@
 			</table>
 			</td>
 		</tr>
-		<tr>
+					<TR>
+						<TD style="width: 108px">run on HTTP server</TD>
+						<TD style="width: 60px">1</TD>
+						<TD style="width: 78px">End-user</TD>
+						<TD style="width: 360px">User can select an HTML file, and &quot;run on server&quot;. This use case can be performed with WST only. (This use case has not gotten a lot of discussion, but support for &quot;static projects&quot; is mentioned in WTP/WST vision statement, and is a good case to make sure the architecture and design is correct). </TD>
+					</TR>
+					<tr>
 			<td style="width: 108px">get list of installed servers</td>
 			<td style="width: 60px">1</td>
 			<td style="width: 78px">client programs (unit test)</td>
@@ -161,7 +170,7 @@
 			<td style="width: 108px">Export ANT build scripts for modules</td>
 			<td style="width: 60px">1</td>
 			<td style="width: 78px">End-User</td>
-			<td style="width: 360px">User exports ANT build sxcript that compiles and packages a module in for use outside the Eclipse, possibly for automated builds. </td>
+			<td style="width: 360px">User exports ANT build script that compiles and packages a module in for use outside the Eclipse, possibly for automated builds. </td>
 		</tr>
 		<tr>
 			<td style="width: 108px">Drag a module/artifact to a server to publish it</td>
@@ -170,10 +179,10 @@
 			<td style="width: 360px">Users drags a module or a artifact in it into a server, which would mean the same action as &quot;Run on Server&quot; .</td>
 		</tr>
 		<tr>
-			<td style="width: 108px">Provide classloader behaviour</td>
+			<td style="width: 108px">Provide classloader behavior</td>
 			<td style="width: 60px">1</td>
 			<td style="width: 78px">client programs</td>
-			<td style="width: 360px">A client, a jsp/ejb compiler for example, learns the classloader behaviour to mimic the server runtime environment</td>
+			<td style="width: 360px">A client, a jsp/ejb compiler for example, learns the classloader behavior to mimic the server runtime environment</td>
 		</tr>
 				<tr>
 			<td style="width: 108px">Adapt to existing project/module layout<i>(I am not sure, this is may be a use case for project layout)</i></td>