From 92304323b10d2917abca2f38598e34c7b41f92a2 Mon Sep 17 00:00:00 2001 From: Fernando Correia Date: Sun, 15 Jul 2012 13:18:42 -0300 Subject: docs(tutorial): correct typos and clarify a few sections --- docs/content/tutorial/step_03.ngdoc | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'docs/content/tutorial/step_03.ngdoc') diff --git a/docs/content/tutorial/step_03.ngdoc b/docs/content/tutorial/step_03.ngdoc index 91670f52..18d0fca9 100644 --- a/docs/content/tutorial/step_03.ngdoc +++ b/docs/content/tutorial/step_03.ngdoc @@ -56,7 +56,7 @@ __`app/index.html`:__ We added a standard HTML `` tag and used angular's {@link api/ng.filter:filter $filter} function to process the input for the -`ngRepeat` directive. +{@link api/ng.directive:ngRepeat ngRepeat} directive. This lets a user enter search criteria and immediately see the effects of their search on the phone list. This new code demonstrates the following: @@ -176,12 +176,14 @@ ngBindTemplate} directives, which are invisible to the user while the page is lo Refresh the browser tab with the end-to-end test runner to see the test fail. To make the test pass, edit the `index.html` template to add a `div` or `p` element with `id` `"status"` and content -with the `query` binding. +with the `query` binding, prefixed by "Current filter:". For instance: -* Add a `pause()` statement into an end-to-end test and rerun it. You'll see the runner pause; this -gives you the opportunity to explore the state of your application while it is displayed in the -browser. The app is live! You can change the search query to prove it. Notice how useful this is -for troubleshooting end-to-end tests. +