docs(): updates

core/src/components/nav/nav.tsx

@@ -1,44 +1,10 @@
-import {
+import { Build, Component, Element, Event, EventEmitter, Method, Prop, Watch } from '@stencil/core';
-  Build,
-  Component,
-  Element,
-  Event,
-  EventEmitter,
-  Method,
-  Prop,
-  Watch
-} from '@stencil/core';
 import { ViewLifecycle } from '../..';
-import {
+import { Animation, ComponentProps, Config, FrameworkDelegate, GestureDetail, Mode, NavComponent, NavOptions, NavOutlet, NavResult,QueueController, RouteID, RouteWrite, TransitionDoneFn, TransitionInstruction } from '../../interface';
-  Animation,
-  ComponentProps,
-  Config,
-  FrameworkDelegate,
-  GestureDetail,
-  Mode,
-  NavComponent,
-  NavOptions,
-  NavOutlet,
-  NavResult,
-  QueueController,
-  RouteID,
-  RouteWrite,
-  TransitionDoneFn,
-  TransitionInstruction
-} from '../../interface';
 import { assert } from '../../utils/helpers';
-import {
+import { TransitionOptions, lifecycle, transition } from '../../utils/transition';
-  TransitionOptions,
-  lifecycle,
-  transition
-} from '../../utils/transition';
 import { RouterIntent } from '../router/utils/constants';
-import {
+import { ViewController, ViewState, convertToViews, matches } from './view-controller';
-  ViewController,
-  ViewState,
-  convertToViews,
-  matches
-} from './view-controller';
 
 @Component({
   tag: 'ion-nav'

core/src/components/nav/readme.md

@@ -1,5 +1,7 @@
 # ion-nav
 
+Nav is a standalone component for loading arbitrary components and pushing to new components on to the stack.
+Unlike RouterOutlet, Nav is not tied to a particular router. Meaning that if we load a Nav component, and push other components to the stack, they will not affect the apps overall router. This fits use cased where you could have a modal, which needs it's own sub-navigation, but not make it tied to the apps URL.
 
 
 <!-- Auto Generated Below -->