Make ESLint involvement more clear

ESLint is only part of the application frontend and only invoked implicitly during build time

app/README.md

@@ -9,7 +9,7 @@ The application consists of two parts:
 * frontend (`./client`)
 * backend (`./server`)
 
-and utilizes the following technologies (a.k.a MERN-stack):
+and utilizes the following technologies (aka. MERN-stack):
 
 * React (rendering engine of the web-based graphical user interface)
 * Express (web-server framework)
@@ -19,14 +19,14 @@ and utilizes the following technologies (a.k.a MERN-stack):
 Other, most noticeable dependencies are:
 
 * [Jest](https://jestjs.io/) as the test framework for both parts
-* [ESLint](https://eslint.org/) for code quality (linting)
-* [Webpack](https://webpack.js.org/) to bundle the fronend
+* [Webpack](https://webpack.js.org/) to bundle the frontend
 * [Babel](https://babeljs.io/) to transpile and therewith support latest Ecmascript versions
+* [ESLint](https://eslint.org/) to ensure code quality (linting); is invoked as part of the webpack build chain 
 * [Mongoose](https://mongoosejs.com/docs/api.html) as the database driver
  
 
 *Please see the `scripts` sections in the respective `package.json` files to find out which commands are available for
-each parts.*
+each part.*
 
 
 ##### Full disclosure