Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / test / doc / adv_scenarios / entry_point_overview.qbk

diff --git a/libs/test/doc/adv_scenarios/entry_point_overview.qbk b/libs/test/doc/adv_scenarios/entry_point_overview.qbk
index 1898e2e..a8cb681 100644 (file)
--- a/libs/test/doc/adv_scenarios/entry_point_overview.qbk
+++ b/libs/test/doc/adv_scenarios/entry_point_overview.qbk
@@ -1,5 +1,5 @@
 [/
- / Copyright (c) 2003 Boost.Test contributors 
+ / Copyright (c) 2003 Boost.Test contributors
  /
  / Distributed under the Boost Software License, Version 1.0. (See accompanying
  / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
@@ -13,7 +13,7 @@ The only thing you are required to do in case your program consists of more than
 is to indicate to the framework in which of the files it is supposed to generate function `main`.
 You do it by defining macro __BOOST_TEST_MODULE__ before the inclusion of any of the framework files.
 The value of this macro is used as a name of the [link ref_test_module test module] as well as the
-[link boost_test.tests_organization.test_tree.master_test_suite master test suite]. 
+[link boost_test.tests_organization.test_tree.master_test_suite master test suite].
 
 The reason for defining function `main` for you is twofold: