Author: thomas.heute(a)jboss.com
Date: 2008-10-28 13:26:14 -0400 (Tue, 28 Oct 2008)
New Revision: 12203
Modified:
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/coordination.xml
Log:
Found a typo ;)
Modified:
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/coordination.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/coordination.xml 2008-10-28
17:13:26 UTC (rev 12202)
+++
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/coordination.xml 2008-10-28
17:26:14 UTC (rev 12203)
@@ -38,7 +38,7 @@
However, such an <emphasis>implicit</emphasis> model of how
portlets are wired together fails to handle more
complex cases. In particular, it is often the case that semantically related
events or public parameters are
named differently by different portlet providers. As it is not always
possible to modify the portlets to
- adjust for this minor naming difference of otherwise semnantically compatible
portlets, JBoss Portal
+ adjust for this minor naming difference of otherwise semantically compatible
portlets, JBoss Portal
introduces an <emphasis>explicit</emphasis> coordination model
that takes precedence over the implicit model
when so required.
</para>