Fix typos identified by IntelliJ (#137)

Author: JackPGreen

README.adoc

@@ -47,7 +47,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 this field.
 
-. When you are ready to release, create a maintentance branch (`v/<version>`) from the release branch.
+. When you are ready to release, create a maintenance branch (`v/<version>`) 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.
 

antora-playbook.yml

@@ -20,7 +20,7 @@ asciidoc:
   attributes:
     # Download images from kroki at build time (does not work for inline images)
     kroki-fetch-diagram: true
-    # Inlude next and previous links on each page
+    # Include next and previous links on each page
     page-pagination: true
     idprefix: ''
     # Separate anchor link names by dashes

check-links-playbook.yml

@@ -148,7 +148,7 @@ asciidoc:
   attributes:
     # Download images from kroki at build time (does not work for inline images)
     kroki-fetch-diagram: true
-    # Inlude next and previous links on each page
+    # Include next and previous links on each page
     page-pagination: true
     idprefix: ''
     # Separate anchor link names by dashes

docs/modules/ROOT/pages/advanced-networking.adoc

@@ -1,6 +1,6 @@
 = Advanced Network Configuration
 
-In Hazelcast, you can configure the Hazelcast members with separate server sockets using a different network configuration for different protocols. It is called  link:https://docs.hazelcast.com/hazelcast/latest/clusters/network-configuration#advanced-network-configuration[ Advanced Network] and support Member, Client, REST, Memcache and WAN protocols.
+In Hazelcast, you can configure the Hazelcast members with separate server sockets using a different network configuration for different protocols. It is called link:https://docs.hazelcast.com/hazelcast/latest/clusters/network-configuration#advanced-network-configuration[Advanced Network] and support Member, Client, REST, Memcache and WAN protocols.
 
 In the Hazelcast Platform Operator, advanced networking configuration is enabled by default and REST and Client protocols are already configured:
 
@@ -28,6 +28,6 @@ The following example shows an example configuration for configuring WAN sockets
 include::ROOT:example$/advanced-networking-wan.yaml[]
 ----
 
-Possible values for `serviceType` are: `ClusterIP` and `LoadBalancer`. After applying this example configuration, there will be 1 service created with type of `LoadBalancer` which exposes 5 ports: `5710`, `5711`, `5712`, `5713`, `5714`. If you don't provide a `serviceType`, it will be set to `LoadBalancer` by default.
+Possible values for `serviceType` are: `ClusterIP` and `LoadBalancer`. After applying this example configuration, there will be 1 service created with a type of `LoadBalancer` which exposes 5 ports: `5710`, `5711`, `5712`, `5713`, `5714`. If you don't provide a `serviceType`, it will be set to `LoadBalancer` by default.
 
 NOTE: In case WAN Replication configuration is not provided in `advancedNetwork` configuration, port number `5710` will be configured for WAN Replication by default.

docs/modules/ROOT/pages/backup-restore.adoc

@@ -254,7 +254,7 @@ To recover a cluster that has Persistence enabled after a cluster-wide restart,
 
 WARNING: The cluster loses all persisted data after a force-start.
 
-WARNING: The cluster loses some persistend data after a partial-start.
+WARNING: The cluster loses some persistent data after a partial-start.
 
 To trigger the cluster recover action set the `startupAction`:
 

docs/modules/ROOT/pages/custom-config.adoc

@@ -85,7 +85,7 @@ spec:
     - name: service3
 ```
 
-The configuration from the Hazelcat CR and the Custom Config will be merged into one structure that will be used as the Hazelcasat member configuration.
+The configuration from the Hazelcast CR and the Custom Config will be merged into one structure that will be used as the Hazelcast member configuration.
 If the same feature is configured with Custom Config `ConfigMap` and in the Hazelcast CR, the configuration from the Hazelcast CR will take precedence and will override the one from the Custom Config.
 
 == Cautions and limitations

docs/modules/ROOT/pages/serialization-configuration.adoc

@@ -5,11 +5,11 @@
 
 With the Hazelcast Platform Operator you can configure Hazelcast Serialization using the Hazelcast CR. To understand the Hazelcast Serialization, refer to xref:hazelcast:serialization:serialization.adoc[Platform documentation].
 
-You can find more detailed information on configuration of Serializartion in xref:api-ref.adoc#serializationconfig[API Reference] page.
+You can find more detailed information on configuration of Serialization in xref:api-ref.adoc#serializationconfig[API Reference] page.
 
 == Configuring Custom Serialization
 
-To register custom serializers, you need to define the list of serizalizers and types in the  `serializers` section. The following configuration will register two custom serializers.
+To register custom serializers, you need to define the list of serializers and types in the  `serializers` section. The following configuration will register two custom serializers.
 
 .Custom serializers example configuration
 [source,yaml,subs="attributes+"]