Author: thomas.diesler(a)jboss.com Date: 2009-04-22 10:55:38 -0400 (Wed, 22 Apr 2009) New Revision: 87675 Modified: projects/jboss-osgi/trunk/build/docbook/en/modules/ch01-introduction.xml Log: Fix typos Modified: projects/jboss-osgi/trunk/build/docbook/en/modules/ch01-introduction.xml =================================================================== --- projects/jboss-osgi/trunk/build/docbook/en/modules/ch01-introduction.xml 2009-04-22 14:27:03 UTC (rev 87674) +++ projects/jboss-osgi/trunk/build/docbook/en/modules/ch01-introduction.xml 2009-04-22 14:55:38 UTC (rev 87675) @@ -45,8 +45,8 @@ <emphasis role="bold">Should Java EE developers adopt the OSGi programming model?</emphasis> <para>Probably not. The OSGi runtime may be used internally by Java EE container providers to achieve the desired isolation and configuration - flexibility that the container whishes to provide. At the application programming level, the Java EE model will continue to exist in its own right, - wheras the OSGi model may provide the more suitable runtime environment for applications that require the modular isolation, security and lifecycle + flexibility that the container wishes to provide. At the application programming level, the Java EE model will continue to exist in its own right, + whereas the OSGi model may provide the more suitable runtime environment for applications that require the modular isolation, security and lifecycle management that OSGi offers.</para> </sect1> @@ -142,7 +142,7 @@ </imageobject> </mediaobject> - <para>Appart from bundle versions, OSGi Attribute Matching is a generic mechanism to allow the importer and exporter to influence the + <para>Apart from bundle versions, OSGi Attribute Matching is a generic mechanism to allow the importer and exporter to influence the matching process in a declarative way. For example, the following statements will match.</para> <programlisting>