anchor.diff:  * `bin/rails db:migrate`
   * `bin/rails db:seed`
   
  -Mind that if everything went well you shouldn't need to run this commands manually.
  +Mind that if everything went well you shouldn't need to run these commands manually.
   ====
   
  -If the default database.yml does not suit your needs you can always configure it at your will and run these steps manually.
  +If the default database.yml does not suit your needs you can always configure it at your will and run these steps manually, although
  +we recommend that you make the database configurations with environment variables (ENV VARs) so it's easy for you to regenerate the database. 
   
   The last command will set your database and add some example data (called "seed data") so that you can start trying Decidim.
   We don't recommend using seed data for production environments, but it's useful for local development and staging environments.
  
positive.code: app (that you can create with `decidim app_name`) but with a Gemfile pre-configured for local development and some other small config modifications.
  
  We recommend that you first have a xref:install:manual.adoc[working Decidim app] so that you have fullfilled all the necessary
  system and services requirements, like having a working Ruby installation, PostgreSQL, Node.JS, etc. For better following this
  guide and as you should be working in a development environment (ie without sensitive data in your database), for better comfort
  you can configure PostgreSQL with a relaxed security. See more information about this in the <<database,Database>> section of this page.
  
  You need it in order to have a Rails application configured to lookup Decidim modules from your filesystem. This way changes
  in your modules will be directly observed by this `development_app`.
  
  You can create a `development_app` from inside the project's root folder with the command:
  
  [source,console]
  ----
  
negative.code: 
  [source,console]
  ----
  bin/rake development_app
  ----
  