README

README.md

@@ -508,8 +508,8 @@ Combine with `--format group` for a truly _luxe_ experience:
 
 ## Config File
 
-Use a `.ncurc.{json,yml,js}` file to specify configuration information.
-You can specify file name and path using `--configFileName` and `--configFilePath`
+Use a `.ncurc.{json,yml,js,cjs}` file to specify configuration information.
+You can specify the file name and path using `--configFileName` and `--configFilePath`
 command line options.
 
 For example, `.ncurc.json`:
@@ -545,11 +545,6 @@ console.log(upgraded) // { "mypackage": "^2.0.0", ... }
 
 Contributions are happily accepted. I respond to all PR's and can offer guidance on where to make changes. For contributing tips see [CONTRIBUTING.md](https://github.com/raineorshine/npm-check-updates/blob/main/.github/CONTRIBUTING.md).
 
-## Known Issues
-
-- If `ncu` prints output that does not seem related to this package, it may be conflicting with another executable such as `ncu-weather-cli` or Nvidia CUDA. Try using the long name instead: `npm-check-updates`.
-- Windows: If npm-check-updates hangs, try setting the package file explicitly: `ncu --packageFile package.json`. You can run `ncu --loglevel verbose` to confirm that it was incorrectly waiting for stdin. See [#136](https://github.com/raineorshine/npm-check-updates/issues/136#issuecomment-155721102).
-
 ## Problems?
 
 [File an issue](https://github.com/raineorshine/npm-check-updates/issues). Please [search existing issues](https://github.com/raineorshine/npm-check-updates/issues?utf8=%E2%9C%93&q=is%3Aissue) first.