diff --git a/docs/en/00_Getting_Started/00_Server_Requirements.md b/docs/en/00_Getting_Started/00_Server_Requirements.md
index 623490271..9b4e95b34 100644
--- a/docs/en/00_Getting_Started/00_Server_Requirements.md
+++ b/docs/en/00_Getting_Started/00_Server_Requirements.md
@@ -59,7 +59,7 @@ see `MySQLDatabase::$sql_mode` for more details.) This setting is only available
  ### MySQL/MariaDB Int width in schema
 
 MySQL 8.0.17 stopped reporting the width attribute for integers while MariaDB did not change its behaviour.
-This results in constant rebuilding the schema when MySQLSchemaManager expects a field to look like i.e.
+This results in constant rebuilding of the schema when MySQLSchemaManager expects a field to look like e.g.
 `INT(8)` and MySQL server reports it simply as `INT`. MySQLSchemaManager has been updated to detect the MySQL
 server implementation and act accordingly. In cases when auto-detection fails, you can force the desired behaviour like this:
 ```yml
diff --git a/docs/en/04_Changelogs/4.9.0.md b/docs/en/04_Changelogs/4.9.0.md
index 1c96dc46c..2f0fb5474 100644
--- a/docs/en/04_Changelogs/4.9.0.md
+++ b/docs/en/04_Changelogs/4.9.0.md
@@ -251,7 +251,7 @@ It's highly recommended that existing Silverstripe CMS installation using `Swift
 
 ### MySQL/MariaDB Int width in schema
 MySQL 8.0.17 stopped reporting the width attribute for integers while MariaDB did not change its behaviour. 
-This results in constant rebuilding the schema when MySQLSchemaManager expects a field to look like i.e. 
+This results in constant rebuilding of the schema when MySQLSchemaManager expects a field to look like e.g. 
 `INT(8)` and MySQL server reports it simply as `INT`. MySQLSchemaManager has been updated to detect the MySQL
 server implementation and act accordingly. In cases when auto-detection fails, you can force the desired behaviour like this:
 ```yml