From 7ea988e4b9bfd9012af2ea1b09affaba601596cb Mon Sep 17 00:00:00 2001 From: Jack Green Date: Mon, 2 Oct 2023 14:30:12 +0100 Subject: [PATCH] Fix typos identified by IntelliJ (#137) --- README.adoc | 2 +- antora-playbook.yml | 2 +- check-links-playbook.yml | 2 +- docs/modules/ROOT/pages/advanced-networking.adoc | 4 ++-- docs/modules/ROOT/pages/backup-restore.adoc | 2 +- docs/modules/ROOT/pages/custom-config.adoc | 2 +- docs/modules/ROOT/pages/serialization-configuration.adoc | 4 ++-- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/README.adoc b/README.adoc index e5777b5d..7e159f95 100644 --- a/README.adoc +++ b/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/`) from the release branch. +. When you are ready to release, create a maintenance branch (`v/`) 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/antora-playbook.yml b/antora-playbook.yml index 0dcc82c5..e7863b08 100644 --- a/antora-playbook.yml +++ b/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 diff --git a/check-links-playbook.yml b/check-links-playbook.yml index 54293ab4..480c5181 100644 --- a/check-links-playbook.yml +++ b/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 diff --git a/docs/modules/ROOT/pages/advanced-networking.adoc b/docs/modules/ROOT/pages/advanced-networking.adoc index 8a7730f8..95f62d43 100644 --- a/docs/modules/ROOT/pages/advanced-networking.adoc +++ b/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. \ No newline at end of file diff --git a/docs/modules/ROOT/pages/backup-restore.adoc b/docs/modules/ROOT/pages/backup-restore.adoc index 9a4e0bd3..bd8002cf 100644 --- a/docs/modules/ROOT/pages/backup-restore.adoc +++ b/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`: diff --git a/docs/modules/ROOT/pages/custom-config.adoc b/docs/modules/ROOT/pages/custom-config.adoc index 369bd9b8..b3047210 100644 --- a/docs/modules/ROOT/pages/custom-config.adoc +++ b/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 diff --git a/docs/modules/ROOT/pages/serialization-configuration.adoc b/docs/modules/ROOT/pages/serialization-configuration.adoc index 6b85a040..7b2aef2d 100644 --- a/docs/modules/ROOT/pages/serialization-configuration.adoc +++ b/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+"]