Update documentation on import public limitations.

PiperOrigin-RevId: 878981321

Author: protobuf-github-bot

content/programming-guides/editions.md

@@ -887,8 +887,7 @@ a single change, you can put a placeholder `.proto` file in the old location to
 forward all the imports to the new location using the `import public` notion.
 
 **Note that the public import functionality is not available in Java, Kotlin,
-TypeScript, JavaScript, GCL, as well as C++ targets that use protobuf static
-reflection.**
+TypeScript, JavaScript, or GCL.**
 
 `import public` dependencies can be transitively relied upon by any code
 importing the proto containing the `import public` statement. For example:

content/programming-guides/proto2.md

@@ -921,8 +921,7 @@ a single change, you can put a placeholder `.proto` file in the old location to
 forward all the imports to the new location using the `import public` notion.
 
 **Note that the public import functionality is not available in Java, Kotlin,
-TypeScript, JavaScript, GCL, as well as C++ targets that use protobuf static
-reflection.**
+TypeScript, JavaScript or GCL.**
 
 `import public` dependencies can be transitively relied upon by any code
 importing the proto containing the `import public` statement. For example:

content/programming-guides/proto3.md

@@ -943,8 +943,7 @@ these cases, generated names remain stable, avoiding the need to update
 references in your code. While technically functional when moving a subset of a
 .proto file without `java_multiple_files = true`, doing so requires simultaneous
 updates to many references, thus might not significantly ease migration. The
-functionality is not available in Kotlin, TypeScript, JavaScript, GCL, or with
-C++ targets that use protobuf static reflection.
+functionality is not available in Kotlin, TypeScript, JavaScript, or GCL.
 
 `import public` dependencies can be transitively relied upon by any code
 importing the proto containing the `import public` statement. For example: