[jboss-cvs] JBossAS SVN: r66142 - branches/Branch_4_2/build/docs.

[jboss-cvs-commits at lists.jboss.org]

Author: dimitris at jboss.org
Date: 2007-10-15 17:56:41 -0400 (Mon, 15 Oct 2007)
New Revision: 66142

Modified:
   branches/Branch_4_2/build/docs/readme.html
Log:
JBAS-4695, release notes for 4.2.2.GA, more info on jbossxb and jbossws

Modified: branches/Branch_4_2/build/docs/readme.html
===================================================================
--- branches/Branch_4_2/build/docs/readme.html	2007-10-15 21:54:44 UTC (rev 66141)
+++ branches/Branch_4_2/build/docs/readme.html	2007-10-15 21:56:41 UTC (rev 66142)
@@ -125,9 +125,9 @@
 WS 1.0.x due to a deployer limitation used a proprietary .jse
 extension for deploying WS endpoints nested in .sar files.
 This was deprecated with JBoss WS 1.2.x. and with JBoss WS 2.x this
-proprietary extention is not supported anymore as it is possible to use
+proprietary extension is not supported anymore as it is possible to use
 the standard .war extension for deploying nested WS endpoints. If
-you seeINIT_WAITING_DEPLOYER error messages for .jse files, re-package them using a .war extension,  <a href="http://jira.jboss.com/jira/browse/JBWS-1854">JBWS-1854</a>.<span style="font-family: monospace;"></span></li><li>Finding
+you see:&nbsp;INIT_WAITING_DEPLOYER error messages for .jse files, re-package them using a .war extension, <a href="http://jira.jboss.com/jira/browse/JBWS-1854">JBWS-1854</a>.<span style="font-family: monospace;"></span></li><li>Finding
 the default local business interface on a ejb3 bean may not work in
 certain inheritance scenarios. You may workaround this known
 problem&nbsp;by&nbsp;annotating the local business interface. Read more