reorder content

prisma · Oct 31, 2023 · 037469d · 037469d
1 parent 54568b6
commit 037469d
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/content/300-guides/050-database/900-turso.mdx b/content/300-guides/050-database/900-turso.mdx
@@ -27,11 +27,6 @@ Many aspects of using Prisma with Turso are just like using Prisma with any othe
 
 ## Differences to consider
 
-There are a number of differences between Turso and SQLite to consider. You should be aware of the following when deciding to use Turso and Prisma:
-
-- **Remote and embedded SQLite databases**. libSQL uses HTTP to connect to the remote SQLite database. libSQL also supports remote database replicas and embedded replicas. Embedded replicas enable you to replicate your primary database inside your application.
-- **Making schema changes**. Since libSQL uses HTTP to connect to the remote database, this makes it incompatible with Prisma Migrate. However, you can use [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) <span class="api"></span> to create a schema migration and then apply the changes to your database using [Turso's CLI](https://docs.turso.tech/reference/turso-cli).
-
 libSQL is 100% compatible with SQLite. libSQL extends SQLite with the following features and capabilities:
 
 - Support for replication
@@ -42,6 +37,11 @@ libSQL is 100% compatible with SQLite. libSQL extends SQLite with the following
 
 To learn more about the differences between libSQL and how it is different from SQLite, see [libSQL Manifesto](https://turso.tech/libsql-manifesto).
 
+There are a number of differences between Turso and SQLite to consider. You should be aware of the following when deciding to use Turso and Prisma:
+
+- **Remote and embedded SQLite databases**. libSQL uses HTTP to connect to the remote SQLite database. libSQL also supports remote database replicas and embedded replicas. Embedded replicas enable you to replicate your primary database inside your application.
+- **Making schema changes**. Since libSQL uses HTTP to connect to the remote database, this makes it incompatible with Prisma Migrate. However, you can use [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) <span class="api"></span> to create a schema migration and then apply the changes to your database using [Turso's CLI](https://docs.turso.tech/reference/turso-cli).
+
 ## Connect and query your primary database
 
 1. Create a database on Turso if you don't have one already: