Grammar improvements.

sokoliva · sokoliva · commit b2b75a7be502 · 2026-03-19T14:08:20.000Z
diff --git a/docs/migrations/v1_0/database/README.md b/docs/migrations/v1_0/database/README.md
@@ -18,5 +18,5 @@ Depending on your application's availability requirements, choose one of the fol
 ## 🏗️ Technical Overview
 
 The v1.0 database migration involves:
-1.  **Schema Updates**: Adding `protocol_version`, `owner`, and `last_updated` columns to the `tasks` table and `protocol_version`, `owner` columns to the `push_notification_configs` table.
+1.  **Schema Updates**: Adding the `protocol_version`, `owner`, and `last_updated` columns to the `tasks` table, and the `protocol_version` and `owner` columns to the `push_notification_configs` table.
 2.  **Storage Model**: Transitioning from Pydantic-based JSON to Protobuf-based JSON serialization for better interoperability and performance.
diff --git a/docs/migrations/v1_0/database/simple_migration.md b/docs/migrations/v1_0/database/simple_migration.md
@@ -40,7 +40,7 @@ uv run a2a-db --database-url "your-database-url"
 
 > [!NOTE]
 >
-> Database stores v1.0 are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.
+> The v1.0 database stores are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.
 
 ### Step 2: Verify the Migration
 
diff --git a/docs/migrations/v1_0/database/zero_downtime.md b/docs/migrations/v1_0/database/zero_downtime.md
@@ -43,7 +43,7 @@ uv run a2a-db --database-url "your-database-url"
 > [!NOTE]
 > All new columns are nullable. Your existing v0.3 code will continue to work normally after this step is completed.
 >
-> Database stores v1.0 are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.
+> The v1.0 database stores are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.
 
 #### ✅ How to Verify
 Confirm the schema is at the correct version:

Original file line number	Diff line number	Diff line change
`@@ -40,7 +40,7 @@ uv run a2a-db --database-url "your-database-url"`
`40`	`40`
`41`	`41`	`> [!NOTE]`
`42`	`42`	`>`
`43`		`-> Database stores v1.0 are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.`
	`43`	`+> The v1.0 database stores are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.`
`44`	`44`
`45`	`45`	`### Step 2: Verify the Migration`
`46`	`46`
Original file line number	Diff line number	Diff line change
`@@ -43,7 +43,7 @@ uv run a2a-db --database-url "your-database-url"`
`43`	`43`	`> [!NOTE]`
`44`	`44`	`> All new columns are nullable. Your existing v0.3 code will continue to work normally after this step is completed.`
`45`	`45`	`>`
`46`		`-> Database stores v1.0 are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.`
	`46`	`+> The v1.0 database stores are designed to be backward compatible by default. After this step, your new v1.0 code will be able to read existing v0.3 entries from the database using a built-in legacy parser.`
`47`	`47`
`48`	`48`	`#### ✅ How to Verify`
`49`	`49`	`Confirm the schema is at the correct version:`