Few fixes for the accessibility section

index.html

@@ -623,25 +623,25 @@ <h2>
       <ol>
         <li>Designing and making applications which do not place content in the
         fold/hinge area, especially buttons. This area is typically hard to
-        interact with with fingers because the curvature of the fold make touch
+        interact with with fingers because the curvature of the fold makes touch
         less precise or impossible.
         </li>
-        <li>Designing and making applications which do not put a large
-        contiguous content (like a video or a picture) spanning across the
+        <li>Designing and making applications which do not put large,
+        contiguous content (such as video or a picture) spanning across the
         fold/hinge area if the device is folded. This area slightly distorts
         content and colors.
         </li>
         <li>Designing and making applications which use the screen estate
-        better by providing a split UI - a user interface where the content is
-        split up across the screen segments -, allowing the application to
+        better by providing a split UI (a user interface where the content is
+        split up across the screen segments), allowing the application to
         provide a differentiated and more powerful interface.
         </li>
       </ol>When using this API it is important to consider the opportunities
       above with accessibility in mind. Here are few concrete examples:
       <ul>
         <li>
           <strong>Placement of UI elements:</strong> A typical placement logic
-          for dialogs is to center them horizontally and vertically but in a
+          for dialogs is to center them horizontally and vertically, but in a
           device folded with a symmetrical fold they may end up in the middle
           of the fold area making it harder to interact with, for instance
           clicking on buttons. It might also make it harder to read text due to
@@ -651,7 +651,7 @@ <h2>
           <strong>Fullscreen mode:</strong> When resizing an element in
           fullscreen, a typical logic would expand that element to the width
           and the height of the {{Window}}. If the device is folded, the
-          element will be laid out across the fold making a subpar user
+          element will be laid out across the fold, leading to a subpar user
           experience. An alternative is to display that element either on top
           or below the fold area.
         </li>
@@ -669,7 +669,8 @@ <h2>
           <strong>Content shouldn't be designed for just one
           {{posture}}:</strong> The idea of foldable devices is their
           versatility and the ability for the user to change the posture as
-          they see fit. With accessibility, it is important to not always
+          they see fit. Similarly to the <a href="https://www.w3.org/WAI/WCAG21/Understanding/orientation.html"
+          >orientation</a>, it is important to not always
           choose for the user as they might have other needs but allowing them
           to choose the UI that fits their needs better. Ideally it is
           preferred to make the UI configurable.
@@ -761,8 +762,8 @@ <h2>
       </h2>
       <p>
         We would like to offer our sincere thanks to Daniel Appelquist, Jo
-        Balletti, Michael Blix, Alexis Menard and Laura Morinigo for their
-        contributions to this work.
+        Balletti, Michael Blix, Paul Grenier and Laura Morinigo
+        for their contributions to this work.
       </p>
     </section>
   </body>