anchor.diff:  Rather, we delegate this responsibility to the maven plugin that is generating the binder based apps. Therefore, you don't
   have to provide a spring.factories file that lists all your configuration classes.
   
  -* Add the new foobar task starter module to the root pom of the repository
  -
  -* At the root of the repository build and install the new module into your local maven cache:
  -
  -`./mvnw clean install -pl :spring-cloud-starter-task-foobar`
  -
  -* You need to add the new starter dependency to the `spring-cloud-task-app-dependencies` bill of material (BOM) in the
  -dependecy management section. For example,
  +* Add the new foobar task starter module to the root pom.xml
  +
  +* You need to add the new starter dependency to a bill of material (BOM) called `foobar-task-app-dependencies` in the
  +dependency management section. For example,
   
   [source,xml]
   ----
  
positive.code: mvn clean install
  ```
  
  For the each of the prebuilt applications, the script will generate the following items:
  
  * `pom.xml` file with the required dependencies
  * a class that contains the `main` method of the application and imports the predefined configuration
  
negative.code: </foobar-task>
  ----
  
  * At this point, you can build the project and generate the apps.
  
  `mvn clean install -PgenerateApps`
  
  This will generate the foobar task app in a directory named `apps` at the root of the project.
  If you want to change the location where the apps are generated, for instance /tmp/task-apps, you can do it in the
  configuration section of the plugin.
  
  