“Design principles”: Fix typos grammatical errors (#463)

* Fix typos of Design principles page * Fix typos in design-principles.html and design-principles-accessibility.html Co-authored-by: Volker E <[email protected]>
wikimedia · Jun 14, 2021 · efacbd7 · efacbd7
1 parent 874d369
commit efacbd7
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/design-principles.html b/design-principles.html
@@ -86,7 +86,7 @@ <h2>This is for everyone</h2>
 
 					<section id="content-first">
 						<h2>Content first</h2>
-						<p>People come to Wikimedia projects for their content. Our solutions should help to facilitate its creation, consumption, and sharing — without getting in the way. Our content (facts, images, quotes, etc.) is our most representative element, and needs to be emphasized in our solutions.</p>
+						<p>People come to Wikimedia projects for their content. Our solutions should help to facilitate its creation, consumption, and sharing — without getting in the way. Our content (facts, images, quotes, etc.) is our most representative element and needs to be emphasized in our solutions.</p>
 						<figure class="figure figure--full">
 							<picture>
 								<source media="( min-width: 415px )" srcset="img/design-principles/[email protected]">

diff --git a/design-principles_accessibility.html b/design-principles_accessibility.html
@@ -70,13 +70,13 @@ <h1 class="page__title">This is for everyone – Accessibility</h1>
 						<h2>What and why accessibility?</h2>
 						<p>Web accessibility methods ensure that people with impairments or disabilities can perceive, understand, navigate, interact with, and contribute to the products we all create. Just as importantly, many methods improve general usability, resulting in <strong>easier-to-use interfaces that are Perceivable, Operable, Understandable and Robust for everyone</strong>.</p>
 						<p>These are the four principles of accessibility from the Web Content Accessibility Guidelines standard<sup><a href="#references">[3]</a></sup> (WCAG 2.0 onwards). They specify the success criteria for achieved levels of conformance – A, AA and AAA.</p>
-						<p>In the Wikimedia Design Style Guide and its resources we aim for satisfying all level AA success criterias. Some AAA criterias are not possible to be satisfied for entire web sites as they are opposing each other. We also try to balance requirements that enable the widest possible audience under reasonable operation for our non-profit organization. Further, highly specific user group needs might be better covered by specific software products than by the Foundation itself.</p>
+						<p>In the Wikimedia Design Style Guide and its resources we aim for satisfying all level AA success criteria. Some AAA criteria are not possible to be satisfied for entire websites as they are opposing each other. We also try to balance requirements that enable the widest possible audience under reasonable operation for our non-profit organization. Further, highly specific user group needs might be better covered by specific software products than by the Foundation itself.</p>
 						<p>Note, that our principles mainly focus on designing for:</p>
 						<ul>
 							<li>Visual impairment needs</li>
 							<li>Motor impairment needs</li>
 						</ul>
-						<p>Other categories like speech impairments don't apply in our graphical user-interface focus, while hearing and cognitive impairments are to be covered on a content level, see for example Simple Wikipedia <span style="white-space: nowrap;">(English)<sup><a href="#references">[4]</a></sup></span> for being inclusive to users with learning difficulties.</p>
+						<p>Other categories like speech impairments don't apply in our graphical user-interface focus; while hearing and cognitive impairments are to be covered on a content level. See for example Simple Wikipedia <span style="white-space: nowrap;">(English)<sup><a href="#references">[4]</a></sup></span> for being inclusive to users with learning difficulties.</p>
 					</section>
 
 					<section id="accessible-by-design">
@@ -91,17 +91,17 @@ <h3>Colors and color palette – Use of color</h3>
 
 						<h3>Fonts and typography – Legible and zoomable content</h3>
 						<p class="heading__description">Visual</p>
-						<p>Choices of typeface, size, style, and spacing of text make it well readable in general, and are a must for some to be legible. <a href="visual-style_typography.html">Our choices</a> advise on minimum font sizes. Those are able to be overridden by user browser preferences – setting fonts in relative CSS units <code>em</code> or <code>rem</code> to provide text zooming when needed. </p>
+						<p>Choices of typeface, size, style, and spacing of text make it well readable in general and are a must for some to be legible. <a href="visual-style_typography.html">Our choices</a> advise on minimum font sizes. Those are able to be overridden by user browser preferences – setting fonts in relative CSS units <code>em</code> or <code>rem</code> to provide text zooming when needed. </p>
 
 						<h3>Touch and keyboard interaction – Ensure alternative input methods</h3>
 						<p class="heading__description">Motor</p>
 						<p>Our components are designed to support different interaction mechanisms, including touch, pointing devices and keyboard.</p>
-						<p>When touch screens are the main interface, our components' design ensures <a href="components/buttons.html#designing">minimum touch target sizes</a> for happy human fingers. Additionally users with motor impairments profit from minimum target sizes for pointer inputs too.<br>Our components feature a strong outline to indicate keyboard focus state. This enables keyboard-bound users to easily navigate the interface.</p>
+						<p>When touch screens are the main interface, our components' design ensures <a href="components/buttons.html#designing">minimum touch target sizes</a> for happy human fingers. Additionally, users with motor impairments profit from minimum target sizes for pointer inputs too.<br>Our components feature a strong outline to indicate keyboard focus state. This enables keyboard-bound users to easily navigate the interface.</p>
 
 						<h3>Icons and images – Provide text alternatives</h3>
 						<p class="heading__description">Visual</p>
 						<p>When implementing icons and images, you have to define a textual description to enable assistive technology to interpret it, as long as they are not solely used as decorative elements:</p>
-						<p>Icons have to be provided with SVG <code>title</code> attribute or with text nodes visible only for screen readers when used in icon-only buttons. <br>Images have to provide <code>alt</code> attribute with alternative text. <br><code>title</code> attributes are part of the icons in <a href="resources.html#icons">WikimediaUI icon collection</a>, and <a href="https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-ltr" target="_blank">code in WikimediaUI theme of user-interface library OOUI</a>.</p>
+						<p>Icons have to be provided with SVG <code>title</code> attributes or with text nodes visible only for screen readers when used in icon-only buttons. <br>Images have to provide <code>alt</code> attributes with alternative text. <br><code>title</code> attributes are part of the icons in <a href="resources.html#icons">WikimediaUI icon collection</a>, and <a href="https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-ltr" target="_blank">code in WikimediaUI theme of user-interface library OOUI</a>.</p>
 
 						<h3>Markup – Follow standards</h3>
 						<p class="heading__description">Visual, motor</p>