[Bug 19909] New: [Explainer]: Typos in 7 November 2012 draft

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19909

          Priority: P2
            Bug ID: 19909
          Assignee: dglazkov@chromium.org
            Blocks: 14949
           Summary: [Explainer]: Typos in 7 November 2012 draft
        QA Contact: public-webapps-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: miket@opera.com
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: Component Model
           Product: WebAppsWG

Hi there,

Found a couple of typos or minor grammar nits while reviewing the spec:

5.5 Lifecycle Methods
=====================

"The callbacks are invoked with this as the instance element."

-> add <code>this</code>


5.7 Error Handling
==================

"This situation is treated as if the definitions hasn't been loaded yet..."
s/hasn't/haven't/ or s/definitions/definition/?


6.3 CSS and Shadow DOM
======================

"Conversely , you can make the boundary even stronger by setting the
reset-style-inherifance attribute"

s/inherifance/inheritance/

"since they will appear as non-sensical babbling after the retargeting (what?
the element just reported that the mouse just moved from itself back to
itself?!)"

-> add a period to the end of the sentence.


7 Decorators vs. Custom Elements
================================

"Decorator shadows are never accessible with DOM."

-> with DOM methods?

9 Isolation, Confinement and Encapsulation
==========================================

"Component isolation can be viewed as combination of two parts"

-> as a combination


Appendix B. HTML Elements
=========================

"The insertion point is replaced with the elements' children..."

s/elements'/element's/


Appendix C. Custom Element Constructor Properties
=================================================

'b.outerHTML ⇒ "<button is="FancyButton"></button.html>"'

s/\.html//

Cheers,
Mike

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 8 November 2012 17:36:41 UTC