aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarko Bonaci2013-10-08 21:10:42 +0200
committerPete Bacon Darwin2013-10-09 11:30:47 +0100
commit8469779a8e18ebf8ff90072872735b1730fdcc70 (patch)
tree20877c34da2045b52eb781a14f3ea12bdc095854
parent3374e35953f41fb255fff276e43afd2fc997f1d7 (diff)
downloadangular.js-8469779a8e18ebf8ff90072872735b1730fdcc70.tar.bz2
docs(tutorial/step11): correct Jasmine Matcher link
Link http://pivotal.github.com/jasmine/jsdoc/symbols/jasmine.Matchers.html is no longer valid. Closes #4329
-rw-r--r--docs/content/tutorial/step_11.ngdoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/content/tutorial/step_11.ngdoc b/docs/content/tutorial/step_11.ngdoc
index aff35703..53f2dd3d 100644
--- a/docs/content/tutorial/step_11.ngdoc
+++ b/docs/content/tutorial/step_11.ngdoc
@@ -135,7 +135,7 @@ The {@link api/ngResource.$resource $resource} service augments the response obj
with methods for updating and deleting the resource. If we were to use the standard `toEqual`
matcher, our tests would fail because the test values would not match the responses exactly. To
solve the problem, we use a newly-defined `toEqualData` {@link
-http://pivotal.github.com/jasmine/jsdoc/symbols/jasmine.Matchers.html Jasmine matcher}. When the
+https://github.com/pivotal/jasmine/wiki/Matchers Jasmine matcher}. When the
`toEqualData` matcher compares two objects, it takes only object properties into account and
ignores methods.