[css-ui] Editorial: Use "control" instead of "form control"

Fixes w3c#3970.

Author: zcorpan

css-ui-4/Overview.bs

@@ -1745,7 +1745,7 @@ without adverse consequences to compatibility,
 so this specification allows flexibility.
 
 
-<h2 id="form-styling">Form Control Styling</h2>
+<h2 id="control-styling" oldids="form-styling">Control Styling</h2>
 
 <h3 id="appearance-switching" caniuse="css-appearance">Switching appearance</h3>
 
@@ -1785,13 +1785,13 @@ so this specification allows flexibility.
 </div>
 
 While the way most elements in a document look can be fully controlled by CSS,
-form controls are typically rendered by UAs using native UI controls of the host operating system,
+controls are typically rendered by UAs using native UI controls of the host operating system,
 which can neither be replicated nor styled using CSS.
 
 This specification introduces the 'appearance' property
 to provide some control over this behavior.
 In particular, using ''appearance: none'' allows authors
-to suppress the native style of form controls,
+to suppress the native style of controls,
 so that CSS can be used to restyle them.
 
 <pre class="propdef">
@@ -1827,17 +1827,17 @@ Animation type: discrete
 	<dt><dfn>none</dfn>
 	<dd>
 		The element is rendered following the usual rules of CSS.
-		Replaced elements other than form controls are not affected by this,
+		Replaced elements other than controls are not affected by this,
 		and remain replaced elements.
-		Form controls are <em>not</em> made to look like native controls of the host operating system.
+		Controls are <em>not</em> made to look like native controls of the host operating system.
 		See [[#appearance-decorative]] and [[#appearance-semantics]] for details.
 
 	<dt><dfn>auto</dfn>
 	<dd>
-		UAs may render form controls using native controls of the host operating system
+		UAs may render controls using native controls of the host operating system
 		or with a look and feel not otherwise expressible in CSS.
 
-		Elements other than form controls must be rendered as if ''appearance/none'' had been specified.
+		Elements other than controls must be rendered as if ''appearance/none'' had been specified.
 
 	<dt><dfn>button</dfn>
 	<dd>
@@ -1883,7 +1883,7 @@ Animation type: discrete
 		some of these values need to be promoted to being full blown values
 		with effects on arbitrary elements like ''button'',
 		or that
-		some of these values need to have some side effects on some form controls.
+		some of these values need to have some side effects on some controls.
 
 
 </dl>
@@ -1914,7 +1914,7 @@ Animation type: discrete
 	and activating (for example by clicking) the element would toggle the state as usual.
 </div>
 
-On form control elements where the computed value is ''appearance/auto'' or one of the <<compat>> values,
+On controls where the computed value is ''appearance/auto'' or one of the <<compat>> values,
 and on any element where the computed value is ''appearance/button'',
 UAs may disregard some CSS properties
 to ensure that the intended appearance is preserved,
@@ -1943,7 +1943,7 @@ Issue: Are there more properties should include in this list?
 Should we remove some?
 Should whitelist the properties that are ok to ignore instead of
 blacklisting those that are not?
-Either way, UAs do ignore some properties when rendering form controls,
+Either way, UAs do ignore some properties when rendering controls,
 so this specification needs to say something about this.
 
 For compatibility with legacy content, UAs must also support <dfn property export>-webkit-appearance</dfn>
@@ -1952,7 +1952,7 @@ as a [=legacy name alias=] of 'appearance'.
 <h4 id=appearance-decorative>
 Effects of 'appearance' on Decorative Aspects of Elements</h4>
 
-All decorative visual aspects of a form control which are not caused by a CSS style rule
+All decorative visual aspects of a control which are not caused by a CSS style rule
 must be suppressed when the appearance is changed using 'appearance',
 even if the UA's internal representation for this element
 was composed of multiple elements or pseudo elements combined together.
@@ -1965,14 +1965,14 @@ was composed of multiple elements or pseudo elements combined together.
 </div>
 
 UAs should include in their User Agent stylesheet style rules
-to give form controls a recognizable shape when 'appearance' is ''appearance/none''.
+to give controls a recognizable shape when 'appearance' is ''appearance/none''.
 
 Note: Authors may therefore need to override these UA style rules to get the styling
 they intended.
 
 <div class=advisement>
 	Authors may find it convenient to use ''all: unset'',
-	to get fully unstyled form control elements
+	to get fully unstyled controls
 	which they can then style as they want without interference from the browser's UA stylesheet.
 	However, this also suppresses the focus indicators provided by the same UA stylesheet.
 	In order avoid damaging accessibility,
@@ -1983,7 +1983,7 @@ they intended.
 <h4 id=appearance-semantics>
 Effects of 'appearance' on Semantic Aspects of Elements</h4>
 
-UAs must preserve aspects of the form control
+UAs must preserve aspects of the control
 which are necessary to operate the control with its original semantics.
 The UA may however give them a different look and feel
 as long as it remains possible to operate the control.
@@ -2042,7 +2042,7 @@ that are typical of the element whose appearance it acquires.
 </div>
 
 <h3 id=control-specific-rules>
-Form Control Specific Rules</h3>
+Control Specific Rules</h3>
 
 Issue: Maybe some or all of this section
 should be moved to the [[HTML]] spec