AWS bedrock documentation change
Summary
Minor wording changes: replaced 'leverage' with 'use' and 'utilization' with 'use' in prompt caching feature description
Security assessment
Cosmetic language improvements without security implications. The changes describe cache efficiency benefits without introducing security features or addressing vulnerabilities.
Diff
diff --git a/bedrock/latest/userguide/prompt-caching.md b/bedrock/latest/userguide/prompt-caching.md index 760cc3c69..3fb9a6008 100644 --- a//bedrock/latest/userguide/prompt-caching.md +++ b//bedrock/latest/userguide/prompt-caching.md @@ -11 +11 @@ How it worksSupported models, Regions, and limitsSimplified Cache Management for -Prompt caching is an optional feature that you can use with supported models on Amazon Bedrock to reduce inference response latency and input token costs. By adding portions of your context to a cache, the model can leverage the cache to skip recomputation of inputs, allowing Bedrock to share in the compute savings and lower your response latencies. +Prompt caching is an optional feature that you can use with supported models on Amazon Bedrock to reduce inference response latency and input token costs. By adding portions of your context to a cache, the model can use the cache to skip recomputation of inputs, allowing Bedrock to share in the compute savings and lower your response latencies. @@ -96 +96 @@ The 1-hour cache is best used in the following scenarios: - * When you want to improve your rate limit utilization, since cache hits are not deducted against your rate limit. + * When you want to improve your rate limit use, since cache hits are not deducted against your rate limit.