The current explanation of how to use is difficult to follow. Instead of running the script with parameters, it would be better to use a configuration file to specify these parameters (including corpus/output path). You can briefly explain each parameter in this section, including their possible values. This is similar to how parameters are stored in output_config.json. Once everything is consolidated into the configuration file, you can remove output_config.json. This way, by examining config.json, users can easily see the parameter values applied to produce the output.
The current explanation of how to use is difficult to follow. Instead of running the script with parameters, it would be better to use a configuration file to specify these parameters (including corpus/output path). You can briefly explain each parameter in this section, including their possible values. This is similar to how parameters are stored in output_config.json. Once everything is consolidated into the configuration file, you can remove output_config.json. This way, by examining config.json, users can easily see the parameter values applied to produce the output.