fixing typo

docs/codebase_structure.md

@@ -7,7 +7,7 @@ The HarmBench code is structured around five key elements:
 5. The `data` folder
 
 ## 1: Evaluation pipeline scripts
-The evaluation pipeline consists of four scripts: `generate_test_cases.py`, `merge_test_cases.py`, `generate_completions.py`, `evaluate_completions.py`. We describe how to use these below in the Quick Start section. At a high level, the first two scripts output a `test_cases.json` dictionary for a specific **experiment**. This dictionary contains a list of test cases for each behavior. The second two scripts run the test cases on a **target model** to compute attack success rate (ASR).
+The evaluation pipeline consists of four scripts: `generate_test_cases.py`, `merge_test_cases.py`, `generate_completions.py`, `evaluate_completions.py`. We describe how to use these in the Quick Start section. At a high level, the first two scripts output a `test_cases.json` dictionary for a specific **experiment**. This dictionary contains a list of test cases for each behavior. The second two scripts run the test cases on a **target model** to compute attack success rate (ASR).
 
 ## 2: Experiments and target models
 Each `test_cases.json` file generated by a red teaming method corresponds to a single **experiment**. Each red teaming method can run different experiments, corresponding to test cases optimized for different target models, or more generally test cases generated with different hyperparameters. By convention we save test cases in `{top_level_results_dir}/{method_name}/{experiment_name}/test_cases/test_cases.json`, so some example save locations could be