From ead97bba855b3342b153b3d83b320e68cd242893 Mon Sep 17 00:00:00 2001 From: Andrii Hrytsiuk Date: Mon, 6 Nov 2023 18:04:27 +0100 Subject: [PATCH] Fix some typos in docs * Replaced phrase 'String with version' to 'Starting with version' * Fixed formatting for code block --- .../antora/modules/ROOT/pages/jdbc/lock-registry.adoc | 6 +++--- src/reference/antora/modules/ROOT/pages/redis.adoc | 6 +++--- src/reference/antora/modules/ROOT/pages/zookeeper.adoc | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/reference/antora/modules/ROOT/pages/jdbc/lock-registry.adoc b/src/reference/antora/modules/ROOT/pages/jdbc/lock-registry.adoc index 7fe82b337e..1147b5263f 100644 --- a/src/reference/antora/modules/ROOT/pages/jdbc/lock-registry.adoc +++ b/src/reference/antora/modules/ROOT/pages/jdbc/lock-registry.adoc @@ -43,12 +43,12 @@ So the time to live can be highly reduce and deployments can retake a lost lock NOTE: The lock renewal can be done only if the lock is held by the current thread. -String with version 5.5.6, the `JdbcLockRegistry` is support automatically clean up cache for JdbcLock in `JdbcLockRegistry.locks` via `JdbcLockRegistry.setCacheCapacity()`. +Starting with version 5.5.6, the `JdbcLockRegistry` is support automatically clean up cache for JdbcLock in `JdbcLockRegistry.locks` via `JdbcLockRegistry.setCacheCapacity()`. See its JavaDocs for more information. -String with version 6.0, the `DefaultLockRepository` can be supplied with a `PlatformTransactionManager` instead of relying on the primary bean from the application context. +Starting with version 6.0, the `DefaultLockRepository` can be supplied with a `PlatformTransactionManager` instead of relying on the primary bean from the application context. -String with version 6.1, the `DefaultLockRepository` can be configured for custom `insert`, `update` and `renew` queries. +Starting with version 6.1, the `DefaultLockRepository` can be configured for custom `insert`, `update` and `renew` queries. For this purpose the respective setters and getters are exposed. For example, an insert query for PostgreSQL hint can be configured like this: diff --git a/src/reference/antora/modules/ROOT/pages/redis.adoc b/src/reference/antora/modules/ROOT/pages/redis.adoc index 45a708df41..251d27026e 100644 --- a/src/reference/antora/modules/ROOT/pages/redis.adoc +++ b/src/reference/antora/modules/ROOT/pages/redis.adoc @@ -643,7 +643,7 @@ For more information about commands, their arguments and result type, see https: == Redis Queue Outbound Gateway Spring Integration introduced the Redis queue outbound gateway to perform request and reply scenarios. -It pushes a conversation `UUID` to the provided `queue`, pushes the value with that `UUID` as its key to a Redis list, and waits for the reply from a Redis list with a key of `UUID' plus '.reply`. +It pushes a conversation `UUID` to the provided `queue`, pushes the value with that `UUID` as its key to a Redis list, and waits for the reply from a Redis list with a key of `UUID` plus `.reply`. A different UUID is used for each interaction. The following listing shows the available attributes for a Redis outbound gateway: @@ -844,10 +844,10 @@ You should set the expiry at a large enough value to prevent this condition, but Starting with version 5.0, the `RedisLockRegistry` implements `ExpirableLockRegistry`, which removes locks last acquired more than `age` ago and that are not currently locked. -String with version 5.5.6, the `RedisLockRegistry` is support automatically clean up cache for redisLocks in `RedisLockRegistry.locks` via `RedisLockRegistry.setCacheCapacity()`. +Starting with version 5.5.6, the `RedisLockRegistry` is support automatically clean up cache for redisLocks in `RedisLockRegistry.locks` via `RedisLockRegistry.setCacheCapacity()`. See its JavaDocs for more information. -String with version 5.5.13, the `RedisLockRegistry` exposes a `setRedisLockType(RedisLockType)` option to determine in which mode a Redis lock acquisition should happen: +Starting with version 5.5.13, the `RedisLockRegistry` exposes a `setRedisLockType(RedisLockType)` option to determine in which mode a Redis lock acquisition should happen: - `RedisLockType.SPIN_LOCK` - the lock is acquired by periodic loop (100ms) checking whether the lock can be acquired. Default. diff --git a/src/reference/antora/modules/ROOT/pages/zookeeper.adoc b/src/reference/antora/modules/ROOT/pages/zookeeper.adoc index 5eb93a9e18..3e0fc23716 100644 --- a/src/reference/antora/modules/ROOT/pages/zookeeper.adoc +++ b/src/reference/antora/modules/ROOT/pages/zookeeper.adoc @@ -81,7 +81,7 @@ public interface KeyToPathStrategy { If the strategy returns `true` from `isBounded`, unused locks do not need to be harvested. For unbounded strategies (such as the default), you need to periodically invoke `expireUnusedOlderThan(long age)` to remove old unused locks from memory. -String with version 5.5.6, the `ZookeeperLockRegistry` is support automatically clean up cache for ZkLock in `ZookeeperLockRegistry.locks` via `ZookeeperLockRegistry.setCacheCapacity()`. +Starting with version 5.5.6, the `ZookeeperLockRegistry` is support automatically clean up cache for ZkLock in `ZookeeperLockRegistry.locks` via `ZookeeperLockRegistry.setCacheCapacity()`. See its JavaDocs for more information. [[zk-leadership]]