From 0a3dbfa43e2c029d65a2df234775d3d133a4277b Mon Sep 17 00:00:00 2001 From: Jeff Date: Tue, 4 Dec 2018 14:36:12 +0100 Subject: [PATCH] Fix RedisOperationsSessionRepository javadoc typos Resolves: #1275 --- .../session/data/redis/RedisOperationsSessionRepository.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-session-data-redis/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java b/spring-session-data-redis/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java index 28aecd1a..042813b9 100644 --- a/spring-session-data-redis/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java +++ b/spring-session-data-redis/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java @@ -202,7 +202,7 @@ import org.springframework.util.Assert; * *

* One problem with relying on Redis expiration exclusively is that Redis makes no - * guarantee of when the expired event will be fired if they key has not been accessed. + * guarantee of when the expired event will be fired if the key has not been accessed. * Specifically the background task that Redis uses to clean up expired keys is a low * priority task and may not trigger the key expiration. For additional details see * Timing of expired events section in @@ -213,7 +213,7 @@ import org.springframework.util.Assert; * To circumvent the fact that expired events are not guaranteed to happen we can ensure * that each key is accessed when it is expected to expire. This means that if the TTL is * expired on the key, Redis will remove the key and fire the expired event when we try to - * access they key. + * access the key. *

* *