@@ -837,7 +837,7 @@ and are never used outside of the UA stylesheet.
837837Instead, this specification only provides
838838''appearance/auto'' , ''appearance/none'' .
839839UAs cannot therefore use the 'appearance' property
840- in the UA stylesheet to give each control is native look and feel,
840+ in the UA stylesheet to give each control its native look and feel,
841841and must use ''appearance:auto'' instead.
842842
843843Issue: IE supports -webkit-appearance, and also includes the textfield and button values.
@@ -864,7 +864,7 @@ so we may need to include it as well.
864864On form control elements where the computed value is ''appearance/auto''
865865UAs may disregard some CSS properties
866866to ensure that the intended appearance is preserved,
867- or because these property may not be meaningful for the chosen appearance.
867+ or because these properties may not be meaningful for the chosen appearance.
868868However, the following properties must not be disregarded:
869869<ul>
870870 <li> 'appearance'
@@ -897,7 +897,7 @@ must be suppressed when the appearance is changed using 'appearance',
897897even if the UA's internal representation for this element
898898was composed of multiple elements or pseudo elements combined together.
899899For example, <{select}> is often rendered with an arrow on the right side
900- indicating that the list will be expanded if the element is clicked,
900+ indicating that the list will be expanded if the element is clicked.
901901If the computed value of 'appearance' is ''appearance/none'' , this
902902must disappear.
903903
0 commit comments