@@ -299,7 +299,7 @@ TEST_CASE("escaped_star_query", "[Query]") {
299299 * @ingroup unit_tests_query
300300 * @brief Creates and tests a query with an escaped '*' character.
301301 *
302- * NOTE: This has a static-text case as strings "1", "2' , and "3" in isolation aren't surrounded by
302+ * NOTE: This has a static-text case as strings "1", "2" , and "3" in isolation aren't surrounded by
303303 * delimiters. These tokens then build up the interpretation "123". Although additional
304304 * interpretations don't impact correctness, they may impact performance. We can optimize these out,
305305 * but it'll make the code messy. Instead, we should eventually remove the explicit tracking of
@@ -328,7 +328,7 @@ TEST_CASE("int_query", "[Query]") {
328328 *
329329 * This test ensures that each non-wildcard token is assigned to the highest priority variable.
330330 *
331- * NOTE: Similar to the above `int_query` test there are unneeded intepretations due to aggresively
331+ * NOTE: Similar to the above `int_query` test there are unneeded interpretations due to aggresively
332332 * generating static-text tokens.
333333 */
334334TEST_CASE (" non_wildcard_multi_variable_query" , " [Query]" ) {
@@ -376,7 +376,7 @@ TEST_CASE("non_wildcard_multi_variable_query", "[Query]") {
376376 *
377377 * This test ensures that each greedy wildcard token is identified as all correct token types.
378378 *
379- * NOTE: Similar to the above `int_query` test there are unneeded intepretations due to aggresively
379+ * NOTE: Similar to the above `int_query` test there are unneeded interpretations due to aggresively
380380 * generating static-text tokens. This same issue causes interpretations with redundant wildcards.
381381 */
382382TEST_CASE (" wildcard_multi_variable_query" , " [Query]" ) {
0 commit comments