Author: mcaspers Date: 2011-03-13 23:04:59 -0400 (Sun, 13 Mar 2011) New Revision: 29735 Modified: trunk/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_4.png trunk/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_5.png trunk/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml Log: "General editing and screenshot updates" Modified: trunk/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_4.png =================================================================== (Binary files differ) Modified: trunk/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_5.png =================================================================== (Binary files differ) Modified: trunk/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml =================================================================== --- trunk/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml 2011-03-14 02:57:46 UTC (rev 29734) +++ trunk/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml 2011-03-14 03:04:59 UTC (rev 29735) @@ -133,7 +133,7 @@ <entry> <para> - Some servers already provide JSF libs and you risk library conflicts while deploying your project. To avoid such conflicts, use a template without libs if you have a server with its own JSF libraries. + Some servers already provide JSF libs, and you risk library conflicts while deploying your project. To avoid such conflicts, use a template without libs if you have a server with its own JSF libraries. </para> </entry> </row>