From b948f51dc779c2c6d78d773638be66dbc8e51c2b Mon Sep 17 00:00:00 2001 From: Sarah Rainsberger Date: Mon, 7 Oct 2024 08:08:39 -0300 Subject: [PATCH] typo fix Co-authored-by: Armand Philippot --- src/content/docs/en/guides/astro-db.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/en/guides/astro-db.mdx b/src/content/docs/en/guides/astro-db.mdx index d70543bcd2d1d..75edc36364df5 100644 --- a/src/content/docs/en/guides/astro-db.mdx +++ b/src/content/docs/en/guides/astro-db.mdx @@ -137,7 +137,7 @@ In development, Astro will use your DB config to generate local types according You will not have access to production data during development unless you [seed from your remote database](#seed-from-your-remote-database). This protects your data while allowing you to test and develop with type-safety using simulated data. -To seed development data for testing and debugging into your Astro project, create a `db/seed.ts` file. Import both the `db` object and any configured table from `astro:db`. Use the `db.insert()` function to provide an array of table row data objects. This development data should match the form of your database schema and prodution data. +To seed development data for testing and debugging into your Astro project, create a `db/seed.ts` file. Import both the `db` object and any configured table from `astro:db`. Use the `db.insert()` function to provide an array of table row data objects. This development data should match the form of your database schema and production data. The following example defines two rows of development data for a `Comment` table: