Emphasized type checker warning is due to static analyzer's limitation

Author: adamlui

find-project-root/docs/README.md

@@ -38,7 +38,7 @@ root = find_project_root()
 print(root) # e.g. /home/user/projects/my-project
 ```
 
-_Note: Most type checkers will falsely warn_ `find_project_root` _is not a callable module because they cannot analyze runtime behavior (where the module is replaced w/ a function for cleaner, direct access). You can safely suppress such warnings using_ `# type: ignore`.
+_Note: Most type checkers will falsely warn_ `find_project_root` _is not a callable module because they are incapable of analyzing runtime behavior (where the module is replaced w/ a function for cleaner, direct access). You can safely suppress such warnings using_ `# type: ignore`.
 
 ### Available options:
 

project-markers/docs/README.md

@@ -30,7 +30,7 @@ print(project_markers)
 # => ['.ansible-lint', '.bazelrc', '.browserslistrc', '.buckconfig', ...]
 ```
 
-_Note: Most type checkers will falsely warn_ `project_markers` _is not iterable because they cannot analyze runtime behavior (where the module is replaced w/ a list for cleaner, direct access). You can safely suppress such warnings using_ `# type: ignore`.
+_Note: Most type checkers will falsely warn_ `project_markers` _is not iterable because they are incapable of analyzing runtime behavior (where the module is replaced w/ a list for cleaner, direct access). You can safely suppress such warnings using_ `# type: ignore`.
 
 The list includes hundreds of markers from many tools and ecosystems, including: