Imported Upstream version 1.72.0

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

diff --git a/libs/test/doc/usage_recommendations.qbk b/libs/test/doc/usage_recommendations.qbk
index 24147ee..c35f626 100644 (file)
--- a/libs/test/doc/usage_recommendations.qbk
+++ b/libs/test/doc/usage_recommendations.qbk
@@ -102,7 +102,7 @@ Now run the test again under debugger and it will break at the point of failure.
 
 [section Command line usage recommendations]
 
-[h4 If you got fatal exception somewhere within test case, make program generate coredump by adding extra command
+[h4 If you got fatal exception somewhere within test case, make program generate core-dump by adding extra command
       line argument]
 If you got "memory access violation" message (or any other message indication fatal or system error) when you
 run you test, to get more information about the error location add
@@ -111,7 +111,7 @@ run you test, to get more information about the error location add
 --[link boost_test.utf_reference.rt_param_reference.catch_system catch_system_error]=no
 ]
 
-to the test run command line. Now run the test again and it will create a coredump you could analyze using you preferable
+to the test run command line. Now run the test again and it will create a core-dump you could analyze using you preferable
 debugger. Or run it under debugger in a first place and it will break at the point of failure.
 
 [h4 How to use test module build with Boost.Test framework under management of automated regression test facilities?]