removing Web UI tutorials, updating remaining 4 to current release, + review pass

src/site/docs/tutorials/indexeddb/index.markdown

 ---
 layout: default
 title: "Use IndexedDB"
 description: "Use IndexedDB for persistence and offline capability for your app."
 has-permalinks: true
 tutorial:
   id: indexeddb
 next: 
-next-title: "A Game of Darts"
+next-title: "Home"
 prev: forms/
 prev-title: "Get Input from a Form"
 ---
 
 {% capture whats_the_point %}
 
 * IndexedDB is a new standard for client-side storage in modern web browsers.
 * Client-side storage provides persistence, offline capability,
 and other advantages.
 * IndexedDB lets you store significant amounts of structured data.
@@ skipping 36 matching lines @@
 such as images, arrays, maps, and objects using IndexedDB.
 The standard does not specify size limits for
 individual data items or for the database itself,
 but browsers may impose storage limits.
 
 IndexedDB provides several advantages.
 Your apps
 
 * can have full functionality even if a network connection is not available.
 * can cache data and restore state between invocations.
-* won't lose data if the network connected is interrupted.
+* won't lose data if the network connection is interrupted.
 * generate less network traffic.
 * perform better because data management happens on the local computer
 rather than over the Internet.
 
-<aside class="alert" markdown="1">
+<aside class="alert alert-info" markdown="1">
 <strong>Note:</strong>
 Some browsers don't yet support IndexedDB.
 Check
 <a href="http://caniuse.com/#feat=indexeddb"
    target="_blank">caniuse.com</a>
 for up-to-date information.
 Your app can check programmatically
 if the current platform supports IndexedDB
 and adjust accordingly.
 </aside>
@@ skipping 10 matching lines @@
 * [Checking for IndexedDB support](#checking-indexeddb)
 * [Creating and opening a database](#opening-indexeddb)
 * [Creating an object store](#creating-object-store)
 * [Using a name index](#using-a-name-index)
 * [Using transactions](#using-transactions)
 * [Adding data](#adding-data)
 * [Removing data](#removing-data)
 * [Clearing all data](#clearing-all-data)
 * [Using a cursor to get all the records](#getting-data)
 * [Other resources](#other-resources)
+* [What next?](#what-next)
 
 ##Run the app {#run-the-app}
 
 The `count_down` app below maintains a list of milestones
 and displays a countdown timer for each one.
 
 **Try it!**
 Enter the name, date, and time of a milestone&mdash;your
 birthday, for example&mdash;and click the plus (**+**) button.
-The app shows the milestone name briefly,
-starts a countdown timer,
-and then displays the amount of time remaining until the milestone occurs.
+The app starts a countdown timer
+and displays the amount of time remaining until the milestone occurs.
 The app updates the display every second.
 
 Close this browser window and reload
 <a href="index.html#run-the-app">this page</a>.
 The milestone you created still exists
 because the app stored it in an IndexedDB in the browser.
 
 Use the minus (**-**) button to the right of a milestone
 to delete that milestone.
 Use the **Clear** button to delete all the milestones.
@@ skipping 27 matching lines @@
 ##About the app: The basics {#the-basics}
 
 The count_down app uses a Model, View, View-model (MVVM) structure.
 
 ![Structure of the count_down app](images/MVVM-simple.png)
 
 * The **View-model**, in the center of the diagram,
 connects the View and the Model,
 using UI and Timer events
 to make changes to the Model.
-The MilestoneApp class is primary class
+The MilestoneApp class is the primary class
 that implements the View-Model&mdash;it
 manages the timer,
 and implements the app's business logic,
 which manages the information exchange between the Model and the View.
 
 * The **View** provides the user interface for the app.
-Two custom components implement the View in the count_down app:
+Two custom elements implement the View in the count_down app:
 CountDownComponent describes the user interface for the app as a whole,
 and MilestoneComponent describes the UI for an individual milestone.
 These components inform the View-model of UI events.
 
 * The **Model** contains and manages the data.
 The Model,
 implemented by the MilestoneStore class,
 manages a list of Milestone objects in memory
 and keeps an IndexedDB in sync with the list,
 saving the milestone data persistently.
 The View-model queries the Model upon initialization
 and uses Polymer data-bindings to keep the View in sync.
 Also, it uses Timer events to trigger updates in the Model.
 
 ###The libraries used by the count_down app 
 
 The count_down app uses the following libraries:
 
 | Library | Description |
 |---|---|
 | <a href="https://api.dartlang.org/dart_indexed_db.html" target="_blank">dart:indexed_db</a> | Save data into an indexed database for persistence and offline capability |
 | <a href="https://api.dartlang.org/dart_async.html" target="_blank">dart:async</a> | Perform tasks asynchronously |
 | <a href="https://api.dartlang.org/dart_core.html" target="_blank">dart:core</a> | Use DateTime and Duration to manage time-related tasks |
 | <a href="https://api.dartlang.org/polymer.html" target="_blank">Polymer</a> | Create UIs with custom elements and data binding. |
 {: .table }
 
 This tutorial explains the Dart API for IndexedDB used by the count_down app.
-In addition, this tutorial covers some interesting
-API related to dates, times, and timers.
 
-<aside class="alert" markdown="1">
+<aside class="alert alert-info" markdown="1">
 <strong>Note:</strong>
 This tutorial does not cover Futures or Polymer.
 For information about Futures,
 see
 <a href="/articles/using-future-based-apis/">Using Future Based APIs</a>
 and 
 <a href="/articles/futures-and-error-handling/">Futures and Error Handling</a>.
 For information about Polymer,
 refer to <a href="/docs/tutorials/polymer-intro/">Define a Custom Element</a>.
 
@@ skipping 123 matching lines @@
 The first two parameters indicate the name and version of the
 database to open.
 The first time the count_down app runs from a particular origin,
 `milestoneDB` version 1 gets created and opened.
 The next time the app runs from that same origin,
 the database is simply opened.
 
 The third parameter, `onUpgradeNeeded`,
 provides a callback function that gets called
 when an upgrade needed event is fired,
-which happens when a new database
+which happens when a new database is created
 or the version of a database is updated.
 This gives your app an opportunity to create an object store.
 The only place you can create an object store
 is within an upgrade needed event.
 You _must_ have an object store to add records to the database.
 The next section covers how to create an object store.
 
 The following flow chart describes the logic of the
 `window.indexedDB.open()` function.
 
 ![Logic flow of database creation](images/flowchart.png)
 
 Because creating and opening a database can take time,
 `window.indexedDB.open()` returns a Future object,
-which runs asynchronously and returns a value sometime in the future.
-The value is returned to a callback function
+which runs asynchronously and returns a value, the database object,
+sometime in the future.
+The database object is returned to a callback function
 registered with `then()`.
 In this example,
 the callback function is called `_loadFromDB()`.
 Using cursors,
 `_loadFromDB()` reads all the milestones 
 from the database and populates the app.
 The details are covered in
 [Using a cursor to get all the records](#getting-data).
 
 ##Creating an object store {#creating-object-store}
@@ skipping 33 matching lines @@
 Use the Database object's `createObjectStore()` method
 to create a new object store with the given name.
 Each object store must have a unique name.
 The count_down app uses one object store called `milestoneStore`.
 All the countdown milestones are stored and retrieved
 in this object store.
 
 The code sets `autoIncrement` on the object store to true.
 When autoIncrement is true,
 the database generates unique, primary keys for you,
-which saves you the trouble of doing so.
+which saves you the trouble of ensuring unique keys.
 
-Finally, `_initializeDatabase` creates an index.
+Finally, `_initializeDatabase` creates a name index.
 
 ##Using a name index
 
 An index provides a lookup table.
 You can associate a primary key with a field in the stored objects.
 In the example,
 the index associates a primary key with the milestoneName field.
 
 ![Use an index to allow for searches on a field in the objects](images/devtools-with-index.png)
 
@@ skipping 23 matching lines @@
 In the count_down app,
 if you try to add a milestone with the same name as another,
 it is this index that causes the add() to fail.
 
 ##Using transactions {#using-transactions}
 
 All database operations must be performed
 within a
 <a href="https://api.dartlang.org/dart_indexedDb/Transaction.html" target="_blank">Transaction</a>.
 
-<aside class="alert" markdown="1">
+<aside class="alert alert-info" markdown="1">
 <strong>Important: About the life-cycle of a transaction</strong>
 
 The life-cycle of a transaction is as follows:
 
 * Open a transaction.
 * Place requests on the transaction and register callbacks.
 * When there are no more requests
 and the last callback finishes, the transaction completes.
 
 So, a transaction remains alive until all requests are complete and
@@ skipping 233 matching lines @@
   <a href="/articles/futures-and-error-handling/">Futures and Error Handling</a>.
   </li>
   <li>
   For information about Polymer,
   read <a href="/docs/tutorials/polymer-intro">Define a Custom Element</a>.
   </li>
 </ul>
 
 ###What next?
 
-Check out our
-<a href="/codelabs/web-ui-writer/index.html" target="_blank"><i class="icon-beaker"> </i>Codelab</a>;
-it uses LocalStorage instead of IndexedDB to store data in the client.
-Try converting it to use IndexedDB.
+You've completed the tutorials!
+Check out the Dart
+[code samples](/samples/) and [articles](/articles/).
 
 {% endcapture %}
 
 {% include tutorial.html %}