minor markup formatting adjustment

index.html

@@ -244,11 +244,8 @@ HTML Element Role Mappings
         HTML elements with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the [[core-aam-1.2]] specification.
         "Not mapped" means the element is not exposed via an accessibility API. Commonly, an element is not mapped because it's not displayed as part of the user interface. However, authors can force some of these elements to be rendered. For instance, by overriding user agent styles to render elements that would have been otherwise set to `display: none`. In these cases, the user agent SHOULD map such elements to the role of `generic`, unless other HTML features have been specified which would require a more specific minimum role to be exposed.
         Where an element is indicated as having No corresponding (WAI-ARIA) role, or is mapped to the `generic` role, user agents MUST NOT expose the `aria-roledescription` property value in the accessibility tree unless the element has an explicit, conforming `role` attribute value for which [[WAI-ARIA-1.2]] does not prohibit the use of `aria-roledescription`.
-        
-          Some HTML elements expose implicit WAI-ARIA roles depending on whether they have been provided an accessible name. How an element participates in the computation of its own or another element's accessible name and/or accessible description is described in the Accessible Name and Description Computation section of this document.
-        
+        Some HTML elements expose implicit WAI-ARIA roles depending on whether they have been provided an accessible name. How an element participates in the computation of its own or another element's accessible name and/or accessible description is described in the Accessible Name and Description Computation section of this document.
       
-
       
         Platform API mapping requirements