Address review comments

Author: captainbrosset

microsoft-edge/web-platform/release-notes/135.md

@@ -167,7 +167,7 @@ In order to avoid resizing the element every time the document is scrolled, the
 <!-- ---------- -->
 ###### CSS `dynamic-range-limit` property
 
-The `dynamic-range-limit` CSS property allows limiting the maximum brightness of HDR<!-- todo: define/expand HDR --> content.
+The `dynamic-range-limit` CSS property allows limiting the maximum brightness of High Dynamic Range (HDR) content.
 
 
 <!-- ---------- -->
@@ -255,7 +255,7 @@ _Self-links_ are excluded from this; links to a site's own pages can be styled a
 <!-- ---------- -->
 ###### Create service worker client and inherit service worker controller for iframe with `srcdoc`
 
-Documents created by iframes that use the `srcdoc` attribute are now service worker clients that are covered by their parent's service worker.<!-- todo: change plural to singular for clarity -->
+A service worker client is now created for iframes that use the `srcdoc` attribute. The created service worker client inherits from the service worker of the iframe's parent.
 
 
 <!-- ---------- -->
@@ -273,7 +273,7 @@ The `Float16Array` typed array is now supported.  Number values are rounded to h
 <!-- ---------- -->
 ###### HSTS tracking prevention
 
-Mitigates user tracking by third-parties via the HSTS<!-- todo: define HSTS --> cache.
+Mitigates user tracking by third-parties via the HTTP Strict Transport Security (HSTS) cache.
 
 This feature only allows HSTS upgrades for top-level navigations, and blocks HSTS upgrades for sub-resource requests.  Blocking such an HSTS upgrade makes it infeasible for third-party sites to use the HSTS cache in order to track a user across the web.
 
@@ -305,17 +305,17 @@ List of changes:
 <!-- ---------- -->
 ###### Observable API
 
-Observables are a popular reactive-programming paradigm to handle an asynchronous stream of push-based events.  Observables can be thought of as Promises but for multiple events, and aim to do what Promises did for callbacks and nesting.  That is, Observables allow ergonomic event handling, by providing an `Observable` object that represents the asynchronous flow of events.
+Observables are a popular reactive-programming paradigm to handle an asynchronous stream of push-based events.  Observables can be thought of as Promises but for multiple events. Observables let you write more linear and declarative-style code and avoid nestied callbacks.  That is, Observables allow ergonomic event handling, by providing an `Observable` object that represents the asynchronous flow of events.
 
-You can "subscribe" to this object to receive events as they come in, and call any of its operators or combinators to declaratively describe the flow of transformations through which events go.  This is in contrast with the _imperative_ version, which often requires complicated nesting with approaches such as `addEventListener()`.  For more on this, see the examples in the explainer.<!-- todo: link to the explainer.  if that's the next link, clarify. -->
+You can "subscribe" to this object to receive events as they come in, and call any of its operators to declaratively describe the flow of transformations through which events go.  This is in contrast with the _imperative_ version, which often requires complicated nesting with approaches such as `addEventListener()`.
 
 See the [W3C Observable specification](https://wicg.github.io/observable/).
 
 
 <!-- ---------- -->
 ###### Service worker client URL now ignores `history.pushState` changes
 
-The `Client.url` property of a service worker now ignores document URL changes that are made by the `history.pushState()` method and other similar history APIs.  The `Client.url` property is intended to be the creation URL of the HTML document,<!-- todo: check meaning of comma vs no comma --> which ignores such changes.
+The `Client.url` property of a service worker, which is the URL of the initial HTML document, now ignores changes that are made by the `history.pushState()` method and other similar history APIs.
 
 <!-- ---------- -->
 ###### Timestamps for RTC Encoded Frames
@@ -333,11 +333,7 @@ This change allows video conferencing applications which use WebRTC to implement
 <!-- ---------- -->
 ###### Use the `double` type for ProgressEvent's `loaded` and `total` attributes
 
-The `loaded` and `total` attributes of a `ProgressEvent` indicate the current progress.  The type of these attributes is now `double`, which gives you more control over the value than `int`<!-- todo: what was the previous type? --> gave.
-
-For example, you can now create a `ProgressEvent` with the value of `total` set to `1`, and then the value of `loaded` increases from `0` to `1` gradually.<!-- todo: how was it before? -->
-
-This behavior aligns the event with the default behavior of the `<progress>` HTML element, if the `max` attribute is omitted.
+The `loaded` and `total` attributes of a `ProgressEvent` indicate the current progress.  The type of these attributes is now a floating point number between `0` and `1`, which aligns `ProgressEvent` with the default behavior of the `<progress>` HTML element, when the `max` attribute is omitted.
 
 
 <!-- ---------- -->
@@ -380,7 +376,7 @@ The accessor properties of the `Intl.Locale` object are now deprecated, in favor
 
 The deprecated `navigator.xr.supportsSession` property has been removed from the WebXR API.
 
-In the WebXR specification in 2019, the `navigator.xr.supportsSession` property was marked as deprecated, and was replaced by the `navigator.xr.()` method.
+In the WebXR specification in 2019, the `navigator.xr.supportsSession` property was marked as deprecated, and was replaced by the `navigator.xr.isSessionSupported()` method.
 
 
 <!-- ---------- -->
@@ -427,7 +423,7 @@ The Digital Goods API allows a web application to get information about their di
 
 Expires on March 31, 2025.
 
-Web App LocalFolder Access allows a Microsoft Store-installed Progressive Web App (PWA) to access file content that was previously stored in the WinRT `ApplicationData.LocalFolder` folder by an earlier,<!-- todo: analyze implication of comma vs no comma --> UWP version of the application.
+Web App LocalFolder Access allows a Microsoft Store-installed Progressive Web App (PWA) to access file content that was previously stored in the WinRT `ApplicationData.LocalFolder` folder by an earlier version of the application.
 
 * [Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/LocalFolder/explainer.md)
 * [Feedback](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?labels=LocalFolder+Access,OriginTrialFeedback&amp;title=%5BLocalFolder%20Access%5D+Feedback)
@@ -440,7 +436,7 @@ Web App LocalFolder Access allows a Microsoft Store-installed Progressive Web Ap
 
 Expires on June 14, 2025.
 
-Granular per-document and per-element control over which content should (dis)allow<!-- todo: ungrammatical, confusing, clarify --> handwriting input.
+The `handwriting` attribute provides developers with a per-document and per-element way to control where handwriting input, such as when using a stylus, is allowed.
 
 * [Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Handwriting/explainer.md)
 * [Feedback](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?labels=Handwriting,OriginTrialFeedback&amp;title=%5BHandwriting%5D+Feedback)