[resize-observer] Removed the inline issues that were resolved. Added a note about potential deprecation in the future of contentRect

Author: Greg Whitworth

resize-observer-1/Overview.bs

@@ -150,8 +150,6 @@ ResizeObserver can observe different kinds of CSS sizes:
     };
 </pre>
 
-<p class='issue'>Is size the right name here? It's actually denoting which layout box we want to observe, possibly `box`?</p>
-
 This section is non-normative. An author may desire to observe more than one CSS box.
 In this case, author will need to use multiple ResizeObservers.
 
@@ -160,7 +158,7 @@ In this case, author will need to use multiple ResizeObservers.
     ro.observe(document.querySelector('#menu'), { box: 'content-box' });
 
     // Observe just the border box. Replaces previous observation.
-    ro.observe(document.querySelector('#menu'), { box: 'border-box' });
+    ro1.observe(document.querySelector('#menu'), { box: 'border-box' });
 </pre>
 
 <p class="note">This does not have any impact on which box dimensions are returned to the defined callback when the event is fired,
@@ -238,8 +236,7 @@ interface ResizeObserverEntry {
 };
 </pre>
 
-<p class="issue">Do we only want to return the box(es) that were requested to be observed, or all? Leaning: all</p>
-<p class="issue">Do we want to add a note explaining that contentRect is for compatibility reasons, and might be depreciated? Leaning: yes</p>
+<p class="note">contentRect is from the incubation phase of ResizeObserver and is only included for current web compat reasons. It may be deprecated in future levels.</p>
 
 <div dfn-type="attribute" dfn-for="ResizeObserverEntry">
     : <dfn>target</dfn>
@@ -290,8 +287,6 @@ interface ResizeObserverEntry {
     };
 </pre>
 
-<p class="issue">We're covering the dimensions of the extra boxes, do we want to also cover their positions similiar to that of the initial contentRect?</p>
-
 <h2 id="processing-model">Processing Model</h2>
 
 <h3 id="resize-observation-interface">ResizeObservation example struct</h3>