update build documentation page
@@ -43,10 +43,10 @@ See [Dump and restore](database/dump_and_restore.md) for details on how to impor
## Setting up maven profiles
Waltz uses maven profiles to target the build against the correct database. Generic db vendor settings are located in
-the profiles section of `<REPO>/waltz-schema/pom.xml` and should not need to be changed.
+the profiles section of `<REPO>/pom.xml` and should not need to be changed.
Specific database connection details should be configured in the
-`~/.m2/settings.xml` file. An example (for both MariaDB and Microsoft
+`~/.m2/settings.xml` file. An example (for both PostreSQL and Microsoft
SQL Server) would look like:
```xml
@@ -85,7 +85,7 @@ SQL Server) would look like:
Typically one of two maven targets is executed. For the first run (and whenever schema updates are required) then a full `package` build should be executed. For code only change then the quicker `compile` target can be used.
-When running either variant you must provide the names of two profiles, firstly the generic database profile (either `waltz-mariadb` or `waltz-mssql`) and the specific profile created in your `~.m2/settings.xml` file (in the example above either `dev-maria` or `dev-mssql`).
+When running either variant you must provide the names of two profiles, firstly the generic database profile (either `waltz-postgres` or `waltz-mssql`) and the specific profile created in your `~/.m2/settings.xml` file (in the example above either `dev-postgres` or `dev-mssql`).
### Examples (using aliases)
