AWS bedrock-agentcore documentation change
Summary
Updated typographical apostrophes from straight to curly quotes in three places for consistency.
Security assessment
The changes are purely typographical (straight apostrophes to curly apostrophes) with no functional or security implications. No security vulnerabilities, weaknesses, or incidents are addressed.
Diff
diff --git a/bedrock-agentcore/latest/devguide/agents-tools-runtime.md b/bedrock-agentcore/latest/devguide/agents-tools-runtime.md index 3c389466f..a529707ac 100644 --- a//bedrock-agentcore/latest/devguide/agents-tools-runtime.md +++ b//bedrock-agentcore/latest/devguide/agents-tools-runtime.md @@ -12 +12 @@ Framework agnostic -AgentCore Runtime lets you transform any local agent code to cloud-native deployments with a few lines of code no matter the underlying framework. Works seamlessly with popular frameworks like LangGraph, Strands, and CrewAI. You can also leverage it with custom agents that don't use a specific framework. +AgentCore Runtime lets you transform any local agent code to cloud-native deployments with a few lines of code no matter the underlying framework. Works seamlessly with popular frameworks like LangGraph, Strands, and CrewAI. You can also leverage it with custom agents that don’t use a specific framework. @@ -37 +37 @@ Persistent filesystems -Runtime supports persisting filesystem state across session stop/resume cycles. The agent's files, installed packages, and build artifacts can survive session stops without external storage. +Runtime supports persisting filesystem state across session stop/resume cycles. The agent’s files, installed packages, and build artifacts can survive session stops without external storage. @@ -42 +42 @@ Consumption-based pricing model -Runtime implements consumption-based pricing that charges only for resources actually consumed. Unlike allocation-based models that require pre-selecting resources, Runtime dynamically provisions what's needed without requiring right-sizing. The service aligns CPU billing with actual active processing - typically eliminating charges during I/O wait periods when agents are primarily waiting for LLM responses - while continuously maintaining your session state. +Runtime implements consumption-based pricing that charges only for resources actually consumed. Unlike allocation-based models that require pre-selecting resources, Runtime dynamically provisions what’s needed without requiring right-sizing. The service aligns CPU billing with actual active processing - typically eliminating charges during I/O wait periods when agents are primarily waiting for LLM responses - while continuously maintaining your session state.