Make migration guide intro more coherent

Max-AR · Feb 14, 2020 · f9f06d5 · f9f06d5
1 parent b033351
commit f9f06d5
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/docs/manual/working/scalaGuide/main/sql/slick/PlaySlickMigrationGuide.md b/docs/manual/working/scalaGuide/main/sql/slick/PlaySlickMigrationGuide.md
@@ -1,8 +1,8 @@
 # Play Slick Migration Guide
 
-This is a guide for migrating from Play Slick v0.8 to v1.0, v1.1 or v2.0.0.
+This is a guide for migrating from Play Slick to a version that supports the new Slick 3.0 APIs.
 
-It assumes you have already migrated your project to use Play 2.5 (see [Play 2.5 Migration Guide](https://www.playframework.com/documentation/2.5.x/Migration25)), that you have read the [Slick 3.1 documentation](https://scala-slick.org/docs/), and are ready to migrate your Play application to use the new Slick Database I/O Actions API.
+It assumes you have already migrated your project to use Play 2.5 (see [Play 2.5 Migration Guide](https://www.playframework.com/documentation/2.5.x/Migration25)), that you have read the [Slick documentation](https://scala-slick.org/docs/), and are ready to migrate your Play application to use the new Slick Database I/O Actions API.
 
 ## Build changes
 
@@ -24,7 +24,7 @@ While, if you are not using evolutions, you can now safely remove `evolutionplug
 
 ## Database configuration
 
-With the past releases of Slick Play (which used Slick 2.1 or earlier), you used to configure Slick datasources exactly like you would configure Play JDBC datasources. This is no longer the case, and the following configuration will now be **ignored** by Play Slick:
+With the past releases of Play Slick  (which used Slick 2.1 or earlier), you used to configure Slick datasources exactly like you would configure Play JDBC datasources. This is no longer the case, and the following configuration will now be **ignored** by Play Slick:
 
 ```conf
 db.default.driver=org.h2.Driver
@@ -38,7 +38,7 @@ There are several reasons for this change. First, the above is not a valid Slick
 Here is how you would need to migrate the above configuration:
 
 ```conf
-slick.dbs.default.driver="slick.driver.H2Driver$" # You must provide the required Slick driver! 
+slick.dbs.default.profile="slick.jdbc.H2Profile$" # You must provide the required Slick profile! 
 slick.dbs.default.db.driver=org.h2.Driver
 slick.dbs.default.db.url="jdbc:h2:mem:play"
 slick.dbs.default.db.user=sa