Fix typos in index.html

index.html

@@ -53,10 +53,10 @@ <h2 id="method">Method</h2>
 <h2 id="failures">Failures</h2>
 <p>Unlike a compliance audit (which determines adherence to regulatory guidelines), Chartability is meant to identify design failures. Generally, Chartability approaches accessibility as a scale rather than a state: how accessible a DX is is determined by how few failures it contains. It should be assumed that even the absolute best DX may contain several failures, even after remediation. Note that Chartability should never be used in place of a compliance audit but always in tandem with it.</p>
 <p>Chartability’s insistence on a scale (instead of a state) of accessibility requires that designers and creators consider their choices carefully: they must be willing to argue that lack of scope, time, or research or perhaps a unique consideration led to a given failure. No failure should be left unconsidered.</p>
-<p>An important note about language: Chartability's tests are framed in negative language, like "Target pointer interaction size is too small." This is intentional. Chartability is not meant to be used to "pass" accessibility requirements. You cannot "pass" Chartability 100%. Rather, Chartability is simply framed as a tool that helps people catch known barriers, or "failures." It is possible to have 0 failures in Chartability but still have accessibility issues. This is because the work of accessibility never ends!</p>
+<p>An important note about language: Chartability's tests are framed in negative language, like "Target pointer interaction size is too small." This is intentional. Chartability is not meant to be used to "pass" accessibility requirements. You cannot "pass" Chartability 100%. Rather, Chartability is simply framed as a tool that helps people catch known barriers, or "failures". It is possible to have 0 failures in Chartability but still have accessibility issues. This is because the work of accessibility never ends!</p>
 <h2 id="outcomes">Outcomes</h2>
 <p>Chartability is a set of heuristic tests that not only highlights failures for remediation, but also encourages healthy design critique and critical design discourse related to accessibility. Because excellence in accessibility is never a finished state, the outcome of a Chartability audit is less about arriving at accessibility and more about working towards an accessible experience.</p>
-<p>A good audit is not about measuring sucess: a good audit finds evidence of risk and failure.</p>
+<p>A good audit is not about measuring success: a good audit finds evidence of risk and failure.</p>
 <h2 id="whatarecriticalheuristics">What are "Critical" heuristics?</h2>
 <p>Some tests are considered <em>critical</em> by members of the community because they are prohibitively expensive to fix, common, produces signficant barriers, and/or affect many aspects of a data experience design or development.</p>
 <p>While all tests in Chartability are important, it is worth noting that Chartability's community has contributed to emphasizing the tests marked critical. All data experiences should strive to have 0 critical failures as a minimum while working toward 0 failures overall.</p>
@@ -564,4 +564,4 @@ <h2 id="credits">Credits and Thanks</h2>
 <script>
     console.log("Welcome to Chartability :)")
 </script>
-</body></html>
+</body></html>