fix: make no-jest-import error message more accurate

docs/rules/no-jest-import.md

@@ -2,8 +2,7 @@
 
 The `jest` object is automatically in scope within every test file. The methods
 in the `jest` object help create mocks and let you control Jest's overall
-behavior. It is therefore completely unnecessary to import in `jest`, as Jest
-doesn't export anything in the first place.
+behavior. It is therefore usually unnecessary to import in `jest`.
 
 ### Rule details
 
@@ -12,8 +11,13 @@ This rule reports on any importing of Jest.
 To name a few: `var jest = require('jest');` `const jest = require('jest');`
 `import jest from 'jest';` `import {jest as test} from 'jest';`
 
-There is no correct usage of this code, other than to not import `jest` in the
-first place.
+Examples of correct code include running Jest programatically in non-CLI
+environments (note that this is [not officially supported](https://github.com/facebook/jest/issues/5048)):
+
+```js
+const jest = require('jest')
+jest.runCLI(...)
+```
 
 ## Further Reading
 

src/rules/no-jest-import.ts

@@ -11,7 +11,7 @@ export default createRule({
       recommended: 'error',
     },
     messages: {
-      unexpectedImport: `Jest is automatically in scope. Do not import "jest", as Jest doesn't export anything.`,
+      unexpectedImport: `Do not import "jest". Jest is automatically in scope within every test file.`,
     },
     schema: [],
   },