Developing a Keyboard Interface Practice: Editorial revision to note about pointer considerations (pull #3366)

Makes two minor editorial improvements to the note about pointer considerations when managing focus:

* Change 'must' to 'need to' to avoid use of normative sounding language.
* Remove phrase 'of course' to avoid superfluous language.

Author: daniel-montalvo

content/practices/keyboard-interface/keyboard-interface-practice.html

@@ -379,7 +379,7 @@ <h3>Managing Focus in Composites Using <code>aria-activedescendant</code></h3>
 
           <div class="note">
             <h4>Note</h4>
-            <p>This guidance focuses specifically on keyboard interaction. However, authors must of course also consider pointer interactions, such as mouse clicks
+            <p>This guidance focuses specifically on keyboard interaction. However, authors also need to consider pointer interactions, such as mouse clicks
               and touchscreen taps. When a component is clicked/tapped,
               authors should take the same steps to set the correct <code>tabindex</code> or <code>aria-activedescendant</code> for the element,
               in the same way that they would for keyboard navigation. Otherwise, this could lead to a confusing experience for users that switch between pointer