Consistency: use "touchscreen" rather than "touch screen"

understanding/20/keyboard-no-exception.html

@@ -49,7 +49,7 @@ <h2>Intent of Keyboard (No Exception)</h2>
 
       <div class="note">
          <p>This success criterion does not require that every visible control that can be activated
-            using a pointer (such as a mouse or touch screen input) must also be focusable and actionable using the keyboard.
+            using a pointer (such as a mouse or touchscreen input) must also be focusable and actionable using the keyboard.
             The normative requirement is only that there must be a way for keyboard interface users to perform
             the same, or comparable, actions and to operate the content. Generally, the easiest way
             to achieve this is to provide controls that can be operated with all possible input devices;

understanding/20/keyboard.html

@@ -77,7 +77,7 @@ <h2>Intent of Keyboard</h2>
 
       <div class="note">
          <p>This success criterion does not require that every visible control that can be activated
-            using a mouse or touch screen must also be focusable and actionable using the keyboard.
+            using a mouse or touchscreen must also be focusable and actionable using the keyboard.
             The normative requirement is only that there must be a way for keyboard interface users to perform
             the same, or comparable, actions and to operate the content. Generally, the easiest way
             to achieve this is to provide controls that can be operated with all possible input devices;

understanding/21/input-modalities.html

@@ -10,8 +10,8 @@
 		<h1>Understanding Input Modalities</h1>
 		<section id="intent">
 			<h2>Intent of Input Modalities</h2>
-			<p>All functionality should be accessible via pointer input devices, for example, via a mouse pointer, a finger interacting with a touch screen, an electronic pencil/stylus, or a laser pointer.</p>
-      <p>People operating pointer input devices may not be able to carry out timed or complex gestures. Examples are drag-and-drop gestures and on touch screens, swiping gestures, split taps, or long presses. This Guideline does not discourage the provision of complex and timed gestures by authors. However, where they are used, an alternative method of input should be provided to enable users with motor impairments to interact with content via single untimed pointer gestures.</p>
+			<p>All functionality should be accessible via pointer input devices, for example, via a mouse pointer, a finger interacting with a touchscreen, an electronic pencil/stylus, or a laser pointer.</p>
+      <p>People operating pointer input devices may not be able to carry out timed or complex gestures. Examples are drag-and-drop gestures and on touchscreens, swiping gestures, split taps, or long presses. This Guideline does not discourage the provision of complex and timed gestures by authors. However, where they are used, an alternative method of input should be provided to enable users with motor impairments to interact with content via single untimed pointer gestures.</p>
         <p>Often, people use devices that offer several input methods, for example, mouse input, touch input, keyboard input, and speech input. These should be supported concurrently as users may at any time switch preferred input methods due to situational circumstances, for example, the availability of a flat support for mouse operation, or situational impediments through motion or changes of ambient light.</p>
       <p>A common requirement for pointer interaction is the ability of users to position the pointer over the target. With touch input, the pointer (the finger) is larger and less precise than a mouse cursor. For people with motor impairments, a larger target makes it easier to successfully position the pointer and activate the target.</p>
     </section>

understanding/21/target-size-enhanced.html

@@ -10,7 +10,7 @@ <h1>Understanding SC 2.5.5 Target Size (Enhanced)</h1>
   	<section id="brief">
   		<h2>In brief</h2>
   		<dl>
-  			<dt>Goal</dt><dd>Controls can be operated more easily, especially on touch screens.</dd>
+  			<dt>Goal</dt><dd>Controls can be operated more easily, especially on touchscreens.</dd>
   			<dt>What to do</dt><dd>Make custom targets at least 44 by 44 pixels.</dd>
   			<dt>Why it's important</dt><dd>Some people cannot tap small objects.</dd>
   		</dl>
@@ -19,7 +19,7 @@ <h2>In brief</h2>
   		<h2>Intent</h2>
   		<p>The intent of this success criterion is to help users who may have trouble activating a small target because of hand tremors, limited dexterity, or other reasons. If the target is too small, it may be difficult to aim at the target. Mice and similar pointing devices can be hard to use for these users, and a larger target will help them greatly in having positive outcomes on the web page.</p>
       <p>Touch is particularly problematic as it is an input mechanism with coarse precision. Users lack the same level of fine control as on inputs such as a mouse or stylus. A finger is larger than a mouse pointer, and generally obstructs the user's view of the precise location on the screen that is being touched/activated.</p>
-      <p>The issue can be further complicated for responsive and mobile sites that need to accommodate different types of fine and coarse inputs (for example, a site that can be accessed on a traditional desktop or laptop with a mouse, as well as on a tablet or mobile phone with a touch screen).</p>
+      <p>The issue can be further complicated for responsive and mobile sites that need to accommodate different types of fine and coarse inputs (for example, a site that can be accessed on a traditional desktop or laptop with a mouse, as well as on a tablet or mobile phone with a touchscreen).</p>
       <p>While this criterion defines a minimum target size, it is recommended that larger sizes are used to reduce the possibility of unintentional actions. This is particularly relevant if any of the following are true:</p>
   	  <ul>
         <li>the control is used frequently;</li>
@@ -42,7 +42,7 @@ <h2>Intent</h2>
     <section id="benefits">
       <h2>Benefits</h2>
       <ul>
-        <li>Users who use a mobile device where touch screen is the primary mode of interaction</li>
+        <li>Users who use a mobile device where a touchscreen is the primary mode of interaction</li>
         <li>Users with mobility impairments, such as hand tremors</li>
         <li>Users who use a mobile device in environments where they are exposed to shaking such as public transportation</li>
         <li>Users who find fine motor movements difficult</li>

understanding/22/accessible-authentication-minimum.html

@@ -29,7 +29,7 @@ <h2>Intent of Accessible Authentication (Minimum)</h2>
         <section id="cog-fun-tests">
             <h3>Cognitive Function Tests</h3>
 
-            <p>Remembering a site-specific password is a <a>cognitive function test</a>. Such tests are known to be problematic for many people with cognitive disabilities. Whether it is remembering random strings of characters, or a pattern gesture to perform on a touch screen, cognitive function tests will exclude some people. When a cognitive function test is used, at least one other authentication method must be available which is not a cognitive function test.</p>
+            <p>Remembering a site-specific password is a <a>cognitive function test</a>. Such tests are known to be problematic for many people with cognitive disabilities. Whether it is remembering random strings of characters, or a pattern gesture to perform on a touchscreen, cognitive function tests will exclude some people. When a cognitive function test is used, at least one other authentication method must be available which is not a cognitive function test.</p>
 
 
             <p>Some <abbr title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</abbr> systems have an audio alternative of the visible text. If the user needs to transcribe this audio, it cannot be used to meet the Alternative exception.</p>            

understanding/22/target-size-minimum.html

@@ -149,7 +149,7 @@ <h3>User agent control</h3>
         <h2>Benefits of Target Size (Minimum)</h2>
         <p>Having targets with sufficient size - or at least sufficient target spacing - can help all users who may have difficulty in confidently targeting or operating small controls. Users who benefit include, but are not limited to:</p>
         <ul>
-            <li>People who use a mobile device where the touch screen is the primary mode of interaction;</li>
+            <li>People who use a mobile device where the touchscreen is the primary mode of interaction;</li>
             <li>People using mouse, stylus or touch input who have mobility impairments such as hand tremors;</li>
             <li>People using a device in environments where they are exposed to shaking such as public transportation;</li>
             <li>Mouse users who have difficulty with fine motor movements;</li>