From 38431cf3e0164c7701707cdd2fa5af871d01e493 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20Furga=C5=82a?=
 <83299832+00200200@users.noreply.github.com>
Date: Mon, 14 Sep 2026 15:06:35 +0200
Subject: [PATCH] docs: fix session guide subject-verb agreement

---
 docs/sessions/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/sessions/index.md b/docs/sessions/index.md
index 10fd1dd264..b5c81ed02b 100644
--- a/docs/sessions/index.md
+++ b/docs/sessions/index.md
@@ -2,7 +2,7 @@
 
 The Agents SDK provides built-in session memory to automatically maintain conversation history across multiple agent runs, eliminating the need to manually handle `.to_input_list()` between turns.
 
-Sessions stores conversation history for a specific session, allowing agents to maintain context without requiring explicit manual memory management. This is particularly useful for building chat applications or multi-turn conversations where you want the agent to remember previous interactions.
+Sessions store conversation history for a specific session, allowing agents to maintain context without requiring explicit manual memory management. This is particularly useful for building chat applications or multi-turn conversations where you want the agent to remember previous interactions.
 
 Use sessions when you want the SDK to manage client-side memory for you. In the same run, a session cannot be combined with the run-level continuation options `conversation_id`, `previous_response_id`, or `auto_previous_response_id`. If you want OpenAI server-managed continuation instead, choose one of those mechanisms rather than layering a session on top.
 
@@ -136,7 +136,7 @@ If your session implementation exposes default session settings, each non-`None`
 
 ### Basic operations
 
-Sessions supports several operations for managing conversation history:
+Sessions support several operations for managing conversation history:
 
 ```python
 from agents import SQLiteSession