apply reviewer suggestions

2 files changed, 45 insertions, 43 deletions

diff --git a/docs/elements-getting-started.adoc b/docs/elements-getting-started.adoc
index 5e810c8..7fbac91 100644
--- a/docs/elements-getting-started.adoc
+++ b/docs/elements-getting-started.adoc
@@ -6,76 +6,78 @@ layout: page
 
 # Getting Started with Vaadin Core Elements
 
-This page will guide you through the installation of Vaadin Core Elements bundle and help you get started with your first project using these elements.
+This page will guide you through the installation of the Vaadin Core Elements bundle and help you get started with your first project using these elements.
 
 ## Installation
 
-There are three ways to use Vaadin Core Elements in your project: Bower, CDN and a ZIP archive. The only difference between these options is the URL you will use to import the necessary files into your HTML page.
+There are three ways to use Vaadin Core Elements in your project: Bower, CDN, and a ZIP archive. The only difference between these options is the URL that you use to import the necessary files into your HTML page.
 
-### Create a new folder
+### Create a New Folder
 
-Start by creating a new folder for your project and change into the newly created folder.
+Start by creating a new folder for your project and change to the folder.
 
+[subs="normal"]
 ----
-$ mkdir my-project
-$ cd my-project
+[prompt]#$# [command]#mkdir# [replaceable]#my-project#
+[prompt]#$# [command]#cd# [replaceable]#my-project#
 ----
 
 ### Install Vaadin Core Elements
 
 #### Bower
 
-Recommended way to manage your front-end dependencies is using link:http://bower.io[Bower]. Follow the link:http://bower.io/#install-bower[Bower installation instructions], then run the following command inside your project folder to install the most recent stable release.
+The recommended way to manage your front-end dependencies is to use link:http://bower.io[Bower]. Follow the link:http://bower.io/#install-bower[Bower installation instructions], then run the following command inside your project folder to install the most recent stable release.
 
-[source]
+[subs="normal"]
 ----
-$ bower install --save vaadin-core-elements
+[prompt]#$# [command]#bower# install --save [replaceable]#vaadin-core-elements#
 ----
 
-This will download Vaadin Core Elements bundle and its dependencies into the `bower_components` folder inside your project's folder.
+This will download the Vaadin Core Elements bundle and its dependencies into the [filename]#bower_components# folder under your project's folder.
 
-If you wish to use a development snapshot version of some element, you can install/update that separately. For example:
+If you wish to use a development snapshot version of some element, you can install and update that separately. For example:
 
+[subs="normal"]
 ----
-$ bower install --save vaadin-grid#master
+[prompt]#$# [command]#bower# install --save [replaceable]#vaadin-grid##master
 ----
 
 #### CDN
 
-You can use Vaadin Core Elements from CDN (see example below). This is especially convenient for services like JSFiddle, Codepen.io, etc.
+You can use Vaadin Core Elements from our link:https://en.wikipedia.org/wiki/Content_delivery_network[CDN] server. This is especially convenient for services like JSFiddle, Codepen.io, etc.
 
-For example, to import vaadin-grid, use the following URL:
+For example, to import [vaadinelement]#vaadin-grid#, use the following URL:
 
 ----
-https://cdn.vaadin.com/vaadin-core-elements/latest/vaadin-grid/vaadin-grid.html
+<link href="https://cdn.vaadin.com/vaadin-core-elements/latest/vaadin-grid/vaadin-grid.html" rel="import">
 ----
 
 To import all Vaadin Core Elements, use the following URL:
 
 ----
-https://cdn.vaadin.com/vaadin-core-elements/latest/vaadin-core-elements/vaadin-core-elements.html
+<link href="https://cdn.vaadin.com/vaadin-core-elements/latest/vaadin-core-elements/vaadin-core-elements.html" rel="import">
 ----
 
 You can also use the nightly snapshot versions of any component, e.g.
 
 ----
-https://cdn.vaadin.com/vaadin-core-elements/master/vaadin-grid/vaadin-grid.html
+<link href="https://cdn.vaadin.com/vaadin-core-elements/master/vaadin-grid/vaadin-grid.html" rel="import">
 ----
 
-#### Download ZIP
+#### Download as a ZIP
 
 1. Download the latest release ZIP archive from the link:https://github.com/vaadin/vaadin-core-elements/releases[GitHub releases page]
-2. Extract the archive under your project folder, for example `deps`.
+2. Extract the archive under your project folder, for example in a [filename]#deps# folder.
 
 ### Create a HTML file
 
-Create a new HTML file (for example `index.html`) inside your project folder and copy the following code into it.
+Create a new HTML file (for example [filename]#index.html#) inside your project folder and copy the code below into it.
 
 Pay attention to the following details:
 
- - HTML5 doctype (`<!doctype html>`) is required for everything to work smoothly.
- - You need to adjust how the `webcomponents-lite.min.js` polyfill and `vaadin-core-elements.html` are imported according to the installation option you selected.
- - Notice how the JavaScript logic waits for `WebComponentsReady` event before accessing the elements.
+ - HTML5 doctype [elementname]#!doctype html# is required for everything to work smoothly.
+ - You need to adjust how the [filename]#webcomponents-lite.min.js# polyfill and [filename]#vaadin-core-elements.html# are imported according to the installation option you selected.
+ - Notice how the JavaScript logic waits for [classname]#WebComponentsReady# event before accessing the elements.
 
 
 **Serving the files during development**, when using Bower or the ZIP archive:
@@ -144,7 +146,7 @@ Due to browser security restrictions, serving HTML imports from a `file:///` URL
 </html>
 ----
 
-After you have created the file and you have a local server serving the files, you should be able to open up the application in your browser at http://localhost:3000/index.html (notice, that the port 3000 may vary depending on the server you use).
+After you have created the file and you have a local server serving the files, you should be able to open up the application in your browser at http://localhost:3000/index.html (notice that the port number may vary depending on the server you use).
 
 +++
 <!-- Assumes .w-arrow-button and .blue class names from vaadin.com theme. Will fallback to a plain link. -->
diff --git a/docs/elements-introduction.adoc b/docs/elements-introduction.adoc
index 1f61324..5876e05 100644
--- a/docs/elements-introduction.adoc
+++ b/docs/elements-introduction.adoc
@@ -8,11 +8,11 @@ layout: page
 
 ## Introduction
 
-Vaadin Core Elements is a free and open source set of high quality link:http://webcomponents.org[Web Components] for building mobile and desktop web applications in modern browsers. It builds on top of Google’s link:http://www.polymer-project.org[Polymer] library, and augments the link:https://elements.polymer-project.org[Iron, Paper and other element sets of Polymer] with elements that are needed in building business applications.
+Vaadin Core Elements is a free and open source set of high quality link:http://webcomponents.org[Web Components] for building mobile and desktop web applications in modern browsers. It builds on top of Google’s link:http://www.polymer-project.org[Polymer] library, and augments the link:https://elements.polymer-project.org[Iron, Paper, and other element sets of Polymer] with elements that are needed in building business applications.
 
-Although based on Polymer, Vaadin Elements can be used together with any other web framework which has support for Web Components. See the "Integrations" section for examples how to use the elements together with different JavaScript frameworks and libraries, such as Angular 2 and React.
+Although based on Polymer, Vaadin Elements can be used together with any other web framework that has support for Web Components. See the  link:integrations/polymer.html[Integrations] section for examples how to use the elements together with different JavaScript frameworks and libraries, such as Angular 2 and React.
 
-If you wish to use Vaadin elements with link:http://gwtproject.org[GWT], you can use link:https://vaadin.com/gwt[GWT Polymer Elements]
+If you wish to use Vaadin elements with link:http://gwtproject.org[GWT], you can use link:https://vaadin.com/gwt[GWT Polymer Elements].
 
 Vaadin Core Elements includes the following elements:
 
@@ -21,50 +21,50 @@ Vaadin Core Elements includes the following elements:
  - link:/docs/-/part/elements/vaadin-grid/overview.html[Grid]
  - link:/docs/-/part/elements/vaadin-upload/vaadin-upload-overview.html[Upload]
 
-Learn more about the benefits of using Vaadin elements from the link:https://vaadin.com/elements[Vaadin Elements page »]
+Learn more about the benefits of using Vaadin elements from the link:https://vaadin.com/elements[Vaadin Elements page].
 
 ## Background
 
 ### Web Components
 
-Web Components is a collection of HTML standards (under development, April 2016), which together provide web developers the tools to extend the native web platform with similar tools as the browser vendors have been using for creating the built-in standard elements, such as `<video>`, `<input type="date">` and so on.
+Web Components is a collection of HTML standards (under development, April 2016), which together provide web developers the tools to extend the native web platform with similar tools as the browser vendors have been using for creating the built-in standard elements, such as [elementname]#video#, [elementname]#input type="date"#, and so on.
 
 The four specifications that together form Web Components are:
 
-- **Template element** +
-  “The HTML template element `<template>` is a mechanism for holding client-side content that is not to be rendered when a page is loaded but may subsequently be instantiated during runtime using JavaScript.”
+*Template element*::
+  "The HTML template element [elementname]#template# is a mechanism for holding client-side content that is not rendered when a page is loaded. But it may be instantiated in runtime"
 
-- **Shadow DOM** +
-  “Shadow DOM provides encapsulation for the JavaScript, CSS, and templating in a Web Component. Shadow DOM makes it so these things remain separate from the DOM of the main document.” +
-  “Why would you want to keep some code separate from the rest of the page? One reason is that on a large site, for example, if the CSS is not carefully organized, the styling for the navigation can "leak" into the main content area where it was not intended to go, or vice-versa. As a site or an app scales, this kind of thing becomes difficult to avoid.”
+*Shadow DOM*::
+  "Shadow DOM provides encapsulation for the JavaScript, CSS, and templating in a Web Component. Shadow DOM allows keeping them separate from the DOM of the main document."
+  "Why would you want to keep some code separate from the rest of the page? One reason is that on a large site, for example, if the CSS is not carefully organized, the styling for the navigation can "leak" into the main content area where it was not intended to go, or vice-versa. As a site or an app scales, this kind of thing becomes difficult to avoid."
 
-- **HTML Imports** +
-  “HTML Imports is a way to include HTML documents in other HTML documents. You're not limited to markup either. An import can also include CSS, JavaScript, or anything else an .html file can contain. In other words, this makes imports a fantastic tool for loading related HTML/CSS/JS.”
+*HTML Imports*::
+  "HTML Imports is a way to include HTML documents in other HTML documents. You're not limited to markup either. An import can also include CSS, JavaScript, or anything else an .html file can contain. In other words, this makes imports a fantastic tool for loading related HTML/CSS/JS."
 
-- **Custom Elements** +
-  “Custom Elements allow web developers to define new types of HTML elements. It's quite possibly the most important as Web Components don't exist without the features unlocked by custom elements.”
+*Custom Elements*::
+  "Custom Elements allow web developers to define new types of HTML elements. It's quite possibly the most important as Web Components don't exist without the features unlocked by custom elements."
 
 Descriptions provided by link:https://developer.mozilla.org/en-US/[MDN] and link:http://www.html5rocks.com/en/[HTML5 Rocks].
 
-link:http://webcomponents.org[Learn more about Web Components »]
+link:http://webcomponents.org[Learn more about Web Components]
 
 ### Polymer
 
 The Polymer library is designed to make it easier and faster for developers to create great, reusable components for the modern web.
 
-It provides a declarative syntax that makes it simpler to define custom elements, and it adds features like templating, two-way data binding and property observation to help you build powerful, reusable elements with less code.
+It provides a declarative syntax that makes it simpler to define custom elements, and adds features like templating, two-way data binding, and property observation to help you build powerful, reusable elements with less code.
 
 The Polymer team also builds and maintains a large collection of custom elements, and the most prominent one is the Paper collection. The Paper elements are Google’s reference implementation of Material Design for the web.
 
-link:https://www.polymer-project.org[Learn more about Polymer »]
+link:https://www.polymer-project.org[Learn more about Polymer]
 
-link:https://elements.polymer-project.org[Browse Polymer Element Catalog »]
+link:https://elements.polymer-project.org[Browse Polymer Element Catalog]
 
 ## Browser compatibility
 
 The standards of Web Components are on the cutting-edge of web technologies and as such they are not yet fully supported in all browsers. Vaadin elements rely on polyfills to fill the gap and can therefore support the latest versions of all major browsers.
 
-The current set of supported browsers for Vaadin Core Elements is listed on the table below.
+The current set of supported browsers for Vaadin Core Elements is listed on the table below:
 
 |===
 | IE / Edge | Firefox | Chrome, desktop | Chrome, Android | Safari, OS X | Safari, iOS