DOCS: PR replaces previous Nima removal PR

docs/about/doc_overview.adoc

@@ -107,8 +107,6 @@ xref:{rootdir}/mp/guides/mp-tutorial.adoc[Helidon SE Tutorial]
 --
 Ready for more hands-on learning? Explore the features of Helidon with these quick step-by-step guides.
 
-xref:{rootdir}/nima/guides/overview.adoc[Níma Guides]
-
 xref:{rootdir}/se/guides/overview.adoc[SE Guides]
 
 xref:{rootdir}/mp/guides/overview.adoc[MP Guides]
@@ -125,15 +123,15 @@ xref:{rootdir}/mp/guides/overview.adoc[MP Guides]
 
 //Training and Certification
 [CARD]
-.Helidon MP
+.Training and Certification
 [icon=swap_horiz]
 --
 
 --
 
-//Helidon Níma
+//Get Involved
 [CARD]
-.Helidon Níma
+.Get Involved
 [icon=swap_horiz]
 --
 

docs/about/doc_sitemap.adoc

@@ -18,7 +18,7 @@
 
 = Helidon Documentation Overview
 :description: Helidon Documentation Sitemap
-:keywords: helidon, java, microservices, microprofile, documentation, nima
+:keywords: helidon, java, microservices, microprofile, documentation
 :rootdir: {docdir}/..
 
 == Using This Site
@@ -31,7 +31,6 @@ New to Helidon? Start with the xref:{rootdir}/about/introduction.adoc[Helidon Do
 
 Once you've settled on your preferred programming framework, visit the Helidon flavor sections of this site for more information. 
 
-* xref:{rootdir}/nima/introduction.adoc[Helidon Nima]
 * xref:{rootdir}/se/introduction.adoc[Helidon SE]
 * xref:{rootdir}/mp/introduction.adoc[Helidon MP]
 

docs/about/generating_project.adoc

@@ -29,8 +29,6 @@ https://helidon.io/starter[Helidon Project Starter] allows you to choose from a
 
 === Helidon MP
 
-=== Nima
-
 
 == Choose an Application Type
 Helidon provides the following set of archetypes to bootstrap your application development journey.

docs/about/intro.adoc

@@ -24,3 +24,16 @@
 
 == What's New in This Release
 
+* We have removed the Netty-based Helidon __reactive__ WebServer and WebClient and replaced them with implementations based on virtual threads that have a _blocking_ style API.
+
+NOTE: Virtual threads are lightweight threads that dramatically reduce the effort of writing, maintaining, and observing high-throughput concurrent applications. Learn more about using virtual threads https://openjdk.org/jeps/444[here]. 
+
+
+* Helidon 4 now supports MicroProfile 5.0-based applications working on virtual threads. This is the first MicroProfile framework that supports virtual threads and uses JDK features on the new Helidon WebServer.
+
+
+* item
+
+* Helidon 4 requires Java 20.
+
+

docs/includes/openapi/openapi-generator.adoc

@@ -51,13 +51,13 @@ Each of these generators supports two _libraries_:
 * `mp` - for Helidon MP code generation
 * `se` - for Helidon SE code generation
 
-Use the Helidon _client_ generator and its `{flavor-lc}` library to create a
-ifdef::mp-flavor[]
-xref:{helidon-client-xref}[Helidon MicroProfile REST client].
-endif::mp-flavor[]
-ifdef::se-flavor[]
-Helidon SE client based on xref:{helidon-client-xref}[Helidon WebClients].
-endif::se-flavor[]
+//Use the Helidon _client_ generator and its `{flavor-lc}` library to create a
+//ifdef::mp-flavor[]
+//xref:{helidon-client-xref}[Helidon MicroProfile REST client].
+//endif::mp-flavor[]
+//ifdef::se-flavor[]
+//Helidon SE client based on xref:{helidon-client-xref}[Helidon WebClients].
+//endif::se-flavor[]
 The resulting client library works with any server that implements the API declared in the OpenAPI document you specified when you ran the generator.
 The client library provides an abstraction similar to remote procedure calls (RPC).
 To access a remote service that implements the endpoints declared in the OpenAPI document, your code uses the generated client library first to establish a connection to the remote service and then to call remote service endpoints by invoking local methods passing POJO business objects or Java types as arguments.
@@ -423,7 +423,7 @@ The next example runs the Helidon client generator using the same input file.
 
 :example-project-type: client
 .Creating or updating a client project using the OpenAPI generator CLI
-include::openapi-generator.adoc[tag=example-cli-usage]
+//include::openapi-generator.adoc[tag=example-cli-usage]
 
 The key differences between the commands are:
 
@@ -533,8 +533,11 @@ The generated client code represents a true library. Typically, you do not need
 // end::using-generated-code-client-intro[]
 
 // tag::common-references[]
+
 == References
-* link:{openapi-generator-tool-site-url}[OpenAPI Generator Official Website]
-* link:{openapi-generator-tool-base-url}[OpenAPI Generator GitHub Repository]
-* link:{openapi-spec-url}[OpenAPI specification]
+//* link:{openapi-generator-tool-site-url}[OpenAPI Generator Official Website]
+
+//* link:{openapi-generator-tool-base-url}[OpenAPI Generator GitHub Repository]
+
+//* link:{openapi-spec-url}[OpenAPI specification]
 // end::common-references[]