Changing into unordered bullet point.

Author: Oxyjun

src/content/docs/d1/build-with-d1/import-export-data.mdx

@@ -165,11 +165,11 @@ If you receive an error when trying to import an existing schema and/or dataset
 - If you have foreign key relationships between tables, ensure you are importing the tables in the right order. You cannot refer to a table that does not yet exist.
 - If you receive a `"cannot start a transaction within a transaction"` error, make sure you have removed `BEGIN TRANSACTION` and `COMMIT` from your dumped SQL statements.
 
-### Resolve `Statement too long` error:
+### Resolve `Statement too long` error
 
 If you encounter a `Statement too long` error when trying to import a large SQL file into D1, it means that one of the SQL statements in your file exceeds the maximum allowed length. To resolve this issue, try one of the following approaches:
 
-1. Convert a single large INSERT statement into multiple smaller INSERT statements. For example:
+- Convert a single large INSERT statement into multiple smaller INSERT statements. For example:
 
 ```sql
 INSERT INTO users (id, full_name, created_on)
@@ -180,7 +180,7 @@ VALUES
   ('01GREFXCNF67KV7FPPSEJVJMEW', 'Riane Zamora', '2022-12-24 06:49:04');
 ```
 
-2. Break it into multiple INSERT statements:
+- Break it into multiple INSERT statements:
 
 ```sql
 INSERT INTO users (id, full_name, created_on)
@@ -191,7 +191,7 @@ VALUES
 ('01GREFXCNBYBGX2GC6ZGY9FMP4', 'Hube Bilverstone', '2022-12-15 21:56:13');
 ```
 
-3. If you have a single large INSERT statement with many rows, break it into smaller chunks. For example, instead of inserting 1000 rows in one statement, try splitting that into 250 rows.
+- If you have a single large INSERT statement with many rows, break it into smaller chunks. For example, instead of inserting 1000 rows in one statement, try splitting that into 250 rows.
 
 ## Next Steps