add redirects for broken links #777

_includes/v2_fluid/component-docs/navigation.html

@@ -6,7 +6,7 @@ <h2 id="navigation" class="section-header">Navigation</h2>
 
 _For more in depth information on navigation, see the [Nav API reference](../api/components/nav/Nav)._
 
-Navigation is how users move between different pages in your app. Ionic's navigation follows standard native navigation concepts, like [those in iOS](https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/Navigation.html). In order to enable native-like navigation, we've built a few new navigation components that might feel different for developers used to traditional desktop browser navigation.
+Navigation is how users move between different pages in your app. Ionic's navigation follows standard native navigation concepts, like [those in iOS](https://developer.apple.com/library/content/documentation/WindowsViews/Conceptual/ViewControllerCatalog/Chapters/NavigationControllers.html#//apple_ref/doc/uid/TP40011313-CH2-SW1). In order to enable native-like navigation, we've built a few new navigation components that might feel different for developers used to traditional desktop browser navigation.
 
 <!--
 Like native apps, URLs are not required for navigation in Ionic.  Instead, pages are pushed and popped on and off a navigation controller's page stack.  URLs can be used to link back to unique, important parts of your app ("deeplinking") but don't define navigation as your app runs.

_server/redirects.json

@@ -1,3 +1,11 @@
 {
-  "/docs/v2/resources/resources/what-is/": "http://ionicframework.com/docs/v2/cli/"
+  "/docs/v2/resources/resources/what-is": "/docs/v2/cli/",
+  "/docs/v2/api/components/config/Config": "/docs/v2/api/config/Config",
+  "/docs/v2/api/components/Tabs/Tab": "/docs/v2/api/components/tabs/Tab",
+  "/docs/v2/api/components/nav/NavController": "/docs/v2/api/navigation/NavController/",
+  "/docs/v2/api/tab/Tab": "/docs/v2/api/components/tabs/Tab/",
+  "/docs/v2/api/menu/Menu": "/docs/v2/api/components/menu/Menu",
+  "/docs/v2/api/components/nav/NavBar": "/docs/v2/api/components/navbar/NavBar",
+  "/docs/v2/native/ibeacon/LocationManager": "/docs/v2/native/ibeacon/",
+  "/docs/v2/native/estimotebeacons/undefined": "/docs/v2/native/estimotebeacons"
 }

docs/v2/faq/index.md

@@ -390,7 +390,7 @@ This happens when you try and bind a property on an element that doesn't have th
 
 ### No provider for ControlContainer! (NgControlName -> ControlContainer)
 
-This error is a more specific version of the `No provider` error above.  It happens when you use a form control like [NgControlName](https://angular.io/docs/js/latest/api/core/NgControlName-class.html) without specifying a parent [NgForm](https://angular.io/docs/js/latest/api/core/NgForm-class.html) or [NgFormModel](https://angular.io/docs/js/latest/api/core/NgFormModel-class.html).  In most cases, this can be resolved by making sure your form control is within an actual form element.  NgForm uses `form` as a selector so this will instantiate a new NgForm:
+This error is a more specific version of the `No provider` error above.  It happens when you use a form control like NgControlName without specifying a parent [NgForm](https://angular.io/docs/ts/latest/api/forms/index/NgForm-directive.html) or NgFormModel.  In most cases, this can be resolved by making sure your form control is within an actual form element.  NgForm uses `form` as a selector so this will instantiate a new NgForm:
 
 ```ts
 @Component({
@@ -400,4 +400,3 @@ This error is a more specific version of the `No provider` error above.  It happ
     '</form>'
 })
 ```
-