doc: also explain how to now add the Java plugin to a gradle build

src/docs/content/release-notes/oss/upgrading/3.10-to-3.11/index.md

@@ -163,5 +163,5 @@ This new version is a major overhaul and introduces several breaking changes.
 
 * It has the same behavior as the new version of the Maven plugin: interactive by default, unless when running on a CI.
 * It now uses a `--simulation=<FullyQualifiedClassName>` option to force the desired simulation instead of the non-standard `gatlingRun-<FullyQualifiedClassName>` pattern.
-* It no longer applies the `scala` plugin automatically. It's the responsibility of the user to apply it if needed. See the [demo project](https://github.com/gatling/gatling-gradle-plugin-demo-scala/blob/main/build.gradle#L2) for how to apply the Scala plugin in your gradle build.
+* It no longer applies the `java` and `scala` plugins automatically. It's the responsibility of the user to apply the desired plugin for their language of choice. See the relevant demo project for [Java](https://github.com/gatling/gatling-gradle-plugin-demo-java/blob/main/build.gradle#L2) and [Scala](https://github.com/gatling/gatling-gradle-plugin-demo-scala/blob/main/build.gradle#L2) for how to apply the suited plugin in your gradle build.
 * It no longer generate a logback conf when there's none defined. `logLevel` and `logHttp` have been dropped and must be removed from your `build.gradle`. Instead, you must add a logback conf file as demoed in our [demo projects](https://github.com/gatling/gatling-gradle-plugin-demo-java/tree/main/src/gatling/resources).