diff --git a/plugin-gradle/README.md b/plugin-gradle/README.md
index 878885f645..b44d79ef3d 100644
--- a/plugin-gradle/README.md
+++ b/plugin-gradle/README.md
@@ -624,8 +624,8 @@ For details, see the [npm detection](#npm-detection) and [`.npmrc` detection](#n
 The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
 hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.
 
-The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. It differs in supported
-styleguides and the requirement for a tsconfigFile.
+The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. In typescript, a
+reference to a `tsconfig.json` is required.
 
 ```gradle
 spotless {
@@ -689,8 +689,8 @@ spotless {
 The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
 hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.
 
-The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. It differs in supported
-styleguides and no requirement for a tsconfig (of course).
+The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. In javascript, *no*
+`tsconfig.json` is supported.
 
 ```gradle
 
diff --git a/plugin-maven/README.md b/plugin-maven/README.md
index e74e1b27cf..3ec338bf10 100644
--- a/plugin-maven/README.md
+++ b/plugin-maven/README.md
@@ -724,8 +724,8 @@ For details, see the [npm detection](#npm-detection) and [`.npmrc` detection](#n
 The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
 hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.
 
-The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. It differs in supported
-styleguides and the requirement for a tsconfigFile.
+The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. In typescript, a
+reference to a `tsconfig.json` is required.
 
 ```xml
 <eslint>
@@ -803,8 +803,8 @@ For details, see the [npm detection](#npm-detection) and [`.npmrc` detection](#n
 The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
 hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.
 
-The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. It differs in supported
-styleguides and no requirement for a tsconfig (of course).
+The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. In javascript, *no*
+`tsconfig.json` is supported.
 
 ```xml
 <eslint>