docs: standardizing files and functions format

Author: Heitor Danilo

README.md

@@ -67,10 +67,10 @@ However, if a test fails, the program will halt execution at the point of failur
 You can find the definitions for all tests in the files that end with the ***_test.h*** suffix, while the ***_test.c*** files contain the implementations of these tests. The ***./src/main_test.c*** file serves as the test runner, executing all test implementations.
 
 Tests are named following the pattern "`test_should_pass_if_\[condition]`". For example:
-1. `test_should_pass_if`_var_statement_to_string_is_equal_to_expected (***src/ast/ast_test.h***)
-2. `test_should_pass_if`_bool_assignments_are_equal_to_expected (******src/token/token_test.h******)**
+1. `test_should_pass_if_var_statement_to_string_is_equal_to_expected` (***src/ast/ast_test.h***)
+2. `test_should_pass_if_bool_assignments_are_equal_to_expected` (******src/token/token_test.h******)**
 
-Each `_test.c` file contains local helper functions that assist in performing specific tasks within the file, but are not accessible for other tests. For this reason, I would categorize this as a library, rather than a framework. For instance, in ***src/ast/ast_test.c***, you'll find the `create_program` function:
+Each ***_test.c*** file contains local helper functions that assist in performing specific tasks within the file, but are not accessible for other tests. For this reason, I would categorize this as a library, rather than a framework. For instance, in ***src/ast/ast_test.c***, you'll find the `create_program` function:
 
 ```C
 struct Program* create_program(char* input) {