Another attempt to fix spelling

.github/wordlist.txt

@@ -111,9 +111,9 @@ Failover
 GZIP
 Graal
 GraalVM
-Graal’s
+Graal's
 HdrHistogram
-IP’s
+IPs
 Iterable
 JDK
 JFR
@@ -193,6 +193,7 @@ extensibility
 failover
 fromExecutor
 gradle
+Graal's
 hasNext
 hostnames
 idempotency
@@ -212,11 +213,11 @@ microservices
 misconfiguration
 multithreaded
 natively
-netty’s
+netty's
 newSingle
 nodeId
 nodeIds
-nodeId’s
+nodeId's
 nullability
 onCompleted
 onError

docs/advanced-usage.md

@@ -219,7 +219,7 @@ configure a different DNS resolver. Lettuce comes with
 or custom DNS servers without caching of results so each hostname lookup
 yields in a DNS lookup.</p>
 <p>Since 4.4: Defaults to <code>DnsResolvers.UNRESOLVED</code> to use
-netty’s <code>AddressResolver</code> that resolves DNS names on
+netty's <code>AddressResolver</code> that resolves DNS names on
 <code>Bootstrap.connect()</code> (requires netty 4.1)</p></td>
 </tr>
 <tr>
@@ -674,7 +674,7 @@ output.</p>
 obstruction:</p>
 <p><code>MOVED</code>/<code>ASK</code> redirection but the cluster
 topology view is stale Connecting to cluster nodes using different
-IP’s/hostnames (e.g. private/public IP’s)</p>
+IPs/hostnames (e.g. private/public IPs)</p>
 <p>Connecting to non-cluster members to reconfigure those while using
 the RedisClusterClient connection.</p></td>
 </tr>
@@ -2137,7 +2137,7 @@ less total CPU usage.
 ### Building Native Images
 
 Native images assume a closed world principle in which all code needs to
-be known at the time the native image is built. Graal’s SubstrateVM
+be known at the time the native image is built. Graal's SubstrateVM
 analyzes class files during native image build-time to determine what
 bytecode needs to be translated into a native image. While this task can
 be achieved to a good extent by analyzing static bytecode, it’s harder

docs/integration-extension.md

@@ -77,7 +77,7 @@ underlying bytes. The `byte[]` interface of Lettuce 3.x required the
 user to provide an array with the exact data for interchange. So if you
 have an array where you want to use only a subset, you’re required to
 create a new instance of a byte array and copy the data. The same
-applies if you have a different byte source (e.g. netty’s `ByteBuf` or
+applies if you have a different byte source (e.g. netty's `ByteBuf` or
 an NIO `ByteBuffer`). The `ByteBuffer`s for decoding are pointers to the
 underlying data. `ByteBuffer`s for encoding data can be either pure
 pointers or allocated memory. Lettuce does not free any memory (such as

docs/new-features.md

@@ -45,7 +45,7 @@
 - Configuration of extended Keep-Alive options through
   `KeepAliveOptions` (only available for some transports/Java versions).
 
-- Configuration of netty’s `AddressResolverGroup` through
+- Configuration of netty's `AddressResolverGroup` through
   `ClientResources`. Uses `DnsAddressResolverGroup` when
   `netty-resolver-dns` is on the classpath.
 

docs/user-guide/pubsub.md

@@ -4,7 +4,7 @@ Lettuce provides support for Publish/Subscribe on Redis Standalone and
 Redis Cluster connections. The connection is notified on
 message/subscribed/unsubscribed events after subscribing to channels or
 patterns. [Synchronous](connecting-redis.md#basic-usage), [asynchronous](async-api.md)
-and [reactive](reactive-api.md) API’s are provided to interact with Redis
+and [reactive](reactive-api.md) APIs are provided to interact with Redis
 Publish/Subscribe features.
 
 ### Subscribing