tablespace limitation

Author: ambhatna

articles/mariadb/concepts-limits.md

@@ -148,9 +148,9 @@ The time zone tables can be populated by calling the `mysql.az_load_timezone` st
 
 ### innodb_file_per_table
 
-MariaDB stores the InnoDB table in difference tablespace based on the configuration you provided during the table creation. The [system tablespace](https://mariadb.com/kb/en/innodb-system-tablespaces/) is the storage area for the InnoDB data dictionary. A [file-per-table tablespace](https://mariadb.com/kb/en/innodb-file-per-table-tablespaces/) contains data and indexes for a single InnoDB table, and is stored on the file system in its own data file. This behavior is controlled by the innodb_file_per_table variable. Set `innodb_file_per_table = OFF` causes InnoDB to create tables in the system tablespace, otherwise InnoDB creates tables in file-per-table tablespaces.
+MariaDB stores the InnoDB table in different tablespaces based on the configuration you provided during the table creation. The [system tablespace](https://mariadb.com/kb/en/innodb-system-tablespaces/) is the storage area for the InnoDB data dictionary. A [file-per-table tablespace](https://mariadb.com/kb/en/innodb-file-per-table-tablespaces/) contains data and indexes for a single InnoDB table, and is stored in the file system in its own data file. This behavior is controlled by the `innodb_file_per_table` server parameter. Setting `innodb_file_per_table` to `OFF` causes InnoDB to create tables in the system tablespace. Otherwise, InnoDB creates tables in file-per-table tablespaces.
 
-The Azure Database for MariaDB supports the biggest **1TB** in a single data file. If your database size is bigger than 1TB, you should create the table in [innodb_file_per_table](https://mariadb.com/kb/en/innodb-system-variables/#innodb_file_per_table) tablespace. If you have a single table size larger than 1TB, you should use the partition table.
+Azure Database for MariaDB supports at largest, **1 TB**, in a single data file. If your database size is larger than 1 TB, you should create the table in [innodb_file_per_table](https://mariadb.com/kb/en/innodb-system-variables/#innodb_file_per_table) tablespace. If you have a single table size larger than 1 TB, you should use the partition table.
 
 ## Storage engine support
 

articles/mysql/concepts-limits.md

@@ -151,9 +151,9 @@ The time zone tables can be populated by calling the `mysql.az_load_timezone` st
 
 ### innodb_file_per_table
 
-MySQL stores the InnoDB table in difference tablespace based on the configuration you provided during the table creation. The [system tablespace](https://dev.mysql.com/doc/refman/5.7/en/innodb-system-tablespace.html) is the storage area for the InnoDB data dictionary. A [file-per-table tablespace](https://dev.mysql.com/doc/refman/5.7/en/innodb-file-per-table-tablespaces.html) contains data and indexes for a single InnoDB table, and is stored on the file system in its own data file. This behavior is controlled by the innodb_file_per_table variable. Set `innodb_file_per_table = OFF` causes InnoDB to create tables in the system tablespace, otherwise InnoDB creates tables in file-per-table tablespaces.
+MySQL stores the InnoDB table in different tablespaces based on the configuration you provided during the table creation. The [system tablespace](https://dev.mysql.com/doc/refman/5.7/en/innodb-system-tablespace.html) is the storage area for the InnoDB data dictionary. A [file-per-table tablespace](https://dev.mysql.com/doc/refman/5.7/en/innodb-file-per-table-tablespaces.html) contains data and indexes for a single InnoDB table, and is stored in the file system in its own data file. This behavior is controlled by the `innodb_file_per_table` server parameter. Setting `innodb_file_per_table` to `OFF` causes InnoDB to create tables in the system tablespace. Otherwise, InnoDB creates tables in file-per-table tablespaces.
 
-The Azure Database for MySQL supports the biggest **1TB** in a single data file. If your database size is bigger than 1TB, you should create the table in [innodb_file_per_table](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table) tablespace. If you have a single table size larger than 1TB, you should use the partition table.
+Azure Database for MySQL supports at largest, **1 TB**, in a single data file. If your database size is larger than 1 TB, you should create the table in [innodb_file_per_table](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table) tablespace. If you have a single table size larger than 1 TB, you should use the partition table.
 
 ## Storage engine support