diff --git a/src/main/resources/generator/server/springboot/dbmigration/cassandra/README.md b/src/main/resources/generator/server/springboot/dbmigration/cassandra/README.md
index 845e41140b1..8a79ce4e128 100644
--- a/src/main/resources/generator/server/springboot/dbmigration/cassandra/README.md
+++ b/src/main/resources/generator/server/springboot/dbmigration/cassandra/README.md
@@ -12,5 +12,5 @@ Changelog scripts MUST tell explicitly which keyspace is used:
 - by using `USE myKeyspace;` directive at the beginning of a script
 - or by prepending each table with the keyspace it belongs to: `CREATE TABLE IF NOT EXISTS myKeyspace.myTable`
 
-Second approach is recommended: it allows to not switch keyspace at runtime if there's many of them.
+Second approach is recommended: it allows to not switch keyspace at runtime if there are many of them.
 See [warn-if-set-keyspace section](https://docs.datastax.com/en/developer/java-driver/latest/manual/core/configuration/reference/) for more info.
diff --git a/src/main/resources/generator/server/springboot/dbmigration/cassandra/cassandra-migration.md b/src/main/resources/generator/server/springboot/dbmigration/cassandra/cassandra-migration.md
index d05afb68c82..a7c67f9a2ee 100644
--- a/src/main/resources/generator/server/springboot/dbmigration/cassandra/cassandra-migration.md
+++ b/src/main/resources/generator/server/springboot/dbmigration/cassandra/cassandra-migration.md
@@ -7,7 +7,7 @@ Similar to Liquibase, JHipster Lite provides a tool to apply your CQL migration
 - The tool is not run by the application itself when it is started but inside a Docker container or manually
 - All CQL scripts must follow the pattern `{timestamp}_{description}.cql` and be placed in the changelog directory: `src/main/resources/config/cql/changelog/`
 - All non already applied scripts located in the changelog directory are applied in alphabetical order (ie: following the timestamp)
-- Because Cassandra is not a transactional database, if an error happen before inserting the metadata in the table used by the tool there is a risk to have your CQL migration script run multiple times
+- Because Cassandra is not a transactional database, if an error happens before inserting the metadata in the table used by the tool there is a risk to have your CQL migration script run multiple times
 
 Some information on the tool: