From ad6e765bcd4f35a282ef00e38ed9129f3a5c1d83 Mon Sep 17 00:00:00 2001
From: Hans Bolinder <hasse@erlang.org>
Date: Thu, 1 Sep 2016 14:32:27 +0200
Subject: doc: Correct errors introduced by Editorial changes

Fix some older errors as well.
---
 lib/common_test/doc/src/ct_hooks_chapter.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'lib/common_test/doc/src/ct_hooks_chapter.xml')

diff --git a/lib/common_test/doc/src/ct_hooks_chapter.xml b/lib/common_test/doc/src/ct_hooks_chapter.xml
index 1998f15697..0e4c35e11f 100644
--- a/lib/common_test/doc/src/ct_hooks_chapter.xml
+++ b/lib/common_test/doc/src/ct_hooks_chapter.xml
@@ -374,7 +374,7 @@
      <title>Example CTH</title>
      <p>The following CTH logs information about a test run into a format 
        parseable by <seealso marker="kernel:file#consult-1">file:consult/1</seealso> 
-       (in <c>Kernel</c>):
+       (in Kernel):
      </p>
      <code>
  %%% @doc Common Test Example Common Test Hook module.
@@ -499,13 +499,13 @@
        <tag><c>cth_log_redirect</c></tag>
        <item>
        <p>Built-in</p>
-       <p>Captures all <c>error_logger</c> and <c>SASL</c> logging 
+       <p>Captures all <c>error_logger</c> and SASL logging
 	events and prints them to the current test case log. If an event cannot be 
 	associated with a test case, it is printed in the <c>Common Test</c> framework log. 
 	This happens for test cases running in parallel and events occuring
 	in-between test cases. You can configure the level of
-	<seealso marker="sasl:sasl_app"><c>SASL</c></seealso> events report
-	using the normal <c>SASL</c> mechanisms.</p>
+	<seealso marker="sasl:sasl_app">SASL</seealso> events report
+	using the normal SASL mechanisms.</p>
        </item>
        <tag><c>cth_surefire</c></tag>
        <item>
-- 
cgit v1.2.3