hazelcast · Serdaro · Aug 16, 2023 · Aug 11, 2023
diff --git a/README.adoc b/README.adoc
@@ -156,7 +156,7 @@ For example, if you are releasing version 5.1, create a new release branch named
 +
 IMPORTANT: If you are creating a branch for a beta release, do not remove the `prerelease` field.
 
-. When you are ready to release, create a maintentance branch from the release branch.
+. When you are ready to release, create a maintenance branch from the release branch.
 +
 NOTE: As soon as you push the maintenance branch to the repository, GitHub will trigger a new build of the site, which will include your new content.
 

diff --git a/docs/modules/clusters/pages/cluster-state.adoc b/docs/modules/clusters/pages/cluster-state.adoc
@@ -1,7 +1,7 @@
 = Cluster State
 :description: You can use the Cluster State tab of the Administration menu item to see your cluster's name, state, and to shut down the whole cluster.
 
-You can use the *Cluster State* tab of the *Administration* menu item to to see your cluster's name, state, and to shut down the whole cluster.
+You can use the *Cluster State* tab of the *Administration* menu item to see your cluster's name, state, and to shut down the whole cluster.
 
 This page is available only to admin users.
 

diff --git a/docs/modules/data-structures/pages/cache.adoc b/docs/modules/data-structures/pages/cache.adoc
@@ -7,7 +7,7 @@ page is opened on the right, as shown below.
 
 image:ROOT:CacheGridView.png[Cache Grid View]
 
-You can filter the caches shown and you can also sort the table
+You can filter the caches shown and sort the table
 by clicking on the column headers. Clicking on
 the cache name opens a new page for monitoring that cache
 instance on the right, as shown below.
@@ -71,7 +71,7 @@ From left to right, this table lists the following:
 * IP address and port of each member.
 * Put, get and remove operation rates on each member for this cache.
 
-You can select the period in the combo box placed at the top right
+You can select the period in the combo box placed in the top right
 corner of the window, for which the table data will be shown. Available
 values are **Since Beginning**, **Last Minute**, **Last 10 Minutes**
 and **Last 1 Hour**.

diff --git a/docs/modules/data-structures/pages/executor.adoc b/docs/modules/data-structures/pages/executor.adoc
@@ -15,7 +15,7 @@ instance on the right, as shown below.
 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[the graph section] for more information.
+See the xref:getting-started:graphs.adoc[graph section] for more information.
 
 image:ROOT:MonitoringOptionsExecutor.png[alt=Monitoring Options for Executor]
 

diff --git a/docs/modules/data-structures/pages/map.adoc b/docs/modules/data-structures/pages/map.adoc
@@ -223,7 +223,7 @@ From left to right, this table lists the following:
 
 |===
 
-You can select the time period in the combo box placed on the top
+You can select the time period in the combo box placed in the top
 right corner of the window, for which the table data will be
 shown. Available values are **Since Beginning**, **Last Minute**,
 **Last 10 Minutes** and **Last 1 Hour**.

diff --git a/docs/modules/deploy-manage/pages/configuring.adoc b/docs/modules/deploy-manage/pages/configuring.adoc
@@ -18,7 +18,7 @@ You can configure Management Center to save this data in a different location, u
 
 You can either configure Management Center in the UI while it's running or preconfigure it in the terminal so that it starts with the settings you need.
 
-.Configuration methods for Managment Center
+.Configuration methods for Management Center
 [cols="20%a,80%a"]
 |===
 |Configuration method|Use case

diff --git a/docs/modules/deploy-manage/pages/connecting-to-clusters-ui.adoc b/docs/modules/deploy-manage/pages/connecting-to-clusters-ui.adoc
@@ -24,7 +24,7 @@ image:ROOT:AddClusterConfig.png[alt=Add New Cluster Configuration]
 
 . Enter the name of the cluster that you want to connect to.
 
-. Enter the hostnames or IP adresses of cluster members that you want to connect to. Press *Enter* after each address to add it to the list.
+. Enter the hostnames or IP addresses of cluster members that you want to connect to. Press *Enter* after each address to add it to the list.
 +
 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 list. 
 
@@ -144,7 +144,7 @@ If your cluster has the Jet engine enabled, you will also see that the cluster s
 
 To connect to another cluster, you can repeat these steps with a different configuration file.
 
-NOTE: Management Center requires a connection to every member in order to collect its state, events and metrics so unisocket connections are not supported.  An error message will be shown if the configuraton uses a unisocket connection.
+NOTE: Management Center requires a connection to every member in order to collect its state, events and metrics so unisocket connections are not supported.  An error message will be shown if the configuration uses a unisocket connection.
 
 == Cluster Connection Diagnosis
 

diff --git a/docs/modules/deploy-manage/pages/historical-metrics.adoc b/docs/modules/deploy-manage/pages/historical-metrics.adoc
@@ -20,7 +20,7 @@ For example:
 . A one-minute bucket is created for each metric type in memory and each bucket's timestamp is set to 9:00:00 AM. At this point nothing is saved to disk.
 . The next chunk of metrics is received at 9:00:03 AM. No new one-minute buckets are created, only the new metrics are added to the existing one-minute buckets.
 . The first metrics-persistence thread run starts at 9:00:10 AM.
-The thread didn’t find any minute buckets that are 70 seconds old.
+The thread didn't find any minute buckets that are 70 seconds old.
 Still, nothing is saved to disk.
 . At 9:01:10 AM, the metrics-persistence thread saves the compressed one-minute buckets to disk.
 

diff --git a/docs/modules/deploy-manage/pages/license-management.adoc b/docs/modules/deploy-manage/pages/license-management.adoc
@@ -33,6 +33,6 @@ To update an Enterprise license for Management Center, see xref:updating-mc-lice
 
 == Updating Cluster Licenses at Runtime
 
-You can use Management Center to update an existing Enteprise license in your Hazelcast cluster. See xref:clusters:update-config.adoc[].
+You can use Management Center to update an existing Enterprise license in your Hazelcast cluster. See xref:clusters:update-config.adoc[].
 
 Or, for other ways to update a license, see the xref:{page-latest-supported-hazelcast}@hazelcast:deploy:enterprise-licenses.adoc[Hazelcast Platform documentation].
diff --git a/docs/modules/deploy-manage/pages/local-security-provider.adoc b/docs/modules/deploy-manage/pages/local-security-provider.adoc
@@ -47,8 +47,8 @@ Passwords *must not* include the following:
 
 * The username
 * Two or more of the same letter following each other.
-* A 3-character or longer sequence of letters following or preceeding each other such as "abc" or "fed".
-* A 3-character or longer sequence of digits following or preceeding each other such as "123" or "987".
+* A 3-character or longer sequence of letters following or preceding each other such as "abc" or "fed".
+* A 3-character or longer sequence of digits following or preceding each other such as "123" or "987".
 
 == Creating Users
 

diff --git a/docs/modules/deploy-manage/pages/logging.adoc b/docs/modules/deploy-manage/pages/logging.adoc
@@ -69,7 +69,7 @@ Management Center with the `hazelcast.mc.log.level` property. For example, to us
 -Dhazelcast.mc.log.level=debug
 ```
 
-== Customizing the Logging Configuraton
+== Customizing the Logging Configuration
 
 To further customize the logging configuration, you can create a custom
 Log4j configuration file and start Management Center with

diff --git a/docs/modules/deploy-manage/pages/serving-https.adoc b/docs/modules/deploy-manage/pages/serving-https.adoc
@@ -62,7 +62,7 @@ javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
 No subject alternative names matching IP address 127.0.0.1 found
 ```
 
-When using a self-signed certificate, your browser may warn you that the connection is not secure. If so, add your certficate to the browsers list of trusted certificates.
+When using a self-signed certificate, your browser may warn you that the connection is not secure. If so, add your certificate to the browsers list of trusted certificates.
 
 == Overrriding the Default HTTPS port
 

diff --git a/docs/modules/getting-started/pages/install.adoc b/docs/modules/getting-started/pages/install.adoc
@@ -132,7 +132,7 @@ Windows::
 --
 At the moment, Management Center does not support any Windows package managers.
 
-To get started with Management Center on Windows, use one of the other available installation option.
+To get started with Management Center on Windows, use one of the other available installation options.
 --
 ====
 
@@ -291,5 +291,5 @@ See also the following for the Management Center features that rely on your clus
 
 * xref:clusters:wan-replication.adoc[WAN Replication]
 * xref:clusters:persistence.adoc[Persistence]
-* xref:clusters:triggering-rolling-upgrade[Rolling Upgrades]
+* xref:clusters:triggering-rolling-upgrade.adoc[Rolling Upgrades]
 ====
diff --git a/docs/modules/monitor-streaming/pages/jobs.adoc b/docs/modules/monitor-streaming/pages/jobs.adoc
@@ -164,10 +164,10 @@ CPU-heavy sync call.
 ** **internal processing latency of Hazelcast**; typically
 very low: 1 or 2 milliseconds. It can be higher if the network is slow, system
 is overloaded, if there are many vertices in the job or many
-jobs, which causes lot of switching, etc.
+jobs, which causes lots of switching, etc.
 ** **clock drift**; since we're comparing to the real time,
 latency can be caused by a clock drift between the machine
-where event time is assigned (which can be also be an end
+where event time is assigned (which can also be an end
 user’s device). It can even be negative. Always use NTP to
 keep wall-clock precise and avoid using timestamps from devices
 out of your control as event time.

diff --git a/docs/modules/release-notes/pages/5-1-1.adoc b/docs/modules/release-notes/pages/5-1-1.adoc
@@ -15,7 +15,7 @@
 == Enhancements
 
 * Security: Console access can be enabled or disabled in the members' config.  This defaults to disabled (breaking change). See xref:{page-latest-supported-hazelcast}@hazelcast:maintain-cluster:monitoring.adoc#managing-console-support[Managing Console Support] in the Platform documentation. [MC-1121]
-* Security: Data acess via the SQL Browser and Map Browser can be disabled in the members' configuration. [MC-1039]
+* Security: Data access via the SQL Browser and Map Browser can be disabled in the members' configuration. [MC-1039]
 * Standardization of naming of start scripts.  `hz-mc` should be used and `hz-mc conf` for any MC offline configuration. [MC-1087]
 * Introduced the `mc-hz conf cluster list` command to list all configured cluster names. [MC-1091]
 * SQL Browser provides instructions if `hazelcast-sql` has not been included in the classpath. [MC-871]
@@ -24,7 +24,7 @@
 * SQL Browser the returned results for each field is capped to 1024 characters to prevent large fields from slowing down MC. [MC-1203]
 * MC now quickly identifies whether the cluster has SQL/Streaming enabled or not. [MC-992]
 * xref:clusters:healthcheck.adoc[Config healthcheck] can be customised to ignore specific problems via the Ignore button. [MC-541]
-* Updated Config Heatcheck to allow different config for some security parts. [ [MC-925]
+* Updated Config Healthcheck to allow different config for some security parts. [ [MC-925]
 * Added a button to xref:data-structures:map.adoc[clear all map entries]. [MC-1176]
 * Queues age-related queue metrics can now be reset. [MC-1109]
 * Improved tables with auto widths based on the content. [MC-1073]
@@ -56,7 +56,7 @@
 * Fixed the tooltips shown in the WAN Replication screens so they do not overlap. [MC-1153]
 * Fix for displaying a large number of maps in the WAN Sync screen. [MC-1185]
 * Fix for the maps counter in the left menu to say the total maps count includes system maps. [MC-1207]
-* Fix for the Map Browser TTL value to show time remaining rather than an expiray date. [MC-1366]
+* Fix for the Map Browser TTL value to show time remaining rather than an expiry date. [MC-1366]
 * Maximize chart icon is no longer shown after clicking on it. [MC-1141]
 
 == Breaking Changes

diff --git a/docs/modules/tools/pages/console.adoc b/docs/modules/tools/pages/console.adoc
@@ -10,7 +10,7 @@ WARNING: The console is not recommended for production use.
 Console is disabled by default, and you need to enable it
 in your cluster's configuration. See the
 xref:{page-latest-supported-hazelcast}@hazelcast:maintain-cluster:monitoring.adoc#managing-console-support[Toggle Console Support] for details. The member list shows whether
-console is enabled or disabled for each member.
+the console is enabled or disabled for each member.
 
 . Open a console window by clicking on the **Console** button located at the top menu.
 +