aboutsummaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorTuncer Ayaz <[email protected]>2012-01-07 11:52:33 +0100
committerTuncer Ayaz <[email protected]>2012-03-15 13:39:49 +0100
commit1eca92e381a3cdc10f801808894dabb4026c366f (patch)
tree6b4632c210e13848359715fa3f92df5d70200d0b /lib
parent1588a1d4c109bd9c800cec098d4fa48a4472003a (diff)
downloadotp-1eca92e381a3cdc10f801808894dabb4026c366f.tar.gz
otp-1eca92e381a3cdc10f801808894dabb4026c366f.tar.bz2
otp-1eca92e381a3cdc10f801808894dabb4026c366f.zip
Fix typos in ct getting_started_chapter.xml
Diffstat (limited to 'lib')
-rw-r--r--lib/common_test/doc/src/getting_started_chapter.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/common_test/doc/src/getting_started_chapter.xml b/lib/common_test/doc/src/getting_started_chapter.xml
index 7de0912036..5b5f7475c9 100644
--- a/lib/common_test/doc/src/getting_started_chapter.xml
+++ b/lib/common_test/doc/src/getting_started_chapter.xml
@@ -90,7 +90,7 @@
<p>As you can understand from the illustration above, Common Test requires
that a test case generates a runtime error to indicate failure (e.g.
by causing a bad match error or by calling <c>exit/1</c>, preferrably
- through the <c>ct:fail/1/2</c> help function). A succesful execution is
+ through the <c>ct:fail/1,2</c> help function). A succesful execution is
indicated by means of a normal return from the test case function.
</p>
</section>
@@ -197,7 +197,7 @@
<pre>
1> ct:run_test([{suite, "check_log_SUITE"}]).</pre>
<p>
- The result from running our test is printed in log files on HTML format
+ The result from running our test is printed in log files in HTML format
(stored in unique log directories on different level). This illustration
shows the log file structure:
</p>