Fixed some typos

README.md

@@ -10,21 +10,21 @@ A live deployment is available on Heroku: https://spring-boot-vuejs.herokuapp.co
 
 There's also a blog post about this project available here: https://blog.codecentric.de/en/2018/04/spring-boot-vuejs/
 
-## In Search of a new Webfrontend-Framework after 2 Years of absence...
+## In Search of a new Web Frontend-Framework after 2 Years of absence...
 
-Well I’am not a Frontend developer. I’am more like playing around with Spring Boot, Web- & Microservices & Docker, automating things with Ansible and Docker, Scaling things with Spring Cloud, Docker Compose and Traefik... And the only GUIs I’am building are the "new JS framework in town"-app every two years... :) So the last one was Angular 1 - and it felt, as it was a good choice! I loved the coding experience and after a day of training, I felt able to write awesome Frontends...
+Well, I’m not a Frontend developer. I’m more like playing around with Spring Boot, Web- & Microservices & Docker, automating things with Ansible and Docker, Scaling things with Spring Cloud, Docker Compose, and Traefik... And the only GUIs I’m building are the "new JS framework in town"-app every two years... :) So the last one was Angular 1 - and it felt, as it was a good choice! I loved the coding experience and after a day of training, I felt able to write awesome Frontends...
 
-But now we’re 2 years later and I heard from afar, that there was a complete rewrite of Angular (2), a new kid in town from Facebook (React) and lots of ES201x stuff and dependency managers like bower and Co. So I’am now in the new 2-year-cycle of trying to cope up again - and so glad I found this article: https://medium.com/reverdev/why-we-moved-from-angular-2-to-vue-js-and-why-we-didnt-choose-react-ef807d9f4163
+But now we’re 2 years later and I heard from afar, that there was a complete rewrite of Angular (2), a new kid in town from Facebook (React) and lots of ES201x stuff and dependency managers like bower and Co. So I’m now in the new 2-year-cycle of trying to cope up again - and so glad I found this article: https://medium.com/reverdev/why-we-moved-from-angular-2-to-vue-js-and-why-we-didnt-choose-react-ef807d9f4163
 
 Key points are:
-* Angular 2 isn’t the way to go, if you know version 1 (complete re-write, only with Typescript, loss of many of 1’s advantages, Angular 4 is coming)
+* Angular 2 isn’t the way to go if you know version 1 (complete re-write, only with Typescript, loss of many of 1’s advantages, Angular 4 is coming)
 * React  (facebookish problems (licence), need to choose btw. Redux & MObX, harder learning curve, slower coding speed)
 
 ![comparison-angular-react-vuejs](screenshots/comparison-angular-react-vuejs.png)
 
 And the [introduction phrase](https://vuejs.org/v2/guide/index.html) sounds really great:
 
-> Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. Unlike other monolithic frameworks, Vue is designed from the ground up to be incrementally adoptable. The core library is focused on the view layer only, and is very easy to pick up and integrate with other libraries or existing projects. On the other hand, Vue is also perfectly capable of powering sophisticated Single-Page Applications when used in combination with modern tooling and supporting libraries.
+> Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. Unlike other monolithic frameworks, Vue is designed from the ground up to be incrementally adoptable. The core library is focused on the view layer only and is very easy to pick up and integrate with other libraries or existing projects. On the other hand, Vue is also perfectly capable of powering sophisticated Single-Page Applications when used in combination with modern tooling and supporting libraries.
 
 So I think, it could be a good idea to invest a day or so into Vue.js. Let’s have a look here!
 
@@ -73,7 +73,7 @@ spring-boot-vuejs
 
 ## Backend
 
-Go to https://start.spring.io/ and initialize an Spring Boot app with `Web` and `Actuator`. Place the zip’s contents in the backend folder.
+Go to https://start.spring.io/ and initialize a Spring Boot app with `Web` and `Actuator`. Place the zip’s contents in the backend folder.
 
 Customize pom to copy content from Frontend for serving it later with the embedded Tomcat:
 
@@ -120,7 +120,7 @@ Customize pom to copy content from Frontend for serving it later with the embedd
 vue init webpack frontend
 ```
 
-This will initialize a project skeleton for Vue.js in /frontend directory - it therefore asks some questions in the cli:
+This will initialize a project skeleton for Vue.js in /frontend directory - it, therefore, asks some questions in the cli:
 
 ![vuejs-cli-init](screenshots/vuejs-cli-init.png)
 
@@ -179,7 +179,7 @@ If you’re a backend dev like me, this Maven plugin here https://github.com/eir
 
 ### tell Webpack to output the dist/ contents to target/
 
-Commonly, node projects will create a dist/ directory for final builds which contains the minified source code of the web app - but we want it all in `/target`. Therefore go to `frontend/config/index.js` and replace the following lines:
+Commonly, node projects will create for final build a `dist/` directory which contains the minified source code of the web app - but we want it all in `/target`. Therefore go to `frontend/config/index.js` and replace the following lines:
 
 ```
 index: path.resolve(__dirname, '../dist/index.html'),
@@ -231,13 +231,13 @@ Install vue-devtools Browser extension https://github.com/vuejs/vue-devtools and
 
 There's a blog post: https://blog.jetbrains.com/webstorm/2018/01/working-with-vue-js-in-webstorm/
 
-Escpecially the `New... Vue Component` looks quite cool :)
+Especially the `New... Vue Component` looks quite cool :)
 
 
 
 ## HTTP calls from Vue.js to (Spring Boot) REST backend
 
-Prior to Vue 2.0, there was a build in soultion (vue-resource). But from 2.0 on, 3rd party libraries are necessary. One of them is [Axios](https://github.com/mzabriskie/axios) - also see blog post https://alligator.io/vuejs/rest-api-axios/
+Prior to Vue 2.0, there was a build in solution (vue-resource). But from 2.0 on, 3rd party libraries are necessary. One of them is [Axios](https://github.com/mzabriskie/axios) - also see blog post https://alligator.io/vuejs/rest-api-axios/
 
 ```
 npm install axios --save
@@ -278,9 +278,9 @@ In your template area you can now request a service call via calling `callRestSe
 
 ### The problem with SOP
 
-Single-Origin Policy (SOP) could be a problem, if we want to develop our app. Because the webpack-dev-server runs on http://localhost:8080 and our Spring Boot REST backend on http://localhost:8088.
+Single-Origin Policy (SOP) could be a problem if we want to develop our app. Because the webpack-dev-server runs on http://localhost:8080 and our Spring Boot REST backend on http://localhost:8088.
 
-We need to use Cross Origin Resource Sharing Protocol (CORS) to handle that (read more background info about CORS here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS)
+We need to use Cross-Origin Resource Sharing Protocol (CORS) to handle that (read more background info about CORS here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS)
 
 #### Enabling Axios CORS support
 
@@ -297,7 +297,7 @@ export const AXIOS = axios.create({
 })
 ```
 
-Here we allow requests to the base URL of our Spring Boot App on port 8088 to be accessable from 8080.
+Here we allow requests to the base URL of our Spring Boot App on port 8088 to be accessible from 8080.
 
 Now we could use this configuration inside our Components, e.g. in `Hello.vue`:
 ```js
@@ -329,7 +329,7 @@ export default {
 
 #### Enabling Spring Boot CORS support
 
-Additionally, we need to configure our Spring Boot backend to answer with the appropriate CORS HTTP Headers in it’s responses (theres a good tutorial here: https://spring.io/guides/gs/rest-service-cors/). Therefore we add the annotation `@CrossOrigin` to our BackendController:
+Additionally, we need to configure our Spring Boot backend to answer with the appropriate CORS HTTP Headers in its responses (there's a good tutorial here: https://spring.io/guides/gs/rest-service-cors/). Therefore we add the annotation `@CrossOrigin` to our BackendController:
 
 ```java
 @CrossOrigin(origins = "http://localhost:8080")
@@ -340,7 +340,7 @@ public @ResponseBody String sayHello() {
 }
 ```
 
-Now our Backend will responde CORS-enabled and accepts requests from 8080. But as this only enables CORS on one method, we have to repeatately add this annotation to all of our REST endpoints, which isn’t a nice style. We should use a global solution to allow access with CORS enabled to all of our REST resources. This could be done in the `SpringBootVuejsApplication.class`:
+Now our Backend will respond CORS-enabled and will accept requests from 8080. But as this only enables CORS on one method, we have to repeatedly add this annotation to all of our REST endpoints, which isn’t a nice style. We should use a global solution to allow access with CORS enabled to all of our REST resources. This could be done in the `SpringBootVuejsApplication.class`:
 
 ```java
 // Enable CORS globally
@@ -443,7 +443,7 @@ Frontend needs to know the Port of our Spring Boot backend API, which is [automa
 
 To access the Heroku set port, we need to use relative paths inside our Vue.js application instead of hard-coded hosts and ports! 
 
-All we need to do, is to configure Axios in such a way inside our [frontend/src/components/http-common.js](https://github.com/jonashackt/spring-boot-vuejs/blob/master/frontend/src/components/http-common.js):
+All we need to do is to configure Axios in such a way inside our [frontend/src/components/http-common.js](https://github.com/jonashackt/spring-boot-vuejs/blob/master/frontend/src/components/http-common.js):
 
 ```
 export const AXIOS = axios.create({
@@ -453,7 +453,7 @@ export const AXIOS = axios.create({
 
 #### Using Heroku's Postgres as Database for Spring Boot backend and Vue.js frontend
 
-First add [Heroku Postgres database](https://elements.heroku.com/addons/heroku-postgresql) for your Heroku app. 
+First, add [Heroku Postgres database](https://elements.heroku.com/addons/heroku-postgresql) for your Heroku app. 
 
 Then follow these instructions on Stackoverflow to configure all needed Environment variables in Heroku: https://stackoverflow.com/a/49978310/4964553
 
@@ -539,7 +539,7 @@ public class UserRepositoryTest {
 }
 ```
 
-Then include these functionality into your REST-API - see [BackendController.java](backend/src/main/java/de/jonashackt/springbootvuejs/controller/BackendController.java):
+Then include this functionality in your REST-API - see [BackendController.java](backend/src/main/java/de/jonashackt/springbootvuejs/controller/BackendController.java):
 
 ```java
     @RequestMapping(path = "/user", method = RequestMethod.POST)
@@ -646,7 +646,7 @@ https://github.com/vuejs/vue-test-utils
 
 ### Jest
 
-Jest is a new shooting star at the sky of JavaScript testing frameworks: https://facebook.github.io/jest/
+Jest is a new shooting star in the sky of JavaScript testing frameworks: https://facebook.github.io/jest/
 
 Intro-Blogpost: https://blog.codecentric.de/2017/06/javascript-unit-tests-sind-schwer-aufzusetzen-keep-calm-use-jest/
 
@@ -728,12 +728,12 @@ This will integrate the Jest Unittests right after the npm run build command, ju
 
 ![maven-integration-jest-unittests](screenshots/maven-integration-jest-unittests.png)
 
-And don't mind the depitction with `ERROR` - this is just a known bug: https://github.com/eirslett/frontend-maven-plugin/issues/584
+And don't mind the depiction with `ERROR` - this is just a known bug: https://github.com/eirslett/frontend-maven-plugin/issues/584
 
 
 ##### Run Jest tests inside IntelliJ
 
-First we need to install the NodeJS IntelliJ plugin (https://www.jetbrains.com/help/idea/developing-node-js-applications.html), which isn't bundled with IntelliJ by default:
+First, we need to install the NodeJS IntelliJ plugin (https://www.jetbrains.com/help/idea/developing-node-js-applications.html), which isn't bundled with IntelliJ by default:
 
 ![nodejs-intellij-plugin](screenshots/nodejs-intellij-plugin.png)
 
@@ -757,7 +757,7 @@ Now, when running `All Tests`, this should look like you're already used to Unit
 
 ## End-2-End (E2E) tests with Nightwatch
 
-Great tooling: http://nightwatchjs.org/ - Nightwatch controls WebDriver / Selenium standalone Server in own childprocess and abstracts from those, providing a handy DSL for Acceptance tests:
+Great tooling: http://nightwatchjs.org/ - Nightwatch controls WebDriver / Selenium standalone Server in own child process and abstracts from those, providing a handy DSL for Acceptance tests:
 
 Docs: http://nightwatchjs.org/gettingstarted/#browser-drivers-setup
 
@@ -812,7 +812,7 @@ With the latest 0.9.21 of Nightwatch, this issue is gone. __BUT:__ the the `npm
 
 ![nightwatch-npmaudit-vulnerabilities](screenshots/nightwatch-npmaudit-vulnerabilities.png)
 
-And thus the whole build process will brake. The problem are breaking changes in [Nightwatch 1.x](https://github.com/nightwatchjs/nightwatch#nightwatch-v10), that aren't reflected inside the Vue.js Webpack template so far (they use the latest 0.9.x, which is vulnerable): https://github.com/nightwatchjs/nightwatch/wiki/Migrating-to-Nightwatch-1.0
+And thus the whole build process will break. The problem is breaking changes in [Nightwatch 1.x](https://github.com/nightwatchjs/nightwatch#nightwatch-v10), that aren't reflected inside the Vue.js Webpack template so far (they use the latest 0.9.x, which is vulnerable): https://github.com/nightwatchjs/nightwatch/wiki/Migrating-to-Nightwatch-1.0
 
 
 ## Run all tests
@@ -854,7 +854,7 @@ https://docs.npmjs.com/getting-started/updating-local-packages
 
 # Links
 
-Nice introdutory video: https://www.youtube.com/watch?v=z6hQqgvGI4Y
+Nice introductory video: https://www.youtube.com/watch?v=z6hQqgvGI4Y
 
 Examples: https://vuejs.org/v2/examples/