From d4e6c3829c5294ffa19b1a3021ea9c545208dc12 Mon Sep 17 00:00:00 2001 From: Naumenko Boris Date: Thu, 15 May 2025 19:52:08 +0300 Subject: [PATCH] Fix typos in README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 4951cf7e5..85a26de0c 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ npm run start -- rinkeby ## Schema Migrations Migrations are managed via knex and behave similarly to ActiveRecord -migrations. As you add migrations, knex tracks the currect applied state in the +migrations. As you add migrations, knex tracks the correct, current applied state in the database, and allows you to apply new migrations as they come in. See: [http://knexjs.org/#Migrations-CLI] @@ -84,7 +84,7 @@ See: [http://knexjs.org/#Migrations-CLI] ### Creating Migrations New migrations are in typescript and are store in: ```src/migrations/``` -To use the knex tool to generate a migration in this directly, use the *development* enironment: +To use the knex tool to generate a migration in this directly, use the *development* environment: ``` knex migrate:make -x ts --env development name @@ -99,7 +99,7 @@ knex migrate:latest --env build ## Data Seeds Seed files are used to seed the *test* database. Unlike migrations, seeds are -meant only for boostrapping, and so each time seeds are run all the source +meant only for bootstrapping, and so each time seeds are run all the source files are executed (not just newly added ones). Currently the seeds files drop and re-create the tables with each application.