Merge pull request #6887 from bndtools/docs/gen-2025-10-26-161946

docs: update generated docs

Author: chrisrueger

docs/_instructions/noimportjava.md

@@ -17,7 +17,7 @@ note: AUTO-GENERATED FILE - DO NOT EDIT. You can add manual content via same fil
 
 Prior to OSGi Core R7, it was invalid for the Import-Package header to include `java.*` packages. So Bnd would never include them in the generated Import-Package header. In OSGi Core R7, or later (e.g. [OSGi Core R8](https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#framework.module-execution.environment)), it is now permitted to include `java.*` packages in the Import-Package header. This allows the OSGi framework validate the execution environment can supply all the java packages required by a bundle. This can avoid a `NoClassDefFoundError` during execution of the bundle due to a missing `java.*` package required by the bundle. 
 
-Bnd will now generate the Import-Package header including referenced `java.*` packages when either the bundle imports the `org.osgi.framework` package from OSGi 7, or later, or when the bundle includes class files targeting Java 11, or later.
+Bnd will now generate the Import-Package header including referenced `java.*` packages when either the bundle imports the `org.osgi.framework` package from OSGi Core R7, or later, or when the bundle includes class files targeting Java 11, or later.
 
 The `-noimportjava` instruction can be used to tell Bnd not to include referenced `java.*` packages in the generated Import-Package header.