Rewrite to avoid using RFC2119 keywords in non-normative text.

Author: mgiuca

index.html

@@ -102,9 +102,9 @@ <h3>
           The above statement is designed to permit feature detection. If
           <a for="Navigator"><code>share</code></a> is present, there is a
           reasonable expectation that it will work and present the user with at
-          least one <a>share target</a>. Clients should be able to use the
-          presence or absence of this method to determine whether to show UI
-          that triggers its use.
+          least one <a>share target</a>. Clients can use the presence or
+          absence of this method to determine whether to show UI that triggers
+          its use.
         </div>
         <section>
           <h4>
@@ -235,13 +235,13 @@ <h3>
           These fields are <a data-cite=
           "!WEBIDL#idl-USVString"><code>USVString</code></a> (as opposed to
           <a data-cite="!WEBIDL#idl-DOMString"><code>DOMString</code></a>)
-          because they must not contain invalid <a data-cite=
+          because they are not allowed to contain invalid <a data-cite=
           "rfc2781#section-2">UTF-16</a> surrogates. This means the user agent
           is free to re-encode them in any Unicode encoding (e.g.,
           <a data-cite="rfc3629#section-3">UTF-8</a>).
         </div>
         <div class="note">
-          The <a for="ShareData">url</a> field may contain a <a data-cite=
+          The <a for="ShareData">url</a> field can contain a <a data-cite=
           "!URL#relative-url-with-fragment-string">relative URL</a>. In this
           case, it will be automatically resolved relative to the current page
           location, just like a <a data-cite=
@@ -262,7 +262,7 @@ <h2>
         user agent.
       </p>
       <p>
-        A share target may not be directly able to accept a <a>ShareData</a>
+        A share target might not be directly able to accept a <a>ShareData</a>
         (due to not having been written with this API in mind). However, it
         MUST have the ability to receive data that matches some or all of the
         concepts exposed in <a>ShareData</a>. To <dfn>convert data to a format
@@ -272,18 +272,17 @@ <h2>
         payload is at the discretion of the share target.
       </p>
       <p>
-        Each share target may be made conditionally available depending on the
+        Each share target MAY be made conditionally available depending on the
         <a>ShareData</a> payload delivered to the <a for="Navigator">share</a>
         method.
       </p>
       <div class="note">
         Once a share target has been given the payload, the share is considered
         successful. If the target considers the data unacceptable or an error
-        occurs, the target should either recover gracefully, or show an error
-        message to the end-user, because the sender is not going to know that
-        an error occurred. In other words, the <a for="Navigator">share</a>
-        method is "fire and forget"; it does not wait for the target to approve
-        or reject the payload.
+        occurs, it can either recover gracefully, or show an error message to
+        the end-user; it cannot rely on the sender to handle errors. In other
+        words, the <a for="Navigator">share</a> method is "fire and forget"; it
+        does not wait for the target to approve or reject the payload.
       </div>
       <section class="informative">
         <h3>
@@ -314,16 +313,16 @@ <h3>
         <p>
           In some cases, the host operating system will provide a sharing or
           intent system similar to Web Share. In these cases, the user agent
-          may simply forward the share data to the operating system and not
+          can simply forward the share data to the operating system and not
           talk directly to native applications.
         </p>
         <p>
           Mapping the <a>ShareData</a> to the share target (or operating
           system)'s native format can be tricky as some platforms will not have
           an equivalent set of fields. For example, if the target has a "text"
-          field but not a "URL" field, it may be necessary to concatenate both
-          the <a for="ShareData">text</a> and <a for="ShareData">url</a> fields
-          of <a>ShareData</a> and pass the result in the "text" field of the
+          field but not a "URL" field, one solution is to concatenate both the
+          <a for="ShareData">text</a> and <a for="ShareData">url</a> fields of
+          <a>ShareData</a> and pass the result in the "text" field of the
           target.
         </p>
       </section>
@@ -332,14 +331,10 @@ <h3>
       <h2>
         Security and privacy considerations
       </h2>
-      <p>
-        Implementations should observe the following security and privacy
-        advice.
-      </p>
       <p>
         Web Share enables data to be sent from websites to native applications.
         While this ability is not unique to Web Share, it does come with a
-        number of potential security issues that may vary in severity
+        number of potential security issues that can vary in severity
         (depending on the underlying platform).
       </p>
       <ul>
@@ -349,11 +344,11 @@ <h2>
         used for fingerprinting, as well as leaking details about the user's
         device.
         </li>
-        <li>Implementors should carefully consider what information is revealed
-        in the error message when <a><code>navigator.share</code></a> is
-        rejected. Even distinguishing between the case where no targets are
-        available and user cancellation may reveal information about which apps
-        are installed on the user's device.
+        <li>Implementors will want to carefully consider what information is
+        revealed in the error message when <a><code>navigator.share</code></a>
+        is rejected. Even distinguishing between the case where no targets are
+        available and user cancellation could reveal information about which
+        apps are installed on the user's device.
         </li>
         <li>There is a requirement that <a><code>navigator.share</code></a>
         presents the user with a dialog asking them to select a target
@@ -368,16 +363,16 @@ <h2>
         </li>
         <li>Use of <a><code>navigator.share</code></a> from a <a href=
         "https://en.wikipedia.org/wiki/Privacy_mode">private browsing mode</a>
-        may leak private data to a third-party application that does not
-        respect the user's privacy setting. User agents should consider
-        presenting additional warnings or disabling the feature entirely when
-        in a private browsing mode.
+        might leak private data to a third-party application that does not
+        respect the user's privacy setting. User agents could present
+        additional warnings or disable the feature entirely when in a private
+        browsing mode.
         </li>
-        <li>The data passed to <a><code>navigator.share</code></a> may be used
-        to exploit buffer overflow or other remote code execution
+        <li>The data passed to <a><code>navigator.share</code></a> might be
+        used to exploit buffer overflow or other remote code execution
         vulnerabilities in native applications that receive shares. There is no
-        general way to guard against this, but implementors should be aware
-        that it is a possibility.
+        general way to guard against this, but implementors will want to be
+        aware that it is a possibility.
         </li>
       </ul>
     </section>