docs: improve wording of file-extension-in-import docs (#110)

* docs: improve wording of file-extension-in-import docs

mysticatea#325

* Update docs/rules/file-extension-in-import.md

* docs: Remove multiple blank lines

---------

Co-authored-by: Sebastian Good <2230835+scagood@users.noreply.github.com>

docs/rules/file-extension-in-import.md

@@ -11,9 +11,7 @@ import foo from "./path/to/a/file" // maybe it's resolved to 'file.js' or 'file.
 export * from "./path/to/a/file"
 ```
 
-However, [--experimental-modules](https://medium.com/@nodejs/announcing-a-new-experimental-modules-1be8d2d6c2ff) has declared to drop the file extension omition.
-
-Also, we can import a variety kind of files with bundlers such as Webpack. In the situation, probably explicit file extensions help us to understand code.
+We can also import a variety of file types with bundlers such as Webpack. In this situation, explicit file extensions can help to identify the type of file being imported.
 
 ## 📖 Rule Details