minor docs tweaks

googlearchive · Jun 24, 2014 · e0d648f · e0d648f
1 parent b86dac3
commit e0d648f
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/core-animated-pages.html b/core-animated-pages.html
@@ -65,11 +65,11 @@
 In general, a transition is applied to elements marked with a certain attribute. For example,
 `hero-transition` applies the transition on elements with the `hero` and `hero-id` attribute.
 Among the transitions included with `core-animated-pages`, script-based transitions such as
-`hero-transition` generally look for elements up to one level of shadow root from the
+`hero-transition` generally look for elements up to one level of shadowRoot from the
 `core-animated-pages` element, and CSS-based transitions such as `cross-fade` look for elements
-within any shadow root of the page. This means which means you can use custom elements as a
-page and mark elements in their shadow roots as heroes, or mark elements in deeper shadow roots
-with other transitions.
+within any shadowRoot within the `core-animated-pages` element. This means you can use 
+custom elements as pages and mark elements in their shadowRoots as heroes, or mark 
+elements in deeper shadowRoots with other transitions.
 
 Example:
 
@@ -126,7 +126,7 @@
       // The below element is one level of shadow from the core-animated-pages and will
       // be transitioned.
       <div id="hero1" hero-id="foo" hero></div>
-      // The below element contains a hero inside its shadow root making it two levels away
+      // The below element contains a hero inside its shadowRoot making it two levels away
       // from the core-animated-pages, and will not be transitioned.
       <x-el></x-el>
     </template>

diff --git a/transitions/hero-transition.html b/transitions/hero-transition.html
@@ -59,7 +59,7 @@
 attribute and a single element appears to translate and scale smoothly between
 the two positions during a page transition.
 
-Both elements from the source and destination pages must shared the same `hero-id`
+Both elements from the source and destination pages must share the same `hero-id`
 and must both contain the `hero` attribute to trigger the transition. The separate
 `hero` attribute allows you to use binding to configure the transition: