Skip to content

Commit bfc61fa

Browse files
ivanpanchtzlaine
authored andcommitted
Update config.hpp
1 parent 68c306b commit bfc61fa

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

include/boost/parser/config.hpp

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,19 @@
1616

1717
/** Boost.Parser uses assertions (`BOOST_ASSERT()`) in several places to
1818
indicate that your use of the library has an error in it. All of those
19-
places could heve instead been ill-formed code, caught at compile time.
19+
places could have instead been ill-formed code, caught at compile time.
2020
It is far quicker and easier to determine exactly where in your code such
2121
an error is located if this is a runtime failure; you can just look at the
22-
stack in your favorite debugger. However, if you want to make thes kinds
22+
stack in your favorite debugger. However, if you want to make these kinds
2323
of errors always ill-formed code, define this macro. */
2424
# define BOOST_PARSER_NO_RUNTIME_ASSERTIONS
2525

2626
/** Asserts that the given condition is true. If
2727
`BOOST_PARSER_NO_RUNTIME_ASSERTIONS` macro is defined by the user,
28-
`BOOST_PARSER_ASSERT` expends to a compile-time `static_assert()`.
28+
`BOOST_PARSER_ASSERT` expands to a compile-time `static_assert()`.
2929
Otherwise, it expands to a run-time `BOOST_ASSERT()`. Note that defining
3030
`BOOST_DISABLE_ASSERTS` disables the use of C `assert`, even when
31-
`BOOST_ASSERT` is unavailble. */
31+
`BOOST_ASSERT` is unavailable. */
3232
# define BOOST_PARSER_ASSERT(condition)
3333

3434
/** Boost.Parser will automatically use concepts to constrain templates when

0 commit comments

Comments
 (0)