Author: smukhina
Date: 2008-05-22 08:26:38 -0400 (Thu, 22 May 2008)
New Revision: 8692
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml
Log:
http://jira.jboss.com/jira/browse/RF-398
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml
===================================================================
---
trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml 2008-05-22
12:18:22 UTC (rev 8691)
+++
trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml 2008-05-22
12:26:38 UTC (rev 8692)
@@ -43,7 +43,7 @@
<li>
Several style classes are provided for different types of
elements. That style classes have predefined names. Application
- developer should manually assign classes to controls that needs
+ developer should manually assign classes to controls that need
skinning or assign class to an element that contains controls.
</li>
</ul>
@@ -60,10 +60,10 @@
</li>
</ol>
<p>
- Skinning level calculated automatically at server side depending on user agent info.
+ Skinning level is calculated automatically at server side depending on user agent
info.
</p>
<p class="note">
- Extended skinning not applied to browsers having rich
+ Extended skinning is not applied to browsers having rich
visual styling for controls (e.g. Opera and Safari).
Also advanced level of skinning requires support of CSS 2 attribute selectors
either as implicit type attributes for button/textarea elements (e.g. IE7
@@ -76,7 +76,7 @@
</p>
<ul>
<li>
- <b>org.richfaces.CONTROL_SKINNING</b> context param set to
<b>enabled</b> means that all
+ <b>org.richfaces.CONTROL_SKINNING</b> context param set to
<b>enabled</b> means that all
standard elements on the page will be skinned. (CSS style classes for
elements based on their names and type attribute values will be applied)
</li>
@@ -87,12 +87,12 @@
</li>
<li>
Rich faces also provides predefined classes which can be applied by end developer
- to elements need to be skinned separately. This classes added to the page also
+ to elements need to be skinned separately. This classes added to the page also
according to <b>org.richfaces.CONTROL_SKINNING_CLASSES</b> context-param.
</li>
</ul>
<p>
- Using first way CSS with next definitions will be automatically added to pages:
+ Using first way CSS with the next definitions will be automatically added to pages:
</p>
<fieldset class="demo_fieldset">
<legend class="demo_legend">CSS for standard elements
snippet</legend>
@@ -101,7 +101,7 @@
</rich:panel>
</fieldset>
<p>
- And using the second way next CSS will influence corresponding elements:
+ And using the second way the next CSS will influence corresponding elements:
</p>
<fieldset class="demo_fieldset">
<legend class="demo_legend">CSS for standard elements inside rich
container snippet</legend>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml 2008-05-22
12:18:22 UTC (rev 8691)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml 2008-05-22
12:26:38 UTC (rev 8692)
@@ -9,7 +9,7 @@
<ui:define name="sample">
<p>
- ToolTip is a little non-modal pop-up that could be used to display additional
information, that is usually hidden.<br/>
+ ToolTip is a small non-modal pop-up that could be used to display additional
information, that is usually hidden.<br/>
Major toolTip features:
</p>