From 98e0c233403213dbda174e54238710876597f6a3 Mon Sep 17 00:00:00 2001 From: mhartington Date: Tue, 19 Apr 2016 10:36:53 -0400 Subject: [PATCH] docs(navController): update links References https://github.com/driftyco/ionic-site/issues/554 --- ionic/components/nav/nav-controller.ts | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/ionic/components/nav/nav-controller.ts b/ionic/components/nav/nav-controller.ts index ba002c3e2d..d9e993032d 100644 --- a/ionic/components/nav/nav-controller.ts +++ b/ionic/components/nav/nav-controller.ts @@ -37,7 +37,7 @@ import {ViewController} from './view-controller'; * specific NavController, most times you will inject and use a reference to the * nearest NavController to manipulate the navigation stack. * - *

Injecting NavController

+ * ### Injecting NavController * Injecting NavController will always get you an instance of the nearest * NavController, regardless of whether it is a Tab or a Nav. * @@ -57,8 +57,7 @@ import {ViewController} from './view-controller'; * } * } * ``` - * - *

Page creation

+ * ## Page creation * _For more information on the `@Page` decorator see the [@Page API * reference](../../../decorators/Page/)._ * @@ -72,8 +71,7 @@ import {ViewController} from './view-controller'; * example). They are destroyed when removed from the navigation stack (on * [pop()](#pop) or [setRoot()](#setRoot)). * - * - *

Lifecycle events

+ * ## Lifecycle events * Lifecycle events are fired during various stages of navigation. They can be * defined in any `@Page` decorated component class. *