more link tweaking

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: index.html
+next: /docs/tutorials/
 next-title: "A Game of Darts"
-prev: forms
+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.
 * Indices allow for high performance searches.
@@ skipping 57 matching lines @@
 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>
 
 This target shows you how to use
-<a href="http://api.dartlang.org/dart_indexed_db.html"
+<a href="https://api.dartlang.org/dart_indexed_db.html"
    target="_blank">dart:indexed_db</a>
 to store data to and retrieve data from the browser's IndexedDB.
 
 * [Run the app](#run-the-app)
 * [About the app: The basics](#the-basics)
 * [Details about IndexedDB](#details-about-indexeddb)
 * [Importing the IndexedDB library](#import-indexeddb)
 * [Checking for IndexedDB support](#checking-indexeddb)
 * [Creating and opening a database](#opening-indexeddb)
 * [Creating an object store](#creating-object-store)
@@ skipping 22 matching lines @@
 <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.
 
 <iframe class="running-app-frame"
         style="height:400px;width:600px;"
-        src="http://dart-lang.github.com/dart-tutorials-samples/web/target11/count_down/web/out/count_down.html">
+        src="http://dart-lang.github.io/dart-tutorials-samples/web/target11/count_down/web/out/count_down.html">
 </iframe>
 
 You can find the complete source code for this sample on github at
 <a href="https://github.com/dart-lang/dart-tutorials-samples/tree/master/web/target11/count_down" target="_blank">count_down</a>.
 
 ###Using developer tools to look at the database
 
 You can use the browser's developer tools
 to explore the IndexedDB databases used by your apps.
 In Chrome, select **View&nbsp;>&nbsp;Developer&nbsp;>&nbsp;Developer Tools**,
@@ skipping 41 matching lines @@
 The View-model queries the Model upon initialization
 and uses Web UI 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="http://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="http://api.dartlang.org/dart_async.html" target="_blank">dart:async</a> | Perform tasks asynchronously |
-| <a href="http://api.dartlang.org/dart_core.html" target="_blank">dart:core</a> | Use DateTime and Duration to manage time-related tasks |
-| <a href="http://pub.dartlang.org/packages/web_ui" target="_blank">package:web_ui</a> | Create UIs with data-binding and web components. |
+| <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://pub.dartlang.org/packages/web_ui" target="_blank">package:web_ui</a> | Create UIs with data-binding and web components. |
 {: .table }
 
 This target explains the Dart API for IndexedDB used by the count_down app.
 In addition, this target covers some interesting
 API related to dates, times, and timers.
 
 <aside class="alert" markdown="1">
 <strong>Note:</strong>
 This target does not cover Futures or Web UI.
 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 Web UI,
 check out the relevant recipes in the
 <a href="/docs/cookbook/">
        <i class="icon-food"> </i> Dart Cookbook</a>
 or read the Web UI tutorials in
-Targets <a href="/docs/tutorials/web-ui">6</a>,
-<a href="/docs/tutorials/templates">7</a>,
-<a href="/docs/tutorials/custom-elements">8</a>.
+Targets <a href="/docs/tutorials/web-ui/">6</a>,
+<a href="/docs/tutorials/templates/">7</a>,
+<a href="/docs/tutorials/custom-elements/">8</a>.
 
 </aside>
 
 ##Details about IndexedDB
 
 Some important facts you need to know about IndexedDB:
 
 * Each origin (host, protocol, and port) has its own set of databases.
 A unique name identifies each database within an origin.
 IndexedDB has a same-origin policy,
@@ skipping 188 matching lines @@
 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.
 
 Finally, `_initializeDatabase` creates an index.
 
-##Using an 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)
 
 Using an index provides two benefits:
 
@@ skipping 19 matching lines @@
 * unique, a boolean value.
 When true, the index ensures that the milestone name is unique.
 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="http://api.dartlang.org/dart_indexedDb/Transaction.html" target="_blank">Transaction</a>.
+<a href="https://api.dartlang.org/dart_indexedDb/Transaction.html" target="_blank">Transaction</a>.
 
 <aside class="alert" 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.
@@ skipping 179 matching lines @@
   return cursors.length.then((_) {
     return milestones.length;
   });
 }
 {% endprettify %}
 
 Because getting records does not modify the database,
 this transaction is readonly.
 
 You can use a
-<a href="http://api.dartlang.org/dart_indexedDb/Cursor.html" target="_blank">Cursor</a>
+<a href="https://api.dartlang.org/dart_indexedDb/Cursor.html" target="_blank">Cursor</a>
 object to step through the records in the database one by one,
 creating a Milestone object for each.
 The object store uses a stream to fire an event for each record
 retrieved from the database.
 By listening on the stream,
 your code can be notified for each record read.
 The count_down app creates a corresponding Milestone object
 in the internal list in memory for each database record retrieved.
 
 Open a cursor on a transaction's object store with `openCursor`.
@@ skipping 11 matching lines @@
 
 The openCursor() method returns a stream on which you can listen for events.
 Here,
 the stream is a broadcast stream,
 so the app can listen both for read events
 and for a final count of records retrieved.
 
 For each record retrieved from the database,
 an event fires and the callback function is called.
 A
-<a href="http://api.dartlang.org/dart_indexedDb/CursorWithValue.html" target="_blank">CursorWithValue</a>
+<a href="https://api.dartlang.org/dart_indexedDb/CursorWithValue.html" target="_blank">CursorWithValue</a>
 object, named `cursor` in this example,
 is passed to the callback function.
 Use `cursor.key` to get the key for the record just retrieved.
 Use `cursor.value` to get the value for that record.
 
 The _loadFromDB method returns a Future that returns the length of the stream.
 
 ##Other resources
 
 <ul>
@@ skipping 16 matching lines @@
 ###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.
 
 {% endcapture %}
 
 {% include tutorial.html %}