anchor.diff:  
   After that, in your project root you should have `bower_components` directory with all elements declared by bower.json together with the elements’ requirements. List contents of the `bower_components` directory to verify that, it should contain these subdirectories:
   
  -.Contents of the bower_components directory
  +.Contents of the bower_components Directory
   ----
   app-layout
   font-roboto
  
positive.code: . `Vaadin DatePicker`, as well as native HTML5 `<input type="date">`, gives the date value as an ISO-formatted `string`. To keep the simplicity, in our application we also store dates as strings, avoiding conversions.
  ====
  
  === Mock heroes data
  
  Add `app/mock-heroes.ts` file with some heroes data:
  
  
negative.code: 
  We also add a few positioning style rules for the `paper-icon-button`.
  
  ==== Dynamic Toolbar Shadow
  
  To make the toolbar look better, we make the application toolbar to have a shadow that is shown only for the hero detail view, but not for the heroes list view. For this purpose we bind the `raised` class of the `<app-toolbar>` to `isInChildView` property and add a style rule which applies the shadow mixin from `paper-styles` to the `<app-toolbar>` when it has the `raised` class.
  
  == Wrap Up
  
  All the tutorial steps are complete. Now you can use all powers of Polymer elements in your Angular 2 applications and know how to do it.
  
  TODO: Link the resulting application code repository in this section when it gets published.
  
  === Next Steps
  
  There are several ways of improvement for our application. For example, you might want to add an explicit “Save” button to the hero detail editor and make the user able to intentionally submit or discard their changes. To do that, use the `ngForm` directive. See the https://angular.io/docs/ts/latest/guide/forms.html[Forms Chapter] in the Angular 2 Basics guide for the detailed instructions.
  
  