Fix spelling

.github/wordlist.txt

@@ -80,3 +80,173 @@ DnsResolver
 dnsResolver
 evalReadOnly
 gg
+ACL
+AOT
+APIs
+API’s
+Akka
+Async
+AsyncCommand
+Asynchronicity
+Backpressure
+CamelCase
+Charset
+ClientResources
+CommandLatencyCollector
+CommandWrapper
+CompletionStage
+Config
+Coroutine
+Coroutines
+Customizer
+DNS
+DSL
+EPoll
+ElastiCache
+EventExecutorGroup
+EventLoop
+EventLoopGroup
+EventPublisher
+Failover
+GZIP
+Graal
+GraalVM
+Graal’s
+HdrHistogram
+IP’s
+Iterable
+JDK
+JFR
+JIT
+JNI
+KeyStreamingChannel
+KeyValueStreamingChannel
+Kops
+Kqueue
+Kryo
+LatencyUtils
+Luascripts
+MasterReplica
+Misconfiguring
+Mult
+NIO
+Netty’s
+NodeSelection
+OpenSSL
+PEM
+POSIX
+Plaintext
+RTT
+Reconnection
+RedisClient
+RedisClusterClient
+RedisURIs
+RxJava
+SHA
+SPI
+ScoredValueStreamingChannel
+Serializer
+Sharded
+Sharding
+SomeClient
+StartTLS
+StreamingChannel
+StreamingChannels
+SubstrateVM
+TCP
+TLS
+TimedScheduler
+TransactionalCommand
+URIs
+Un
+ValueStreamingChannel
+aggregable
+amongst
+analytics
+args
+assignability
+async
+asynchronicity
+backoff
+backpressure
+boolean
+broadcasted
+bytecode
+cancelation
+channelId
+charset
+classpath
+codecs
+config
+coroutines
+customizable
+customizer
+dataset
+deserialization
+desynchronize
+desynchronizes
+encodings
+epId
+epoll
+executables
+extensibility
+failover
+fromExecutor
+gradle
+hasNext
+hostnames
+idempotency
+integrations
+interoperable
+interoperate
+invoker
+json
+keyspace
+kotlinx
+kqueue
+latencies
+lifecycle
+localhost
+macOS
+microservices
+misconfiguration
+multithreaded
+natively
+netty’s
+newSingle
+nodeId
+nodeIds
+nodeId’s
+nullability
+onCompleted
+onError
+onNext
+oss
+parametrized
+pipelining
+pluggable
+pre
+preconfigured
+predefine
+reconnection
+redirections
+replicaN
+retrigger
+runtimes
+se
+sharding
+stateful
+subclasses
+subcommand
+synthetization
+th
+throwable
+topologies
+transcoding
+typesafe
+un
+unconfigured
+unix
+uring
+whitespace
+xml

docs/advanced-usage.md

@@ -349,7 +349,7 @@ canceled when a reconnect fails within the activation sequence. The
 reconnect itself has two phases: Socket connection and
 protocol/connection activation. In case a connect timeout occurs, a
 connection reset, host lookup fails, this does not affect the
-cancelation of commands. In contrast, where the protocol/connection
+cancellation of commands. In contrast, where the protocol/connection
 activation fails due to SSL errors or PING before activating connection
 failure, queued commands are canceled.</p></td>
 </tr>
@@ -811,7 +811,7 @@ Netty provides three platform-specific JNI transports:
 
 - io_uring on Linux (Incubator)
 
-- kqueue on MacOS/BSD
+- kqueue on macOS/BSD
 
 Lettuce defaults to native transports if the appropriate library is
 available within its runtime. Using a native transport adds features
@@ -850,7 +850,7 @@ Native transports are available with:
   </dependency>
   ```
 
-- MacOS **kqueue** x86_64 systems with a minimum netty version of
+- macOS **kqueue** x86_64 systems with a minimum netty version of
   `4.1.11.Final`, requiring `netty-transport-native-kqueue`, classifier
   `osx-x86_64`
 
@@ -2162,7 +2162,7 @@ Those cover Lettuce operations for `RedisClient` and
 `RedisClusterClient`.
 
 Depending on your configuration you might need additional configuration
-for Netty, HdrHistorgram (metrics collection), Reactive Libraries, and
+for Netty, HdrHistogram (metrics collection), Reactive Libraries, and
 dynamic Redis Command interfaces.
 
 ### HdrHistogram/Command Latency Metrics
@@ -2526,7 +2526,7 @@ already executed; only the result is not available. These errors are
 caused mostly due to a wrong implementation. The result of a command,
 which cannot be *decoded* is that the command gets canceled, and the
 causing `Exception` is available in the result. The command is cleared
-from the response queue, and the connection stays useable.
+from the response queue, and the connection stays usable.
 
 In general, when `Errors` occur while operating on a connection, you
 should close the connection and use a new one. Connections, that

docs/redis-command-interfaces.md

@@ -199,7 +199,7 @@ interface MixedCommands extends Commands {
 }
 ```
 
-You can choose amongst multiple strategies:
+You can choose among multiple strategies:
 
 - `SPLIT`: Splits camel-case method names into multiple command
   segments: `clientSetname` executes `CLIENT SETNAME`. This is the
@@ -329,7 +329,7 @@ Built-in parameter types:
 - types implementing `io.lettuce.core.CompositeParameter` - Lettuce
   comes with a set of command argument types such as `BitFieldArgs`,
   `SetArgs`, `SortArgs`, … that can be used as parameter. Providing
-  `CompositeParameter` will ontribute multiple command arguments by
+  `CompositeParameter` will contribute multiple command arguments by
   invoking the `CompositeParameter.build(CommandArgs)` method.
 
 - `Value`, `KeyValue`, and `ScoredValue` that are encoded to their
@@ -386,7 +386,7 @@ Another aspect of command methods is their response type. Redis command
 responses consist of simple strings, bulk strings (byte streams) or
 arrays with nested elements depending on the issued command.
 
-You can choose amongst various return types that map to a particular
+You can choose among various return types that map to a particular
 {custom-commands-command-output-link}. A command output can return
 either its return type directly (`List<String>` for `StringListOutput`)
 or stream individual elements (`String` for `StringListOutput` as it