DOC-532: update Enterprise overview, editions and quickstarts (#1784)

Following Enterprise Content plan to clarify and improve Enterprise
positioning, benefits and onboarding:

### WIP list
- [x] Add Features & Benefits table to Enterprise Overview AKA Editions
- [x] Merge Get Started with Enterprise with Persist Map Entries
tutorial
- [ ] Refine and save tutorial template (separate PR)
- [x] Correct and improve other EE GS tutorials
- [x] Review and correct licensing / install info
- [x] Check and correct terminology
- [x] Apply Google Style Guide
- [x] Update screenshots
- [x] _Change license key to secret?_ Add tip and link to PO tutorial

### Docs Feedback
Closes [1833](#1833),
[1836](#1836)

Author: oliverhowell

docs/modules/ROOT/nav.adoc

@@ -2,34 +2,33 @@
 // About
 * xref:whats-new.adoc[What's new]
 * xref:what-is-hazelcast.adoc[What is Hazelcast Platform]
-* xref:getting-started:editions.adoc[Available versions]
+* xref:getting-started:editions.adoc[Hazelcast editions]
 // Getting started
 * Start a local cluster
 ** xref:getting-started:get-started-docker.adoc[Docker]
 ** xref:getting-started:get-started-cli.adoc[CLI]
 ** xref:getting-started:get-started-binary.adoc[Binary]
 ** xref:getting-started:get-started-java.adoc[Java embedded]
 // Enterprise
-* xref:getting-started:enterprise-overview.adoc[Get started with Enterprise Edition]
-** xref:getting-started:persistence.adoc[]
-** xref:getting-started:authenticate-clients.adoc[]
-** xref:getting-started:wan.adoc[]
-** xref:getting-started:blue-green.adoc[]
-// SQL
-* Get started with SQL
-** xref:sql:get-started-sql.adoc[]
-** xref:sql:learn-sql.adoc[]
-** xref:sql:get-started-sql-files.adoc[]
+* xref:getting-started:get-started-enterprise.adoc[Get started with Enterprise]
+** xref:getting-started:authenticate-client-tutorial.adoc[]
+** xref:getting-started:wan-replication-tutorial.adoc[Replicate map across WAN clusters]
+** xref:getting-started:deploy-blue-green-tutorial.adoc[]
 // Clients
-* xref:clients:hazelcast-clients.adoc[Get started with a Hazelcast Client]
+* xref:clients:hazelcast-clients.adoc[Get started with clients]
 ** xref:clients:java-client-getting-started.adoc[Get started with Java]
 ** xref:clients:csharp-client-getting-started.adoc[Get started with .NET]
 ** xref:clients:python-client-getting-started.adoc[Get started with Python]
 ** xref:clients:cpp-client-getting-started.adoc[Get started with {cpp}]
 ** xref:clients:go-client-getting-started.adoc[Get started with Go]
 ** xref:clients:nodejs-client-getting-started.adoc[Get started with Node.js]
+// SQL
+* Get started with SQL
+** xref:sql:get-started-sql.adoc[]
+** xref:sql:learn-sql.adoc[]
+** xref:sql:get-started-sql-files.adoc[]
 // Support
-* xref:getting-started:support.adoc[]
+* xref:getting-started:support.adoc[Get support]
 * xref:ask-ai.adoc[]
 
 .Install and upgrade
@@ -450,7 +449,7 @@
 * xref:cluster-performance:thread-per-core-tpc.adoc[]
 // Synchronizing data across clusters
 * Synchronizing data across clusters
-** xref:wan:wan.adoc[WAN Replication Overview]
+** xref:getting-started:wan-replication-tutorial.adoc[WAN Replication Overview]
 ** xref:wan:modes.adoc[]
 ** xref:wan:quick-start.adoc[]
 ** xref:wan:defining-wan-replication.adoc[]

docs/modules/ROOT/pages/ask-ai.adoc

@@ -1,5 +1,5 @@
 = Ask AI
-:description: Use our Ask AI feature to get instant answers to technical questions.
+:description: Use our Ask AI feature to get instant answers to technical questions and help troubleshoot problems.
 
 {description}
 

docs/modules/ROOT/pages/capacity-planning.adoc

@@ -37,7 +37,7 @@ or asynchronous xref:data-structures:backing-up-maps.adoc[backups]?
 required to accommodate the data, both existing and new. Usually an eviction mechanism keeps
 the map/cache size in check, but the eviction itself does not always clear the memory almost
 immediately. Therefore, the answers to this question gives a good insight.
-* Are you using multiple clusters (which may involve xref:wan:wan.adoc[WAN Replication])?
+* Are you using multiple clusters (which may involve xref:getting-started:wan-replication-tutorial.adoc[WAN Replication])?
 * What are the throughput and latency requirements?
 ** The answer should be about Hazelcast access, not the application throughput.
 For example, an application may plan for 10,000 user TPS but each user

docs/modules/ROOT/pages/index.adoc

@@ -75,7 +75,7 @@ Also, Hazelcast can be used as a cache for applications based on the Spring Fram
 shared data in real time.
 
 You can have multiple Hazelcast clusters at different locations in sync
-by replicating their state over WAN environments. See the xref:wan:wan.adoc[Synchronizing Data Across a WAN section].
+by replicating their state over WAN environments. See the xref:getting-started:wan-replication-tutorial.adoc[Synchronizing Data Across a WAN section].
 
 You can listen to the events happening in the cluster, on the data structures and clients so that
 you are notified when those events happen. See the xref:events:distributed-events.adoc[Distributed Events section].

docs/modules/ROOT/pages/what-is-hazelcast.adoc

@@ -75,7 +75,7 @@ Also, Hazelcast can be used as a cache for applications based on the Spring Fram
 shared data in real time.
 
 You can have multiple Hazelcast clusters at different locations in sync
-by replicating their state over WAN environments. See the xref:wan:wan.adoc[Synchronizing Data Across a WAN section].
+by replicating their state over WAN environments. See the xref:getting-started:wan-replication-tutorial.adoc[Synchronizing Data Across a WAN section].
 
 You can listen to the events happening in the cluster, on the data structures and clients so that
 you are notified when those events happen. See the xref:events:distributed-events.adoc[Distributed Events section].

docs/modules/architecture/pages/architecture.adoc

@@ -39,7 +39,7 @@ cooperatively diagnose the state and immediately take over the responsibility
 of the failed member. To determine if a member is unreachable or crashed, Hazelcast
 provides built-in xref:clusters:failure-detector-configuration.adoc[failure detectors].
 
-Hazelcast also provides replication over WAN for high availability. You can have deployments across multiple data centers using the xref:wan:wan.adoc[WAN replication] mechanism which offers protection against a data center or wider network failures.
+Hazelcast also provides replication over WAN for high availability. You can have deployments across multiple data centers using the xref:getting-started:wan-replication-tutorial.adoc[WAN replication] mechanism which offers protection against a data center or wider network failures.
 
 == AP/CP
 

docs/modules/clients/pages/cplusplus.adoc

@@ -11,7 +11,7 @@ TIP: To learn how to get started quickly with the Hazelcast {cpp} client, follow
 The Hazelcast native {cpp} client is an official library that allows {cpp} applications to connect to and interact with Hazelcast clusters. With the Hazelcast {cpp} client, developers can build high-performance, distributed applications in {cpp} that leverage Hazelcast's powerful in-memory computing platform.
 The key features and benefits include:
 
-* Distributed Data Structures: the client offers access to various distributed data structures such as Map, Queue, Reliable Topic, Set, List, MultiMap, RingBuffer, etc. 
+* Distributed Data Structures: the client offers access to various distributed data structures such as Map, Queue, Reliable Topic, Set, List, MultiMap, Ringbuffer, etc. 
 * Near Cache Support: the Near Cache feature allows frequently read data to be stored for faster read speeds compared to traditional caches.
 * Enterprise-Level security: the client provides SSL support for enhanced security requirements.
 * Distributed synchronization: the client offers distributed synchronization mechanisms through the CP Subsystem, including fenced_lock, counting_semaphore and latch.
@@ -55,7 +55,7 @@ git clone https://github.com/microsoft/vcpkg --branch 2025.02.14
 ``` 
 The above code snippet installs `hazelcast-cpp-client` with its `boost` and `openssl` dependencies.
 
-After installation, the library is available to use. For example, if you are using CMake for your builds, you can use the following cmake build command with the `CMAKE_TOOLCHAIN_FILE` cmake option to be the `vcpkg.cmake`.
+After installation, the library is available to use. For example, if you are using CMake for your builds, you can use the following CMake build command with the `CMAKE_TOOLCHAIN_FILE` CMake option to be the `vcpkg.cmake`.
 ```bat
 cmake -B [build directory] -S . -DCMAKE_TOOLCHAIN_FILE=[path to vcpkg]/scripts/buildsystems/vcpkg.cmake
 cmake --build [build directory]
@@ -129,7 +129,7 @@ cmake --build .
 sudo cmake --build . --target install
 ```
 
-You can speed up the build process with parallel threads like 'cmake --build . -j 4'
+You can speed up the build process with parallel threads like `cmake --build . -j 4`
 
 For information on how to use a different installation location, see xref:clients:cplusplus.adoc#custom-install-location[Custom install location].
 
@@ -181,7 +181,7 @@ For example, if you want to build the static library with SSL support, use the f
 cmake .. -DWITH_OPENSSL=ON -DBUILD_SHARED_LIBS=OFF
 ```
 
-NOTE: If you want to use the `hazelcast-cpp-client` library with the `-DWITH_OPENSSL=ON` option without `find_package()` you must define the `HZ_BUILD_WITH_SSL` symbolic constant before including any `hazelcast-cpp-client` header. This symbolic constant can be defined via compiler options or can be passed directly through the cmake command as `-DVARIABLE=VALUE` pairs.
+NOTE: If you want to use the `hazelcast-cpp-client` library with the `-DWITH_OPENSSL=ON` option without `find_package()` you must define the `HZ_BUILD_WITH_SSL` symbolic constant before including any `hazelcast-cpp-client` header. This symbolic constant can be defined via compiler options or can be passed directly through the `cmake` command as `-DVARIABLE=VALUE` pairs.
 
 For example:
 ```sh

docs/modules/data-structures/pages/vector-collections.adoc

@@ -23,12 +23,11 @@ If you use Docker, you can use the following example command:
 
 [source,bash,subs="attributes+"]
 ----
-docker run -p 5701:5701 -e HZ_LICENSEKEY=<your license key> \
+docker run -p 5701:5701 -e HZ_LICENSEKEY=<YOUR_LICENSE_KEY> \
      -e "JAVA_OPTS=--add-modules jdk.incubator.vector" \
      hazelcast/hazelcast-enterprise:{ee-version}-slim
-----
 
-Replace the `<your license key>` placeholder with your Hazelcast {enterprise-product-name} license key.
+Replace the `<YOUR_LICENSE_KEY>` placeholder with your Hazelcast {enterprise-product-name} license key.
 
 == Configuration
 Collection configuration can be set dynamically during vector collection creation or statically during cluster configuration. Unlike other data structures, the configuration must be set up before the collection can be used.

docs/modules/deploy/pages/deploying-on-azure.adoc

@@ -172,7 +172,7 @@ clientConfig.getNetworkConfig().getAzureConfig()
 
 == Configuration for WAN Replication Target Cluster Discovery
 
-Hazelcast allows you to configure xref:wan:wan.adoc[WAN replication] to work with the clusters in Azure and determine the endpoint IP addresses at runtime. If one Hazelcast cluster is running outside Azure and another is running inside Azure, then you should configure your WAN batch publisher as below:
+Hazelcast allows you to configure xref:getting-started:wan-replication-tutorial.adoc[WAN replication] to work with the clusters in Azure and determine the endpoint IP addresses at runtime. If one Hazelcast cluster is running outside Azure and another is running inside Azure, then you should configure your WAN batch publisher as below:
 
 NOTE: You will need to setup link:https://learn.microsoft.com/entra/identity-platform/howto-create-service-principal-portal/[Microsoft Entra Service Principal credentials] for your Azure Subscription to be able to use these properties.
 

docs/modules/deploy/pages/deploying-with-docker.adoc

@@ -1,21 +1,21 @@
-= Deploying on Docker
+= Deploy on Docker
 :description: In this deployment guide, you will learn how to form a cluster from Hazelcast member containers running on more than one Docker host in the same local area network (LAN).
 :page-aliases: installing-using-docker.adoc
 
 {description}
 
-== Starting a Cluster
+== Start a cluster
 
-The default network mode in Docker is bridge. In this mode, all containers run in a single network that is not accessible outside of the Docker host. If you run member Docker containers on different hosts, you must allow them to discover and connect to each other using one of the following methods:
+The default network mode in Docker is bridge. In this mode, all containers run in a single network that's not accessible outside of the Docker host. If you run member Docker containers on different hosts, you must allow them to discover and connect to each other using one of the following methods:
 
 - Host network mode (Linux only)
 - Port mapping
 
 include::deploy:partial$docker-ip-warning.adoc[]
 
-=== Host Network Mode
+=== Use host network mode
 
-To allow members and clients on different hosts to discover each other with multicast, you can use the `host` network mode. This mode allows members to share the host’s network stack from their Docker containers.
+To allow members and clients on different hosts to discover each other with multicast, you can use the `host` network mode. This mode allows members to share the host's network stack from their Docker containers.
 
 Members will discover and connect to each other automatically only if your local network supports multicast. If your network does not support multicast, members will not form a cluster. In this case, you can try <<port-mapping, port mapping>>.
 
@@ -44,7 +44,7 @@ docker run --rm --network host --name member2 hazelcast/hazelcast-enterprise:{ee
 
 In this mode, each member is available on the internal (private) IP address of the Docker host.
 
-=== Port Mapping
+=== Port mapping
 
 To allow members and clients on different hosts to discover each other over TCP/IP, you can map ports from the Docker host (the device that's running Docker) and tell Hazelcast to listen to your internal IP address.
 
@@ -134,8 +134,7 @@ for more information.
 
 You can configure various aspects of your cluster and environment with Docker.
 
-We recommend that you use the default
-configuration file as a starting point.
+We recommend that you use the default configuration file as a starting point.
 
 === Memory
 
@@ -162,7 +161,7 @@ docker run --memory 2g -e JAVA_OPTS="-XX:MaxRAMPercentage=85.0" --rm hazelcast/h
 
 Make sure to leave enough free RAM for metaspace and other overheads.
 
-=== Custom Hazelcast Configuration File
+=== Custom Hazelcast configuration file
 
 You can configure Hazelcast with your own YAML or XML file
 by replacing the default ones in the container at
@@ -185,7 +184,7 @@ docker run \
 -p:5701:5701 hazelcast/hazelcast:{os-version}
 ----
 
-=== Extend Hazelcast's CLASSPATH with Custom JARS and Files
+=== Extend Hazelcast's classpath with Custom JARS and Files
 
 If you have to add more classes or files to Hazelcast's classpath, one way to
 do it is to put them in a directory such as `ext`, mount it to the
@@ -210,7 +209,7 @@ docker run \
 
 ----
 
-=== Changing Logging Level
+=== Change logging level
 
 You can set the logging level using the `LOGGING_LEVEL` environment
 variable:
@@ -238,7 +237,7 @@ Edit the file and mount it when starting Hazelcast:
 docker run -v /path/to/log4j2.properties:/opt/hazelcast/log4j2.properties hazelcast/hazelcast:{os-version}
 ----
 
-== Building a Custom Image from the Slim Image
+== Build a custom image from the slim Docker image
 
 Hazelcast offers a xref:getting-started:editions.adoc#full-slim[slim] Docker image that
 contains only the core Hazelcast engine. When image size is a concern, you can use it