m

framework/aws-kms/aws-kms-hierarchical-keyring.md

@@ -61,6 +61,8 @@ then the settings on the storm tracking cache need to be rational with respect t
 For example, a TTL that is less than the storm tracking grace period will result poor caching behavior.
 This is because all entries would be immediately within the grace period.
 
+For most purposes, the TTL should be much much greater than the grace period.
+
 If the cache to initialize is a [Storm Tracking Cryptographic Materials Cache](../storm-tracking-cryptographic-materials-cache.md#overview)
 then the [Grace Period](../storm-tracking-cryptographic-materials-cache.md#grace-period) MUST be less than the [cache limit TTL](#cache-limit-ttl).
 

framework/storm-tracking-cryptographic-materials-cache.md

@@ -92,13 +92,11 @@ Here are examples of ambiguous or inconsistent settings:
 
 Therefore
 
-- The [Grace Period](#grace-period) MUST be less than or equal to the ttlSeconds.
 - The [Grace Interval](#grace-interval) MUST be less than or equal to the [Grace Period](#grace-period).
 - The [Inflight TTL](#inflight-ttl) MUST be less than or equal to the [Grace Period](#grace-period).
 - The [Grace Interval](#grace-interval) MUST be less than or equal to the [Inflight TTL](#inflight-ttl).
 
-In actual use, the ttlSeconds should be much much larger than the [Grace Period](#grace-period),
-and the [Grace Period](#grace-period) should be several times larger than the [Grace Interval](#grace-interval).
+For most purposes, the [Grace Period](#grace-period) should be several times larger than the [Grace Interval](#grace-interval).
 
 ## Behaviors