docs(ngRepeat): fix link to MDN

JonyD · Narretz · commit 4ff6c85792d5 · 2015-11-02T20:48:12.000+01:00
Closes #13226
diff --git a/src/ng/directive/ngRepeat.js b/src/ng/directive/ngRepeat.js
@@ -43,7 +43,7 @@
  * Version 1.4 removed the alphabetic sorting. We now rely on the order returned by the browser
  * when running `for key in myObj`. It seems that browsers generally follow the strategy of providing
  * keys in the order in which they were defined, although there are exceptions when keys are deleted
- * and reinstated. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete#Cross-browser_issues
+ * and reinstated. See the [MDN page on `delete` for more info](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete#Cross-browser_notes).
  *
  * If this is not desired, the recommended workaround is to convert your object into an array
  * that is sorted into the order that you prefer before providing it to `ngRepeat`.  You could

Original file line number	Diff line number	Diff line change
`@@ -43,7 +43,7 @@`
`43`	`43`	`* Version 1.4 removed the alphabetic sorting. We now rely on the order returned by the browser`
`44`	`44`	* when running `for key in myObj`. It seems that browsers generally follow the strategy of providing
`45`	`45`	`* keys in the order in which they were defined, although there are exceptions when keys are deleted`
`46`		`- * and reinstated. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete#Cross-browser_issues`
	`46`	+ * and reinstated. See the [MDN page on `delete` for more info](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete#Cross-browser_notes).
`47`	`47`	`*`
`48`	`48`	`* If this is not desired, the recommended workaround is to convert your object into an array`
`49`	`49`	* that is sorted into the order that you prefer before providing it to `ngRepeat`. You could