[css-paint-api] Remove normative words from notes.

Author: bfgeek

css-paint-api/Overview.bs

@@ -74,7 +74,7 @@ box based on that box's size (as generated by the layout stage) and computed sty
 This specification describes an API which allows developers to paint a part of a box in
 response to size / computed style changes with an additional <<image>> function.
 
-Note: In a future version of the spec, support may be added for defining the clip, global alpha,
+Note: In a future version of the spec, support could be added for defining the clip, global alpha,
     filter on a portion of a box (for example on the background layers).
 
 Paint Invalidation {#paint-invalidation}
@@ -107,9 +107,9 @@ When the computed style for a |box| changes, the user agent <em>must</em> run th
 Performing <a>draw a paint image</a> results in the <a>paint valid flag</a> for a <<paint()>>
 function on a box to be set to <a>paint-valid</a>.
 
-Note: In a future version of the spec, support may be added for partial invalidation. The user agent
-    will be able to specify a region of the rendering context which needs to be re-painted by the
-    paint class.
+Note: In a future version of the spec, support could be added for partial invalidation. The user
+    agent will be able to specify a region of the rendering context which needs to be re-painted by
+    the paint class.
 
 Paint Worklet {#paint-worklet}
 ==============================
@@ -315,9 +315,9 @@ called, the user agent <em>must</em> run the following steps:
 Note: The list of input properties should only be looked up once, the class doesn't have the
     opportunity to dynamically change its input properties.
 
-Note: In a future version of the spec, the author may be able to set an option to receive a
-    different type of RenderingContext. In particular the author may want a WebGL rendering context
-    to render 3D effects. There are complexities in setting up a WebGL rendering context to take the
+Note: In a future version of the spec, the author could have the ability to receive a different type
+    of RenderingContext. In particular the author may want a WebGL rendering context to render 3D
+    effects. There are complexities in setting up a WebGL rendering context to take the
     {{PaintSize}} and {{StylePropertyMap}} as inputs.
 </div>
 
@@ -438,7 +438,7 @@ negotiation</a> algorithm which is responsible for rendering an <<image>>.
 For the purposes of the <a>object size negotiation</a> algorithm, the paint image has no
 <a>intrinsic dimensions</a>.
 
-Note: In a future version of the spec, the author may be able to specify the <a>intrinsic
+Note: In a future version of the spec, the author could have the ability to specify the <a>intrinsic
     dimensions</a> of the paint image. This will probably be exposed as a callback allowing the
     author to define static <a>intrinsic dimensions</a> or dynamically updating the <a>intrinsic
     dimensions</a> based on computed style and size changes.
@@ -534,8 +534,8 @@ following steps:
         The user agent <em>may</em> also <a>create a WorkletGlobalScope</a> given the paint
         {{Worklet}} and use that.
 
-        Note: The user agent <em>may</em> use any policy for which {{PaintWorkletGlobalScope}} to
-            select or create. It may use a single {{PaintWorkletGlobalScope}} or multiple and
+        Note: The user agent can use any policy for which {{PaintWorkletGlobalScope}} to select or
+            create. For example it could use a single {{PaintWorkletGlobalScope}} or multiple and
             randomly assign between them.
 
     13. Run <a>invoke a paint callback</a> given |name|, |inputArguments|, |concreteObjectSize|,
@@ -565,10 +565,10 @@ When the user agent wants to <dfn>invoke a paint callback</dfn> given |name|, |i
 
         2. Let the image output be an <a>invalid image</a> and abort all these steps.
 
-        Note: This handles the case where there may be a paint worklet global scope which didn't
+        Note: This handles the case where there could be a paint worklet global scope which didn't
             receive the {{registerPaint(name, paintCtor)}} for |name| (however another global scope
-            did). A paint callback which is invoked on the other global scope may succeed, but wont
-            succeed on a subsequent frame when <a>draw a paint image</a> is called.
+            did). A paint callback which is invoked on the other global scope could succeed, but
+            wont succeed on a subsequent frame when <a>draw a paint image</a> is called.
 
     3. Let |definition| be the result of <a>get</a> |paintDefinitionMap|[|name|].
 
@@ -600,8 +600,8 @@ When the user agent wants to <dfn>invoke a paint callback</dfn> given |name|, |i
             - "height" - The height given by |concreteObjectSize|.
             - "alpha" - The <a for="paint definition">context alpha flag</a> given by |definition|.
 
-        Note: The |renderingContext| must not be re-used between invocations of paint. Implicitly
-            this means that there is no stored data, or state on the |renderingContext| between
+        Note: The |renderingContext| is not be re-used between invocations of paint. Implicitly this
+            means that there is no stored data, or state on the |renderingContext| between
             invocations. For example you can't setup a clip on the context, and expect the same clip
             to be applied next time the paint method is called.
 
@@ -622,13 +622,13 @@ When the user agent wants to <dfn>invoke a paint callback</dfn> given |name|, |i
 
         If an exception is <a>thrown</a> the let the image output be an <a>invalid image</a>.
 
-Note: The user agent <em>should</em> consider long running paint functions similar to long running
-    script in the main execution context. For example, they <em>should</em> show a "unresponsive
-    script" dialog or similar. In addition user agents <em>should</em> provide tooling within their
-    debugging tools to show authors how expensive their paint classes are.
+Note: The user agent can consider long running paint functions similar to long running script in the
+    main execution context. For example, they could show a "unresponsive script" dialog or similar.
+    In addition user agents could provide tooling within their debugging tools to show authors how
+    expensive their paint classes are.
 
-Note: The contents of the resulting image are not designed to be accessible. Authors <em>should</em>
-    communicate any useful information through the standard accessibility APIs.
+Note: The contents of the resulting image are not designed to be accessible. Authors can communicate
+    any useful information through the standard accessibility APIs.
 </div>
 
 Examples {#examples}