AWS bedrock-agentcore documentation change
Summary
Changed straight apostrophe to curly apostrophe in 'OAuth 2.0's' for typographical consistency
Security assessment
This is a typographical change only (straight apostrophe to curly apostrophe). The security content about OAuth 2.0 scope-based security model and token vault security measures remains unchanged. No security implications.
Diff
diff --git a/bedrock-agentcore/latest/devguide/key-features-and-benefits.md b/bedrock-agentcore/latest/devguide/key-features-and-benefits.md index 16cb1e2ba..ceafb8a42 100644 --- a//bedrock-agentcore/latest/devguide/key-features-and-benefits.md +++ b//bedrock-agentcore/latest/devguide/key-features-and-benefits.md @@ -38 +38 @@ The token vault provides security for storing OAuth 2.0 tokens, OAuth client cre -Building on OAuth 2.0's scope-based security model, the token vault implements additional security measures where every access request is validated independently, even from callers within the same trust domain. This extra security mechanism is necessary to protect end-user data from malicious or misbehaving agent code. The vault securely stores OAuth 2.0 tokens, reducing security risks while improving your overall security posture. +Building on OAuth 2.0’s scope-based security model, the token vault implements additional security measures where every access request is validated independently, even from callers within the same trust domain. This extra security mechanism is necessary to protect end-user data from malicious or misbehaving agent code. The vault securely stores OAuth 2.0 tokens, reducing security risks while improving your overall security posture.