Author: julien(a)jboss.com Date: 2007-04-27 19:00:28 -0400 (Fri, 27 Apr 2007) New Revision: 7120 Modified: docs/trunk/referenceGuide/en/modules/contentIntegration.xml Log: typo Modified: docs/trunk/referenceGuide/en/modules/contentIntegration.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/contentIntegration.xml 2007-04-27 22:57:01 UTC (rev 7119) +++ docs/trunk/referenceGuide/en/modules/contentIntegration.xml 2007-04-27 23:00:28 UTC (rev 7120) @@ -12,7 +12,7 @@ content integration had to be done by configuring a portlet to show some content from an URI and then place that portlet on a page. The new content integration capabilities allows to directly configure a page window with the content URI removing the need to configure a portlet for that purpose.</para> - <note>We do not advocate to avoid to use portlet preferences, we rather advocate that content configuration managed at the portal level + <note>We do not advocate to avoid the usage portlet preferences, we rather advocate that content configuration managed at the portal level simplifies the configuration: it helps to make content a first class citizen of the portal instead of having an intermediary portlet that holds the content for the portal. The portlet preferences can still be used to configure how content is displayed to the user.</note>