Align docs with MC 5.4.0

docs/modules/clusters/pages/administration.adoc

@@ -4,6 +4,8 @@
 
 You can use the *Administration* menu item to manage Hazelcast clusters.
 
+image:ROOT:Administration.png[Changing Cluster state]
+
 NOTE: This menu item is available only to admin users.
 
 From this menu item, you can do the following:

docs/modules/clusters/pages/clients.adoc

@@ -18,10 +18,8 @@ image:ROOT:ClientGridView.png[Client Grid View]
 |Local IP address, hostname, or canonical hostname of the client, depending on the <<client-address-types, client address filter>>.
 
 |Type
-|Type of client. This field usually contains the client's programming language.
-
-|Enterprise
-|Whether the client is an Enterprise Java client. Although non-Java clients can also connect to Enterprise clusters, the Java client includes Enterprise features that non-Java clients do not.
+|Type of client. This field typically denotes the client's programming language and indicates whether it is an Enterprise Java client.
+Although non-Java clients can also connect to Enterprise clusters, the Java client includes Enterprise features that non-Java clients do not.
 
 |Member Connection
 |The member that the client is

docs/modules/clusters/pages/cluster-license.adoc

@@ -5,12 +5,13 @@ You can use the *Cluster License* tab of the *Administration* menu item to see d
 
 This page is available only to admin users.
 
-image:ROOT:cluster-license.png[Cluster License page]
+image:ROOT:ClusterLicense.png[Cluster License page]
 
 - *License Key Hash*: SHA-256 hash of the key as a Base64 encoded string. The actual key is not displayed for security reasons.
 - *Expires*: The date on which the license will expire.
 - *Licensed Cluster Members*: The total number of members that the license supports and the current number of members running on the license.
-- *License Type*: The type of license.
+- *Allowed Tiered Store Size*: Allowed size of Tiered Store, if the license includes Tiered Storage feature.
+- *Allowed Native Memory Size*: Allowed size of Native Memory, if the license includes High Density Memory feature.
 
 Warnings are displayed when a license expires within 30 days.
 

docs/modules/clusters/pages/members.adoc

@@ -263,7 +263,7 @@ Any time difference greater than one minute between the Management Center and a
 issues, delayed responses or data loss. To prevent such issues, Management Center would report the members that have such
 time differences to the user.
 
-You can view the detected members in the warning notification that is positioned just below the top bar.
+You can view the detected members in the warning notification that is positioned just below the Top Bar.
 
 image:ROOT:ClockSynchronization.png[Clock Synchronization]
 

docs/modules/clusters/pages/update-config.adoc

@@ -40,12 +40,14 @@ You can add configuration blocks to the text field or you can upload a YAML or X
 NOTE: If you submit an existing configuration block, other than `license`, 
 that already exists, the cluster ignores that configuration block and applies only the new ones.
 
-.Update Config page
+Update Config page
+
 image:ROOT:UpdateConfigData.png[Update Config With Data]
 
 To check which configuration blocks will be applied, click the *Preview* button.
 
-.Preview
+Preview
+
 image:ROOT:UpdateConfigPreview.png[Update Config Preview]
 
 To apply the new configuration, click the *Submit* button.

docs/modules/cp-subsystem/pages/atomic-ref.adoc

@@ -5,6 +5,4 @@ by clicking on the **Atomic References** menu item in the left menu.
 
 image:ROOT:AtomicReferences.png[Atomic References View]
 
-An atomic reference has only a single metric: Its name.
-
 You can sort the table by clicking on the column headers.

docs/modules/cp-subsystem/pages/cpmap.adoc

@@ -1,4 +1,4 @@
-= CP Maps
+= CPMaps
 
 You can see a list of all the xref:{page-latest-supported-hazelcast}@hazelcast:data-structures:cpmap.adoc[CPMaps] in your cluster
 by clicking on the **CPMaps** menu item in the left menu.

docs/modules/cp-subsystem/pages/fenced-lock.adoc

@@ -7,8 +7,8 @@ image:ROOT:FencedLocks.png[Fenced Locks View]
 
 A fenced lock has two fixed metrics:
 
-- *Lock Count*: Total number of times the lock has been acquired.
 - *Acquire Limit*: Maximum number of reentrant acquires, which is configured in the CP member's xref:{page-latest-supported-hazelcast}@hazelcast:cp-subsystem:configuration.adoc#fencedlock-configuration[`lock-acquire-limit`] option.
+- *Lock Count*: Total number of times the lock has been acquired.
 
 If lock is held by an endpoint, the following additional metrics are displayed:
 

docs/modules/data-structures/pages/executor.adoc

@@ -17,27 +17,8 @@ image:ROOT:MonitoringExecutors.png[Monitoring Executors]
 On top of the page, there are two graphs that show various metrics of the Executor.
 See the xref:getting-started:graphs.adoc[graph section] for more information.
 
-image:ROOT:MonitoringOptionsExecutor.png[alt=Monitoring Options for Executor]
-
-When you click on a desired monitoring, the chart loads with the
-selected option. To open a chart as a separate dialog, click on the
-image:ROOT:MaximizeChart.png[maximize] button placed at top right of each
-chart. The below monitoring charts are available:
-
-* **Pending**: Monitors the pending executors. Y-axis is the executor count.
-* **Started**: Monitors the started executors. Y-axis is the executor count.
-* **Start Lat. (msec.)**: Shows the latency when executors are started.
-Y-axis is the duration in milliseconds.
-* **Completed**: Monitors the completed executors. Y-axis is the executor count.
-* **Comp. Time (msec.)**: Shows the completion period of executors.
-Y-axis is the duration in milliseconds.
-
 Under these charts is the [[executor-operation-statistics]]**Executor Operation Statistics**
-table, as shown below.
-
-image:ROOT:ExecutorOperationStats.png[Executor Operation Statistics]
-
-From left to right, this table lists the IP address and port of
+table. From left to right, this table lists the IP address and port of
 members, the counts of pending, started and completed executors
 per second, and the execution time and average start latency of
 executors on each member. Click on the column heading to ascend

docs/modules/data-structures/pages/map.adoc

@@ -113,7 +113,7 @@ the window. Once opened, the tool appears as a dialog, as shown below.
 
 image:ROOT:MapConfig.png[Map Config Tool]
 
-You can change any attribute and click the **Update** button to save
+You can change any attribute and click the **Save Configuration** button to save
 your changes.
 
 NOTE: The Map configuration is updated only on the members that Management Center is aware of at the time of the update. When a new member joins the cluster, the updated map configuration is not propagated to it.
@@ -153,9 +153,12 @@ From left to right, this table lists the following:
 |Puts
 |Number of put operations received by the member.
 
-|Removes
+|Removals
 |Number of remove operations received by the member.
 
+|Sets
+|Number of local set operations received by the member.
+
 |Entry Memory
 |Memory cost of owned entries in the member.
 
@@ -212,6 +215,9 @@ From left to right, this table lists the following:
 |Removes/s
 |Number of remove operations per second on the member.
 
+|Sets/s
+|Number of local set operations per second on the member.
+
 |Avg Put Latency
 |Average latency of put operations on the member.
 
@@ -221,6 +227,9 @@ From left to right, this table lists the following:
 |Avg Remove Latency
 |Average latency of remove operations on the member.
 
+|Avg Set Latency
+|Average latency of set operations on the member.
+
 |Max Avg Put Latency
 |Maximum average latency of put operations on the member.
 
@@ -230,6 +239,9 @@ From left to right, this table lists the following:
 |Max Avg Remove Latency
 |Maximum average latency of remove operations on the member.
 
+|Max Avg Set Latency
+|Maximum average latency of set operations on the member.
+
 |===
 
 You can select the time period in the combo box placed in the top
@@ -267,8 +279,8 @@ From left to right, this table lists the following:
 |Misses
 |Count of the entries which cannot be found in the Near Cache when requested to read.
 
-|Ratio
-|Hits/Misses ratio.
+|Effectiveness
+|Hits/total reads ratio.
 
 |===
 

docs/modules/data-structures/pages/overview.adoc

@@ -8,24 +8,25 @@
 
 Under the *Storage* menu, you'll find the following pages:
 
-* xref:data-structures:map.adoc[Map]. Here, you can also set the selected map's attributes.
-* xref:data-structures:cache.adoc[Cache]
-* xref:data-structures:replicated-map.adoc[Replicated Map]
-* xref:data-structures:multimap.adoc[MultiMap]
-* xref:data-structures:lock.adoc[Lock]
-* xref:data-structures:flake-id-gen.adoc[Flake ID Generator]
-* xref:data-structures:pn-counter.adoc[PN Counter]
+* xref:data-structures:map.adoc[Maps]. Here, you can also set the selected map's attributes.
+* xref:data-structures:replicated-map.adoc[Replicated Maps]
+* xref:data-structures:cache.adoc[Caches]
+* xref:data-structures:multimap.adoc[MultiMaps]
+* xref:data-structures:list.adoc[Lists]
+* xref:data-structures:set.adoc[Sets]
+* xref:data-structures:pn-counter.adoc[PN Counters]
+* xref:data-structures:flake-id-gen.adoc[Flake ID Generators]
 
 == Compute
 
 Under the *Compute* menu, you'll find the following pages:
 
-* xref:data-structures:executor.adoc[Executor]
+* xref:data-structures:executor.adoc[Executors]
 
 == Messaging
 
 Under the *Messaging* menu, you'll find the following pages:
 
-* xref:data-structures:queue.adoc[Queue]
-* xref:data-structures:topic.adoc[Topic]
-* xref:data-structures:reliable-topic.adoc[Reliable Topic]
+* xref:data-structures:queue.adoc[Queues]
+* xref:data-structures:topic.adoc[Topics]
+* xref:data-structures:reliable-topic.adoc[Reliable Topics]

docs/modules/data-structures/pages/reliable-topic.adoc

@@ -18,12 +18,9 @@ image:ROOT:MonitoringReliableTopics.png[Monitoring Reliable Topics]
 On top of the page, there are two graphs that show various metrics
 of the reliable topic. See the xref:getting-started:graphs.adoc[the graph section] for more information.
 
-Under these charts is the Reliable Topic Operation Statistics table.
+Under these charts is the Reliable Topic Throughput Statistics table.
 From left to right, this table lists the IP addresses and ports of
 each member, and counts of the messages published and received per
-second in real-time. You can select the period in the combo box placed
-at top right corner of the table to show the table data. The available
-values are **Since Beginning**, **Last Minute**, **Last 10 Minutes**
-and **Last 1 Hour**.
+second in real-time.
 
 Click on the column heading to ascend or descend the order of the listings.

docs/modules/data-structures/pages/topic.adoc

@@ -17,13 +17,10 @@ image:ROOT:MonitoringTopics.png[Monitoring Topics]
 On top of the page, there are two graphs that show various metrics of the topic.
 See the xref:getting-started:graphs.adoc[the graph section] for more information.
 
-Under these charts is the [[topic-operation-statistics]]Topic Operation Statistics table. From
+Under these charts is the [[topic-throughput-statistics]]Topic Throughput Statistics table. From
 left to right, this table lists the IP addresses and ports of each
 member, and counts of the messages published and received per second
-in real-time. You can select the period in the combo box placed at
-top right corner of the table to show the table data. The available
-values are **Since Beginning**, **Last Minute**, **Last 10 Minutes**
-and **Last 1 Hour**.
+in real-time.
 
 Click on the column heading to ascend or descend the order of
 the listings.

docs/modules/data-structures/partials/nav.adoc

@@ -9,6 +9,5 @@
 ** xref:data-structures:topic.adoc[]
 ** xref:data-structures:reliable-topic.adoc[]
 ** xref:data-structures:executor.adoc[]
-** xref:data-structures:lock.adoc[]
 ** xref:data-structures:pn-counter.adoc[]
 ** xref:data-structures:flake-id-gen.adoc[]

docs/modules/deploy-manage/pages/connecting-to-clusters-ui.adoc

@@ -16,7 +16,7 @@ NOTE: When connecting to multiple clusters from the same instance of Management
 == Using the Form Fields
 [[creating-a-cluster-configuration-using-form]]
 
-. Click to *Cluster Connections* in the toolbar.
+. Click to *Cluster Connections* in the Top Bar.
 
 . Click *Add* to start configuring a new connection.
 +
@@ -34,7 +34,7 @@ If this field is *Off*, Management Center will save the configuration but will n
 
 . Click *Connect*.
 +
-image:ROOT:ClusterConfAdded.png[alt=Cluster Configuration Added]
+image:ROOT:ConnectionEstablishedDev.png[alt=Cluster Configuration Added]
 
 You will see the following:
 
@@ -106,7 +106,7 @@ hazelcast-client:
 +
 As soon as Management Center connects to one member, it will auto-discover the other members of the cluster. But, for fault-tolerance, it's best to add more than one member's address to the `cluster-members` configuration.
 
-. Click to *Cluster Connections* in the toolbar.
+. Click to *Cluster Connections* in the Top Bar.
 
 . Click *Add* to start configuring a new connection.
 +
@@ -168,15 +168,15 @@ explanation or cancel the diagnostics.
 
 == Removing a Cluster Connection
 
-To remove an existing connection to a cluster, go to *Cluster Connections* in the toolbar and click the *trash icon* above the name of the cluster that you want to disconnect from Management Center.
+To remove an existing connection to a cluster, go to *Cluster Connections* in the Top Bar and click the *trash icon* above the name of the cluster that you want to disconnect from Management Center.
 
-image:ROOT:remove-connection.png[Trash icon above the name of a cluster called dev]
+image:ROOT:RemoveConnection.png[Trash icon above the name of a cluster called dev]
 
 == Editing a Cluster Connection
 
-To edit an existing connection, go to *Cluster Connections* in the toolbar and click the *configure icon* (next to the *trash icon*) above the name of the cluster.
+To edit an existing connection, go to *Cluster Connections* in the Top Bar and click the *configure icon* (next to the *trash icon*) above the name of the cluster.
 
-image:ROOT:edit-connection.png[Configure icon above the name of a cluster called dev]
+image:ROOT:EditConnection.png[Configure icon above the name of a cluster called dev]
 
 If you connected to the cluster from the form fields, you can edit the form.
 

docs/modules/deploy-manage/pages/license-management.adoc

@@ -10,8 +10,8 @@ Management Center requires a valid Enterprise license for the following:
 
 * Clustered JMX
 * Clustered REST API
-* Client Filtering on the cluster
-* Prometheus exporter
+* Cluster Client Filtering
+* Prometheus Exporter
 * Displaying metrics for more than three cluster members
 * Healthcheck