From 716ef69f6a5885ec5067696389ed9d239677f3e3 Mon Sep 17 00:00:00 2001
From: robert-kinder <57666991+robert-kinder@users.noreply.github.com>
Date: Thu, 23 Jan 2020 17:40:46 +0000
Subject: [PATCH] Remove "Don't" - ref Issue #102

I have left: "Instructions don't rely on sensory characteristics" as it's a title to have a (slightly) different title in the index as opposed to the actual page
---
 index.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.html b/index.html
index 0669179..35ed060 100644
--- a/index.html
+++ b/index.html
@@ -16,7 +16,7 @@ <h1>Accessibility Guidelines Summary</h1>
       <p>This document provided by <a href="https://www.theappbusiness.com/">TAB</a> will help you quickly get up to speed with the <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines (WCAG) 2.1</a>, and avoid common accessibility mistakes.</p>
 
       <p>It only covers <span class="badge badge--level">Level A</span> and <span class="badge badge--level">Level AA</span> requirements, which are referenced in <a href="https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps">public sector procurement laws in the UK</a>, <a href="https://en.wikipedia.org/wiki/Section_508_Amendment_to_the_Rehabilitation_Act_of_1973">US <span class="!visually-hidden">public sector procurement laws</span></a>, <a href="http://mandate376.standards.eu/standard/technical-requirements/#9">EU <span class="!visually-hidden">public sector procurement laws</span></a> and <a href="https://www.w3.org/WAI/policies/"><span class="!visually-hidden">public sector procurement laws </span>around the world</a>.
-
+  
       <p>These guidelines apply to both native apps and web-based apps, except for three which are labelled <span class="badge badge--web-only">Web only</span>.</p>
 
       <p>This summary is a simplification. If you're not sure how a guideline applies, check the official <a href="https://www.w3.org/TR/WCAG21/">WCAG 2.1</a>.</p>
@@ -121,7 +121,7 @@ <h3 id="1_3_heading">1.3. Create content that can be presented in different ways
               <li class="badge badge--level">Level A</li>
               <li class="badge badge--design">Design</li>
             </ul>
-            <div>If you give tips or instructions, don't assume that users can perceive colour, size, shape, sound or the location of elements on screen.</div>
+            <div>If you give tips or instructions, do not assume that users can perceive colour, size, shape, sound or the location of elements on screen.</div>
           </li>
   
           <li class="guideline">
@@ -240,7 +240,7 @@ <h2 id="principle_2_header">2. Easy to operate</h2>
   
         <p>Your website/app must be easy to navigate and use, no matter how someone interacts with it.</p>
   
-        <p>For example people who don't use a mouse may use their voice, or press the 'Tab' key to move their keyboard's focus to interactive controls.</p>
+        <p>For example people who do not use a mouse may use their voice, or press the 'Tab' key to move their keyboard's focus to interactive controls.</p>
   
         <h3 id="2_1_heading">2.1. Make all functionality work with a keyboard</h3>
   
@@ -262,7 +262,7 @@ <h3 id="2_1_heading">2.1. Make all functionality work with a keyboard</h3>
               <li class="badge badge--design">Design</li>
               <li class="badge badge--code">Code</li>
             </ul>
-            <div>Make sure that keyboard-only users don't get trapped within any element.</div>
+            <div>Make sure that keyboard-only users do not get trapped within any element.</div>
           </li>
   
           <li class="guideline">