Skip to content

Commit c29d21f

Browse files
committed
docs(guide/e2e-testing): rename and fix formatting
1 parent 7a19a80 commit c29d21f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/content/guide/dev_guide.e2e-testing.ngdoc renamed to docs/content/guide/e2e-testing.ngdoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ To solve this problem, we have built an Angular Scenario Runner which simulates
1515
that will help you verify the health of your Angular application.
1616

1717
# Overview
18-
You will write scenario tests in JavaScript, which describe how your application should behave,
18+
You write scenario tests in JavaScript. These tests describe how your application should behave
1919
given a certain interaction in a specific state. A scenario is comprised of one or more `it` blocks
2020
(you can think of these as the requirements of your application), which in turn are made of
2121
**commands** and **expectations**. Commands tell the Runner to do something with the application
@@ -310,4 +310,4 @@ element('.btn-danger').click();
310310

311311
# Caveats
312312

313-
ngScenario does not work with apps that manually bootstrap using angular.bootstrap. You must use the ng-app directive.
313+
`ngScenario` does not work with apps that manually bootstrap using `angular.bootstrap`. You must use the `ng-app` directive.

0 commit comments

Comments
 (0)