Fix production build errors v/5.2 (#1271)

Fixes ``` 6:39:08 PM: [15:39:08.721] ERROR (asciidoctor): dropping cells from incomplete row detected end of table 6:39:08 PM: file: docs/modules/configuration/pages/configuring-programmatically.adoc:62 6:39:08 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:10 PM: [15:39:10.721] WARN (asciidoctor): no callout found for <2> 6:39:10 PM: file: docs/modules/getting-started/pages/blue-green.adoc:60 6:39:10 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:10 PM: [15:39:10.724] WARN (asciidoctor): no callout found for <2> 6:39:10 PM: file: docs/modules/getting-started/pages/blue-green.adoc:90 6:39:10 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:11 PM: [15:39:11.062] WARN (asciidoctor): no callout found for <5> 6:39:11 PM: file: docs/modules/getting-started/pages/persistence.adoc:56 6:39:11 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:11 PM: [15:39:11.121] WARN (asciidoctor): no callout found for <2> 6:39:11 PM: file: docs/modules/getting-started/pages/wan.adoc:52 6:39:11 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.254] WARN (asciidoctor): skipping reference to missing attribute: version 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.256] WARN (asciidoctor): skipping reference to missing attribute: default_hazelcast_yaml 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.263] WARN (asciidoctor): skipping reference to missing attribute: version 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.264] WARN (asciidoctor): skipping reference to missing attribute: default_hazelcast_client_yaml 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.533] WARN (asciidoctor): skipping reference to missing attribute: version 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-enterprise-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.534] WARN (asciidoctor): skipping reference to missing attribute: default_hazelcast_yaml 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-enterprise-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.542] WARN (asciidoctor): skipping reference to missing attribute: version 6:39:12 PM: file: docs/modules/kubernetes/pages/helm-hazelcast-enterprise-chart.adoc 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:12 PM: [15:39:12.568] ERROR (asciidoctor): dropping cells from incomplete row detected end of table 6:39:12 PM: file: docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc:25 6:39:12 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:13 PM: [15:39:13.132] ERROR (asciidoctor): target of xref not found: mapstore:configuring-a-generic-maploader.adoc 6:39:13 PM: file: docs/modules/mapstore/pages/configuration-guide.adoc 6:39:13 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:13 PM: [15:39:13.338] WARN (asciidoctor): unterminated listing block 6:39:13 PM: file: docs/modules/migrate/pages/upgrading-from-imdg-3.adoc:295 6:39:13 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:13 PM: [15:39:13.395] WARN (asciidoctor): unterminated listing block 6:39:13 PM: file: docs/modules/migrate/pages/upgrading-from-imdg-3.adoc:1020 6:39:13 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:13 PM: [15:39:13.397] WARN (asciidoctor): unterminated listing block 6:39:13 PM: file: docs/modules/migrate/pages/upgrading-from-imdg-3.adoc:1038 6:39:13 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) 6:39:13 PM: [15:39:13.397] ERROR (asciidoctor): dropping cells from incomplete row detected end of table 6:39:13 PM: file: docs/modules/migrate/pages/upgrading-from-imdg-3.adoc:1038 6:39:13 PM: source: https://github.com/hazelcast/hz-docs (branch: v/5.2 | start path: docs) ``` https://app.netlify.com/sites/nifty-wozniak-71a44b/deploys/66d72c95e732700008b85034#L200
hazelcast · Sep 4, 2024 · 0bc7809 · 0bc7809
1 parent 1f11693
commit 0bc7809
Show file tree

Hide file tree

Showing 9 changed files with 200 additions and 190 deletions.
diff --git a/docs/modules/configuration/pages/configuring-programmatically.adoc b/docs/modules/configuration/pages/configuring-programmatically.adoc
@@ -58,7 +58,8 @@ Hazelcast configuration also by using its default lookup mechanism.
 |link:https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/config/Config.html#loadFromStream-java.io.InputStream-java.util.Properties-[`Config.loadFromStream()`]
 |Creates `Config` from the provided XML or YAML stream content.
 
-|link:https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/config/XmlConfigBuilder.html[]
+|link:https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/config/XmlConfigBuilder.html[`Class XmlConfigBuilder`]
+|A XML `ConfigBuilder` implementation.
 
 |===
 
@@ -144,4 +145,4 @@ HazelcastInstance hz = Hazelcast.newHazelcastInstance(config);
 
 You can use xref:dynamic-config.adoc[dynamic configuration] to add configuration for some supported features at runtime.
 
-TIP: If you want to persist dynamic configuration changes, you need to use a <<config-file,configuration file method>> that sets the `configurationFile` field of the `Config` object such as  `Config.setConfigurationFile()` or `Config.loadFromFile()`.
+TIP: If you want to persist dynamic configuration changes, you need to use a <<config-file,configuration file method>> that sets the `configurationFile` field of the `Config` object such as  `Config.setConfigurationFile()` or `Config.loadFromFile()`.
diff --git a/docs/modules/getting-started/pages/blue-green.adoc b/docs/modules/getting-started/pages/blue-green.adoc
@@ -4,14 +4,14 @@
 
 {description}
 
-When clients are connected to a single cluster, that cluster becomes a single point of failure. If the cluster fails for any reason, the client cannot connect to it and the application may break. To make clients more robust, you can set up a blue-green cluster deployment, which provides a client failover mechanism that reroutes client connections to a different cluster without requiring a client network configuration update or client restart. 
+When clients are connected to a single cluster, that cluster becomes a single point of failure. If the cluster fails for any reason, the client cannot connect to it and the application may break. To make clients more robust, you can set up a blue-green cluster deployment, which provides a client failover mechanism that reroutes client connections to a different cluster without requiring a client network configuration update or client restart.
 
-You can use a blue-green deployment in the following scenarios: 
+You can use a blue-green deployment in the following scenarios:
 
 * To manually redirect client traffic to a secondary cluster while you perform maintenance or software updates.
 * To automatically redirect client traffic to a secondary cluster during a disaster recovery scenario.
 
-In both cases, you will need to manually deploy a xref:{page-latest-supported-mc}@management-center:clusters:client-filtering.adoc[client filter] to the secondary cluster to force clients to reconnect to the original, primary cluster when it is back online.  
+In both cases, you will need to manually deploy a xref:{page-latest-supported-mc}@management-center:clusters:client-filtering.adoc[client filter] to the secondary cluster to force clients to reconnect to the original, primary cluster when it is back online.
 
 This tutorial focuses on the disaster recovery scenario, where you will complete the following steps:
 
@@ -35,7 +35,7 @@ To complete this tutorial, you need the following:
 |xref:getting-started:enterprise-overview.adoc[]
 
 |Docker network with the name `hazelcast-network`
-|Use the `docker network create hazelcast-network` command 
+|Use the `docker network create hazelcast-network` command
 
 |===
 
@@ -51,9 +51,9 @@ Run the following command on the terminal:
 docker run \
     --network hazelcast-network \
     --rm \
-    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5701 \
+    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5701 \ <1>
     -e HZ_CLUSTERNAME=blue \
-    -e HZ_LICENSEKEY=<your license key> \ <1>
+    -e HZ_LICENSEKEY=<your license key> \ <2>
     -p 5701:5701 hazelcast/hazelcast-enterprise:{full-version}
 ----
 <1> Replace the `<host_ip>` placeholder with the IP address of your Docker host.
@@ -63,7 +63,7 @@ You should see your cluster name in the console along with the IP address of the
 
 [source,shell,subs="attributes+"]
 ----
-2021-12-01 18:26:42,369 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.2]:5701 [blue] [{full-version}] 
+2021-12-01 18:26:42,369 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.2]:5701 [blue] [{full-version}]
 
 Members {size:1, ver:1} [
 	Member [172.18.0.2]:5701 - c00213e1-da50-4b5f-a53b-ccfe4a1ebeea this
@@ -81,9 +81,9 @@ Start another local single-member cluster called `green`.
 docker run \
     --network hazelcast-network \
     --rm \
-    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5702 \
+    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5702 \ <1>
     -e HZ_CLUSTERNAME=green \
-    -e HZ_LICENSEKEY=<your license key> \ <1>
+    -e HZ_LICENSEKEY=<your license key> \ <2>
     -p 5702:5701 hazelcast/hazelcast-enterprise:{full-version}
 ----
 <1> Replace the `<host_ip>` placeholder with the IP address of your Docker host.
@@ -93,7 +93,7 @@ See the `green` cluster is formed:
 
 [source,shell,subs="attributes+"]
 ----
-2021-12-01 18:28:46,299 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.3]:5701 [green] [{full-version}] 
+2021-12-01 18:28:46,299 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.3]:5701 [green] [{full-version}]
 
 Members {size:1, ver:1} [
 	Member [172.18.0.3]:5701 - 72f5520c-8c27-4501-9199-a8da6b58c0b4 this
@@ -128,11 +128,11 @@ For this, you need to create two client configurations for the same client, and
 . Create the client configuration file for the `blue` cluster, called `client-blue.yaml` (or `client-blue.xml`)
 and place it in the `resources` directory:
 +
-[tabs] 
-==== 
-YAML:: 
-+ 
--- 
+[tabs]
+====
+YAML::
++
+--
 .client-blue.yaml
 [source,yaml]
 ----
@@ -172,11 +172,11 @@ For testing/development purposes, set to 1000 milliseconds to see the client con
 . Create the client configuration for the `green` cluster, called `client-green.yaml` (or `client-green.xml`)
 and place it in the `resources` directory:
 +
-[tabs] 
-==== 
-YAML:: 
-+ 
--- 
+[tabs]
+====
+YAML::
++
+--
 .client-green.yaml
 [source,yaml]
 ----
@@ -217,11 +217,11 @@ For testing/development purposes, set to 1000 milliseconds to see the client con
 The name of the client failover configuration file must be `hazelcast-client-failover` (`hazelcast-client-failover.yaml` or `hazelcast-client-failover.xml`).
 Place this failover configuration file in the `resources` directory.
 +
-[tabs] 
-==== 
-YAML:: 
-+ 
--- 
+[tabs]
+====
+YAML::
++
+--
 .hazelcast-client-failover.yaml
 [source,yaml]
 ----
@@ -261,15 +261,15 @@ see xref:clients:java#ordering-of-clusters-when-clients-try-to-connect.adoc[Orde
 
 In this step, you'll start the client.
 
-[tabs] 
-==== 
-Java:: 
+[tabs]
+====
+Java::
 +
 
 . Install the xref:getting-started:install-hazelcast.adoc#use-java[Java client library].
 . Add the following to the `MyClient.java` file.
 +
--- 
+--
 [source,java,subs="attributes+"]
 ----
 import com.hazelcast.client.HazelcastClient;
@@ -334,7 +334,7 @@ const { Client } = require('hazelcast-client');
             }
         ]
       });
-        
+
     } catch (err) {
         console.error('Error occurred:', err);
     }
@@ -377,7 +377,7 @@ Dec 01, 2021 8:16:45 PM com.hazelcast.core.LifecycleService
 INFO: hz.client_1 [green] [{full-version}] HazelcastClient {full-version} (20210922 - dbaeffe) is CLIENT_CONNECTED
 ----
 
-NOTE: In this type of failover scenario, the client does not automatically reconnect to the `blue` cluster when it is back online. Instead, you need to deploy a deny list to block client connections to the `green` cluster. The client will then use the failover configuration (in <<step-3, Step 3>>) to reconnect to the original cluster. When the client is reconnected, you can remove the client filter. 
+NOTE: In this type of failover scenario, the client does not automatically reconnect to the `blue` cluster when it is back online. Instead, you need to deploy a deny list to block client connections to the `green` cluster. The client will then use the failover configuration (in <<step-3, Step 3>>) to reconnect to the original cluster. When the client is reconnected, you can remove the client filter.
 
 == Step 6. Shut Down the Cluster
 
@@ -386,7 +386,7 @@ move to the other tutorials. To shut down the cluster, close the terminals in wh
 
 == Next Steps
 
-If you're interested in learning more about the topics introduced in this tutorial, see: 
+If you're interested in learning more about the topics introduced in this tutorial, see:
 
 * xref:clients:java#blue-green-deployment-and-disaster-recovery.adoc[Blue-Green Deployment].
 * xref:{page-latest-supported-mc}@management-center:clusters:client-filtering.adoc[Filtering Client Connections].
diff --git a/docs/modules/getting-started/pages/persistence.adoc b/docs/modules/getting-started/pages/persistence.adoc
@@ -28,7 +28,7 @@ To complete this tutorial, you need the following:
 |xref:getting-started:enterprise-overview.adoc[]
 
 |Docker network with the name `hazelcast-network`
-|Use the `docker network create hazelcast-network` command 
+|Use the `docker network create hazelcast-network` command
 
 |===
 
@@ -41,12 +41,12 @@ You'll start the first member in a cluster called `hello-world`. Run the followi
 docker run \
     --name first-member --network hazelcast-network \
     --rm \
-    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5701 \
+    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5701 \ <1>
     -e HZ_CLUSTERNAME=hello-world \
-    -e HZ_LICENSEKEY=<your license key> \ <1>
-    -e HZ_PERSISTENCE_ENABLED=true \ <2>
-    -e HZ_MAP_MYDISTRIBUTEDMAP_DATAPERSISTENCE_ENABLED=true \ <3>
-    -v ~/persist:/opt/hazelcast/persistence \ <4>
+    -e HZ_LICENSEKEY=<your license key> \ <2>
+    -e HZ_PERSISTENCE_ENABLED=true \ <3>
+    -e HZ_MAP_MYDISTRIBUTEDMAP_DATAPERSISTENCE_ENABLED=true \ <4>
+    -v ~/persist:/opt/hazelcast/persistence \ <5>
     -p 5701:5701 hazelcast/hazelcast-enterprise:{full-version}
 ----
 <1> Replace the `<host_ip>` placeholder with the IP address of your Docker host.
@@ -182,7 +182,7 @@ image:map-details.png[Map details]
 
 Now, you'll shut down the whole cluster using Management Center.
 
-. While in Management Center, go to **Cluster** > **Administration**, and select the **Cluster State** tab. 
+. While in Management Center, go to **Cluster** > **Administration**, and select the **Cluster State** tab.
 +
 image:cluster-state.png[Shutting down the cluster]
 . Click on the **Shutdown** button and confirm it on the dialog shown afterwards.
@@ -198,7 +198,7 @@ Restart the cluster by starting all the members; run the commands in Step 1 and
 
 Once all the members are started, go to Management Center, and you can see that it reconnects to the cluster.
 Check your map as instructed in Step 4 above; you will see the map and its data has been recovered.
-If the persistence was not enabled, the data would be lost in case of a cluster shutdown. 
+If the persistence was not enabled, the data would be lost in case of a cluster shutdown.
 
 == Step 8. Shut Down the Cluster
 

diff --git a/docs/modules/getting-started/pages/wan.adoc b/docs/modules/getting-started/pages/wan.adoc
@@ -30,7 +30,7 @@ To complete this tutorial, you need the following:
 |xref:getting-started:enterprise-overview.adoc[]
 
 |Docker network with the name `hazelcast-network`
-|Use the `docker network create hazelcast-network` command 
+|Use the `docker network create hazelcast-network` command
 
 |===
 
@@ -43,8 +43,8 @@ which means it does not need WAN Replication to be configured. Run the following
 ----
 docker run \
     --network hazelcast-network \
-    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5701 \
-    -e HZ_LICENSEKEY=<your license key> \ <1>
+    -e HZ_NETWORK_PUBLICADDRESS=<host_ip>:5701 \ <1>
+    -e HZ_LICENSEKEY=<your license key> \ <2>
     -e HZ_CLUSTERNAME=london \
     hazelcast/hazelcast-enterprise:{full-version}
 ----
@@ -55,7 +55,7 @@ The member is up and running now.
 
 [source,shell,subs="attributes+"]
 ----
-2021-11-23 11:08:15,055 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.3]:5701 [london] [{full-version}] 
+2021-11-23 11:08:15,055 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.3]:5701 [london] [{full-version}]
 
 Members {size:1, ver:1} [
 	Member [172.18.0.3]:5701 - bed20746-1505-449b-9f4a-548bcdbe12b8 this
@@ -130,7 +130,7 @@ Here is your other single-member cluster:
 
 [source,shell,subs="attributes+"]
 ----
-2021-11-23 11:39:14,198 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.4]:5701 [tokyo] [{full-version}] 
+2021-11-23 11:39:14,198 [ INFO] [main] [c.h.i.c.ClusterService]: [172.18.0.4]:5701 [tokyo] [{full-version}]
 
 Members {size:1, ver:1} [
 	Member [172.18.0.4]:5701 - 98d9a815-5eb3-4341-bec1-e9816cee44b5 this
@@ -182,7 +182,7 @@ docker run --network hazelcast-network -it --rm hazelcast/hazelcast:{full-versio
 [source,sql]
 ----
 CREATE MAPPING cities (__key INT, country VARCHAR, city VARCHAR)
-TYPE IMap 
+TYPE IMap
 OPTIONS ('keyFormat'='int', 'valueFormat' = 'json-flat');
 ----
 . Then, type the following command and press kbd:[Enter] to add data to the map.
@@ -211,8 +211,8 @@ You can also see the map and its entries in Management Center, using the SQL bro
 +
 image:wan/map-tokyo.png[Cities map in Tokyo cluster]
 . Click on **SQL Browser** located on the very top right of the user interface and choose `cities` in the *select a map* field.
-The SQL browser then shows the default query in its editor, `SELECT * FROM cities;`. 
-. Click on **Execute Query**; you will see the data you've put in. 
+The SQL browser then shows the default query in its editor, `SELECT * FROM cities;`.
+. Click on **Execute Query**; you will see the data you've put in.
 +
 image:wan/map-entries.png[Management Center's SQL Browser shows the map data]
 . Close the SQL browser.
@@ -233,7 +233,7 @@ Open the SQL browser, type in the following query.
 [source,sql]
 ----
 CREATE MAPPING cities (__key INT, country VARCHAR, city VARCHAR)
-TYPE IMap 
+TYPE IMap
 OPTIONS ('keyFormat'='int', 'valueFormat' = 'json-flat');
 ----
 . Click **Execute Query**.

diff --git a/docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc b/docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc
@@ -81,15 +81,15 @@ The following table lists the configurable parameters of the Hazelcast chart and
 |Parameter|Description|Default
 
 | image.repository| Hazelcast Image name | hazelcast/hazelcast
-| image.tag| Hazelcast Image tag| {VERSION}
+| image.tag| Hazelcast Image tag| \{VERSION}
 | image.pullPolicy| Image pull policy| IfNotPresent
 | image.pullSecrets | Specify docker-registry secret names as an array| nil
 | cluster.memberCount | Number of Hazelcast members| 3
 | hazelcast.enabled | Turn on and off Hazelcast application| true
 | hazelcast.javaOpts| Additional JAVA_OPTS properties for Hazelcast member| nil
 | hazelcast.loggingLevel| Level of Hazelcast logs (OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE and ALL)| nil
 | hazelcast.existingConfigMap| ConfigMap which contains Hazelcast configuration file(s) that are used instead of hazelcast.yaml file embedded into values.yaml | nil
-| hazelcast.yaml| Hazelcast YAML Configuration (hazelcast.yaml embedded into values.yaml)| {DEFAULT_HAZELCAST_YAML}
+| hazelcast.yaml| Hazelcast YAML Configuration (hazelcast.yaml embedded into values.yaml)| \{DEFAULT_HAZELCAST_YAML}
 | hazelcast.configurationFiles | Hazelcast configuration files| nil
 | annotations | Hazelcast Statefulset annotations| nil
 | affinity| Hazelcast Node affinity| nil
@@ -169,7 +169,7 @@ The following table lists the configurable parameters of the Hazelcast chart and
 | jet.enabled| Turn on and off Hazelcast Jet engine| true
 | mancenter.enabled| Turn on and off Management Center application| true
 | mancenter.image.repository| Hazelcast Management Center Image name| hazelcast/management-center
-| mancenter.image.tag | Hazelcast Management Center Image tag (NOTE: must be the same or one minor release greater than Hazelcast image version) | {VERSION}
+| mancenter.image.tag | Hazelcast Management Center Image tag (NOTE: must be the same or one minor release greater than Hazelcast image version) | \{VERSION}
 | mancenter.image.pullPolicy| Image pull policy| IfNotPresent
 | mancenter.image.pullSecrets | Specify docker-registry secret names as an array| nil
 | mancenter.contextPath | The value for the `MC_CONTEXT_PATH` environment variable. It sets the prefix of all URL paths in Management Center| nil
@@ -180,7 +180,7 @@ The following table lists the configurable parameters of the Hazelcast chart and
 | mancenter.licenseKey| License Key for Hazelcast Management Center, if not provided, can be filled in the web interface| nil
 | mancenter.licenseKeySecretName| Kubernetes Secret Name, where Management Center License Key is stored (can be used instead of licenseKey)| nil
 | mancenter.adminCredentialsSecretName | Kubernetes Secret Name for admin credentials. Secret has to contain `username` and `password` literals. please check Management Center documentation for password requirements| nil
-| mancenter.existingConfigMap | ConfigMap which contains Hazelcast Client configuration file(s) that are used instead of hazelcast-client.yaml file embedded into values.yaml | {DEFAULT_HAZELCAST_CLIENT_YAML}
+| mancenter.existingConfigMap | ConfigMap which contains Hazelcast Client configuration file(s) that are used instead of hazelcast-client.yaml file embedded into values.yaml | \{DEFAULT_HAZELCAST_CLIENT_YAML}
 | mancenter.yaml | Hazelcast Client YAML Configuration (hazelcast-client.yaml used to connect to Hazelcast cluster | nil
 | mancenter.annotations | Management Center Statefulset annotations | nil
 | mancenter.affinity| Management Center Node affinity| nil
@@ -307,4 +307,4 @@ rest-api:
       enabled: true
     CLUSTER_WRITE:
       enabled: true
-----
+----
diff --git a/docs/modules/kubernetes/pages/helm-hazelcast-enterprise-chart.adoc b/docs/modules/kubernetes/pages/helm-hazelcast-enterprise-chart.adoc
@@ -84,7 +84,7 @@ The following table lists the configurable parameters of the Hazelcast chart and
 |Parameter|Description|Default
 
 |image.repository|Hazelcast Image name|hazelcast/hazelcast-enterprise
-|image.tag|Hazelcast Image tag|{VERSION}
+|image.tag|Hazelcast Image tag|\{VERSION}
 |image.pullPolicy|Image pull policy|IfNotPresent
 |image.pullSecrets|Specify docker-registry secret names as an array|nil
 |cluster.memberCount|Number of Hazelcast members|3
@@ -95,7 +95,7 @@ The following table lists the configurable parameters of the Hazelcast chart and
 |hazelcast.javaOpts|Additional JAVA_OPTS properties for Hazelcast member|nil
 |hazelcast.loggingLevel|Level of Hazelcast logs (OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE and ALL)|nil
 |hazelcast.existingConfigMap|ConfigMap which contains Hazelcast configuration file(s) that are used instead hazelcast.yaml embedded into values.yaml|nil
-|hazelcast.yaml|Hazelcast YAML Configuration (hazelcast.yaml embedded into values.yaml)|{DEFAULT_HAZELCAST_YAML}
+|hazelcast.yaml|Hazelcast YAML Configuration (hazelcast.yaml embedded into values.yaml)|\{DEFAULT_HAZELCAST_YAML}
 |hazelcast.configurationFiles|Hazelcast configuration files|nil
 |annotations| Hazelcast Statefulset annotations| nil
 |affinity|Hazelcast Node affinity|nil
@@ -182,7 +182,7 @@ The following table lists the configurable parameters of the Hazelcast chart and
 |env|Additional Environment variables|[]
 |mancenter.enabled|Turn on and off Management Center application|true
 |mancenter.image.repository|Hazelcast Management Center Image name|hazelcast/management-center
-|mancenter.image.tag|Hazelcast Management Center Image tag (NOTE: must be the same or one minor release greater than Hazelcast image version)|{VERSION}
+|mancenter.image.tag|Hazelcast Management Center Image tag (NOTE: must be the same or one minor release greater than Hazelcast image version)|\{VERSION}
 |mancenter.image.pullPolicy|Image pull policy|IfNotPresent
 |mancenter.image.pullSecrets|Specify docker-registry secret names as an array|nil
 |mancenter.contextPath|The value for the `MC_CONTEXT_PATH` environment variable. It sets the prefix of all URL paths in Management Center|nil
@@ -294,4 +294,4 @@ persistence:
   validation-timeout-seconds: 1200
   data-load-timeout-seconds: 900
   auto-remove-stale-data: true
-----
+----