diff options
Diffstat (limited to 'docs/content/tutorial/step_11.ngdoc')
| -rw-r--r-- | docs/content/tutorial/step_11.ngdoc | 12 | 
1 files changed, 4 insertions, 8 deletions
| diff --git a/docs/content/tutorial/step_11.ngdoc b/docs/content/tutorial/step_11.ngdoc index 4b82367d..9a549516 100644 --- a/docs/content/tutorial/step_11.ngdoc +++ b/docs/content/tutorial/step_11.ngdoc @@ -11,14 +11,11 @@ In this step, you will improve the way our app fetches data.  <div doc-tutorial-reset="11"></div> -The next improvement we will make to our app is to define a custom service that represents a {@link -http://en.wikipedia.org/wiki/Representational_State_Transfer RESTful} client. Using this client we +The next improvement we will make to our app is to define a custom service that represents a [RESTful](http://en.wikipedia.org/wiki/Representational_State_Transfer) client. Using this client we  can make XHR requests for data in an easier way, without having to deal with the lower-level {@link  api/ng.$http $http} API, HTTP methods and URLs. -The most important changes are listed below. You can see the full diff on {@link -https://github.com/angular/angular-phonecat/compare/step-10...step-11 -GitHub}: +The most important changes are listed below. You can see the full diff on [GitHub](https://github.com/angular/angular-phonecat/compare/step-10...step-11):  ## Template @@ -55,7 +52,7 @@ controller's constructor in that both can declare dependencies via function argu  service declared a dependency on the `$resource` service.  The {@link api/ngResource.$resource `$resource`} service makes it easy to create a -{@link http://en.wikipedia.org/wiki/Representational_State_Transfer RESTful} client with just a few +[RESTful](http://en.wikipedia.org/wiki/Representational_State_Transfer) client with just a few  lines of code. This client can then be used in our application, instead of the lower-level {@link  api/ng.$http $http} service. @@ -130,8 +127,7 @@ service correctly.  The {@link api/ngResource.$resource $resource} service augments the response object  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 -https://github.com/pivotal/jasmine/wiki/Matchers Jasmine matcher}. When the +solve the problem, we use a newly-defined `toEqualData` [Jasmine matcher](https://github.com/pivotal/jasmine/wiki/Matchers). When the  `toEqualData` matcher compares two objects, it takes only object properties into account and  ignores methods. | 
