Update Polymer components.

third_party/polymer/components/app-route/README.md

 
 <!---
 
 This README is automatically generated from the comments in these files:
 app-location.html  app-route-converter-behavior.html  app-route-converter.html  app-route.html
 
 Edit those files, and our readme bot will duplicate them over here!
 Edit this file, and the bot will squash your changes :)
 
 The bot does some handling of markdown. Please file a bug if it does the wrong
 thing! https://github.com/PolymerLabs/tedium/issues
 
 -->
 
 [![Build status](https://travis-ci.org/PolymerElements/app-route.svg?branch=master)](https://travis-ci.org/PolymerElements/app-route)
 
 
-##&lt;app-route&gt;
+## &lt;app-route&gt;
 
 `app-route` is an element that enables declarative, self-describing routing
 for a web app.
 
 > *n.b. app-route is still in beta. We expect it will need some changes. We're counting on your feedback!*
 
 In its typical usage, a `app-route` element consumes an object that describes
 some state about the current route, via the `route` property. It then parses
 that state using the `pattern` property, and produces two artifacts: some `data`
 related to the `route`, and a `tail` that contains the rest of the `route` that
@@ skipping 53 matching lines @@
 
 And the `subrouteData` will look like this: `{ id: '123' }`
 
 `app-route` is responsive to bi-directional changes to the `data` objects
 they produce. So, if `routeData.page` changed from `'article'` to `'about'`,
 the `app-route` will update `route.path`. This in-turn will update the
 `app-location`, and cause the global location bar to change its value.
 
 
 
-##&lt;app-location&gt;
+## &lt;app-location&gt;
 
 `app-location` is an element that provides synchronization between the
 browser location bar and the state of an app. When created, `app-location`
 elements will automatically watch the global location for changes. As changes
 occur, `app-location` produces and updates an object called `route`. This
 `route` object is suitable for passing into a `app-route`, and other similar
 elements.
 
 An example of the public API of a route object that describes the URL
 `https://elements.polymer-project.org/elements/app-location`:
@@ skipping 39 matching lines @@
 call `window.location.pushState` or `window.location.replaceState` followed by
 firing a `location-changed` event on `window`. i.e.
 
 ```javascript
 window.history.pushState({}, null, '/new_path');
 window.dispatchEvent(new CustomEvent('location-changed'));
 ```
 
 
 
-##&lt;app-route-converter&gt;
+## &lt;app-route-converter&gt;
 
 `app-route-converter` provides a means to convert a path and query
 parameters into a route object and vice versa. This produced route object
 is to be fed into route-consuming elements such as `app-route`.
 
 > n.b. This element is intended to be a primitive of the routing system and for
 creating bespoke routing solutions from scratch. To simply include routing in
 an app, please refer to [app-location](https://github.com/PolymerElements/app-route/blob/master/app-location.html)
 and [app-route](https://github.com/PolymerElements/app-route/blob/master/app-route.html).
 
@@ skipping 37 matching lines @@
 ```
 
 This is a simplified implementation of the `app-location` element. Here the
 `iron-location` produces a path and a query, the `iron-query-params` consumes
 the query and produces a queryParams object, and the `app-route-converter`
 consumes the path and the query params and converts it into a route which is in
 turn is consumed by the `app-route`.
 
 
 
-##Polymer.AppRouteConverterBehavior
+## Polymer.AppRouteConverterBehavior
 
 Provides bidirectional mapping between `path` and `queryParams` and a
 app-route compatible `route` object.
 
 For more information, see the docs for `app-route-converter`.