fixed bullet points in markdown

1 files changed, 10 insertions, 10 deletions

diff --git a/doc/markdown/faq.md b/doc/markdown/faq.md
index d253290..97539d9 100644
--- a/doc/markdown/faq.md
+++ b/doc/markdown/faq.md
@@ -62,20 +62,20 @@ using doctest::Approx;
 
 Here are a couple of differences:
 
-– the main one is that only doctest from the C++ frameworks is usable next to your production code (speed of compilation, ability to remove the tests from the binary, ability to execute tests/code/both, ability to have tests in multiple shared objects and still a single registry for all of them)
-– doctest is a single header – Google Test has to be built as a separate static library and linked against.
-– doctest has the concept of [**Subcases**](https://github.com/onqtam/doctest/blob/master/doc/markdown/tutorial.md#test-cases-and-subcases) which is a much cleaner way to share setup and teardown code between tests compared to fixtures and class inheritance – Google Test is quite verbose!
-– doctest compiles faster and probably runs faster (although the runtime becomes an issue only when you have millions of asserts)
-– doctest asserts are thread-safe even on Windows (Google Test uses pthreads so thread-safe asserts are available only on UNIX)
-– doctest overall has a simpler API
+- the main one is that only doctest from the C++ frameworks is usable next to your production code (speed of compilation, ability to remove the tests from the binary, ability to execute tests/code/both, ability to have tests in multiple shared objects and still a single registry for all of them)
+- doctest is a single header - Google Test has to be built as a separate static library and linked against.
+- doctest has the concept of [**Subcases**](https://github.com/onqtam/doctest/blob/master/doc/markdown/tutorial.md#test-cases-and-subcases) which is a much cleaner way to share setup and teardown code between tests compared to fixtures and class inheritance - Google Test is quite verbose!
+- doctest compiles faster and probably runs faster (although the runtime becomes an issue only when you have millions of asserts)
+- doctest asserts are thread-safe even on Windows (Google Test uses pthreads so thread-safe asserts are available only on UNIX)
+- doctest overall has a simpler API
 
 but there are also some areas in which doctest is lacking:
 
-– value-parameterized tests
-– death tests (where you check if calling a certain function doesn’t simply throw but if it crashes the process)
-– doctest has some integration with mocking libraries but Google Test works perfectly with Google Mock (although doctest should in theory work with it as well)
+- value-parameterized tests
+- death tests (where you check if calling a certain function doesn’t simply throw but if it crashes the process)
+- doctest has some integration with mocking libraries but Google Test works perfectly with Google Mock (although doctest should in theory work with it as well)
 
-The areas where doctest is behind are planned for improvement in the future. There are many other smaller differences – it would be impractical to cover them all.
+The areas where doctest is behind are planned for improvement in the future. There are many other smaller differences - it would be impractical to cover them all.
 
 ### How to get the best compile-time performance with the framework?