Incorporate review feedback

Co-authored-by: Johnathan Gilday <[email protected]>

cli.md

@@ -77,7 +77,7 @@ The `executable` could involve multiple command line tokens (e.g., `npm run` or
 
 The `--path-include` and `--path-exclude` patterns are interpreted as relative to the given `<project directory>`. In practice this means that the patterns should be joined with the `<project directory>` when used internally and also when passed to external tools.
 
-In general, codemods that remediate the results of other tools should respect the file paths specified in findings by those tools. Explicit configuration provided by the user via `--path-include` and `--path-exclude` can be used to filter the applicable results. Remediation codemods should generally not impose their own defaults. The philosophy here is that an external tool has its own defaults and/or configuration, and this should be respected by codemodder.
+In general, codemods that remediate the results of other tools respect the file paths specified in findings by those tools. Explicit configuration provided by the user via `--path-include` and `--path-exclude` takes precedence over any defaults a codemod may define. Remediation codemods must not impose their own defaults: the philosophy here is that an external tool has its own defaults and/or configuration, and this should be respected by codemodder.
 
 Codemods that perform their own detection (i.e. "find-and-fix" codemods) may wish to define reasonable defaults for the paths to be included and excluded for analysis. It is recommended that such codemods should include only relevant source files and ignore test directories and build artifacts by default. For example, such codemods will generally want to exclude `**/tests/**` by default. This will be interpreted relative to the given `<project directory>`, which means that the effective pattern will be `<project directory>/**/tests/**`.