From 0e293d2a97bfbac0b1f501a38e4402726e4fe718 Mon Sep 17 00:00:00 2001
From: Jesse Palmer <jesselpalmer@gmail.com>
Date: Tue, 7 Oct 2014 20:29:52 -0400
Subject: [PATCH] docs(ngIf): update out-of-date link

---
 src/ng/directive/ngIf.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ng/directive/ngIf.js b/src/ng/directive/ngIf.js
index 671ee727e..af759a48e 100644
--- a/src/ng/directive/ngIf.js
+++ b/src/ng/directive/ngIf.js
@@ -19,7 +19,7 @@
  * Note that when an element is removed using `ngIf` its scope is destroyed and a new scope
  * is created when the element is restored.  The scope created within `ngIf` inherits from
  * its parent scope using
- * [prototypal inheritance](https://github.com/angular/angular.js/wiki/The-Nuances-of-Scope-Prototypal-Inheritance).
+ * [prototypal inheritance](https://github.com/angular/angular.js/wiki/Understanding-Scopes#javascript-prototypal-inheritance).
  * An important implication of this is if `ngModel` is used within `ngIf` to bind to
  * a javascript primitive defined in the parent scope. In this case any modifications made to the
  * variable within the child scope will override (hide) the value in the parent scope.