[jboss-cvs] JBossAS SVN: r92551 - projects/docs/enterprise/5.0/Getting_Started_Guide/en-US.

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

Author: irooskov at redhat.com
Date: 2009-08-18 20:16:25 -0400 (Tue, 18 Aug 2009)
New Revision: 92551

Modified:
   projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
Log:
updated to correct tag errors


Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml	2009-08-18 23:36:07 UTC (rev 92550)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml	2009-08-19 00:16:25 UTC (rev 92551)
@@ -15,7 +15,7 @@
 </para>
 <para>
 	The JBoss Enterprise Application Platform ships with six different server profiles. Within the	<literal>&lt;JBoss_Home&gt;/server</literal> directory, you will find six subdirectories:
-	<literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literla>production</literal>, <literal>standard</literal> and <literal>web</literal> - one for each server profile. Each of these profiles provide a different set of services. The <literal>production</literal> profile is the one used if you don’t specify another one when starting up the server.
+	<literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literal>production</literal>, <literal>standard</literal> and <literal>web</literal> - one for each server profile. Each of these profiles provide a different set of services. The <literal>production</literal> profile is the one used if you don’t specify another one when starting up the server.
 </para>
 <para>
 	<variablelist>
@@ -144,7 +144,7 @@
 		Installing JBoss Enterprise Application Platform creates a top level directory, which will be named <filename>jboss-eap-&lt;version&gt;</filename> if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the <filename>JBOSS_DIST</filename> directory.
 	</para>
 	<para>
-		<table id="JBOSS_DIST/jboss-as_directory_structure">
+		<table id="JBOSS_DIST_jboss-as_directory_structure">
 			<title><filename>JBOSS_DIST/jboss-as</filename> directory structure</title>
 			<tgroup cols="3">
 				<colspec colname="c1" colnum="1" colwidth="1*"/>
@@ -262,7 +262,7 @@
 							<filename class="directory">conf</filename>
 						</entry>
 						<entry>
-							The <filename class="directory">conf</filename> directory contains the <filename>jboss-service.xml<filename>, <filename>bootstrap.xml</filename> bootstrap descriptor file for a given server configuration. The <filename>bootstrap.xml</filename> inturn points to various other configuration files which comprise of the server bootstrap. This defines the core microcontainer beans that are fixed for the lifetime of the server. 
+							The <filename class="directory">conf</filename> directory contains the <filename>jboss-service.xml</filename>, <filename>bootstrap.xml</filename> bootstrap descriptor file for a given server configuration. The <filename>bootstrap.xml</filename> inturn points to various other configuration files which comprise of the server bootstrap. This defines the core microcontainer beans that are fixed for the lifetime of the server. 
 						</entry>
 					</row>
 					<row>
@@ -278,7 +278,7 @@
 							<filename class="directory">deploy</filename>
 						</entry>
 						<entry>
-							The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server configuration. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically. This may be overridden through the <poperty>applicationURIs</property> property of the  <classname>BootstrapProfileFactory</classname> bean configuration in the <filename>JBOSS_DIST/jboss-as/server/&lt;instance-name&gt;/conf/bootstrap/profile.xml</filename> file.
+							The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server configuration. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically. This may be overridden through the <property>applicationURIs</property> property of the  <classname>BootstrapProfileFactory</classname> bean configuration in the <filename>JBOSS_DIST/jboss-as/server/&lt;instance-name&gt;/conf/bootstrap/profile.xml</filename> file.
 						</entry>
 					</row>
 					<row>