chore: clarify tsconfig resolution behavior in doc comments (#873)

Tweaked the comments to clarify the behavior a bit.

Author: sapphi-red

src/lib.rs

@@ -175,8 +175,7 @@ impl<Fs: FileSystem> ResolverGeneric<Fs> {
     /// For CommonJS modules, it is the `__dirname` variable that contains the absolute path to the folder containing current module.
     /// For ECMAScript modules, it is the value of `import.meta.url`.
     ///
-    /// NOTE: [TsconfigDiscovery::Auto] does not work for this API, use
-    /// `ResolverGeneric::resolve_file` instead.
+    /// NOTE: [TsconfigDiscovery::Auto] does not work for this API, use [ResolverGeneric::resolve_file] instead.
     ///
     /// # Errors
     ///
@@ -197,7 +196,7 @@ impl<Fs: FileSystem> ResolverGeneric<Fs> {
 
     /// Resolve `specifier` for an absolute path to a file.
     ///
-    /// NOTE: [TsconfigDiscovery::Auto] only work for this API, use `ResolverGeneric::resolve_file` instead.
+    /// NOTE: [TsconfigDiscovery::Auto] only work for this API.
     ///
     /// # Errors
     ///

src/tsconfig_resolver.rs

@@ -37,6 +37,8 @@ impl TsconfigResolveContext {
 impl<Fs: FileSystem> ResolverGeneric<Fs> {
     /// Finds the `tsconfig` to which this `path` belongs.
     ///
+    /// If the `path` is inside `node_modules`, this function always returns `None`.
+    ///
     /// Algorithm:
     ///
     /// 1. Search for `tsconfig.json` in ancestor directories.