Merge pull request #23 from bobocode-projects/spring_mvc_fix_typo_in_java_doc

Fix javadoc and typos

Author: tboychuk

3-0-spring-framework/3-0-1-hello-spring-mvc/src/main/java/com/bobocode/mvc/api/NoteRestController.java

@@ -7,15 +7,15 @@
  * This controller provides a very simple REST API for Notes. It implements two endpoints that allow you to add
  * a new note and get all notes.
  * <p>
- * The base URL is `/api/notes/`. It accepts HTTP GET request to get all notes, and POST request to add a new note.
+ * The base URL is `/api/notes`. It accepts HTTP GET request to get all notes, and POST request to add a new note.
  * <p>
  * Both methods work with content type JSON. The endpoint that returns all notes does not require any input parameters,
  * while the one that adds a new note accepts a JSON with a new note fields in the request body. In order to get or
  * add a note, just use a provided {@link Notes} field as a storage.
  * <p>
  * This controller can only be used by a separate front-end application, since it provides only data and no UI. It shows
  * how Spring MVC is used nowadays to build enterprise web application that have separate front-end. But initially
- * Spring MVC was used to build the whole application including front-end. So the controllers were connected to views
+ * Spring MVC was used to build the whole application including front-end. So the controllers were connected to the views
  * via models, like in {@link com.bobocode.mvc.controller.NoteController}
  */
 @RequiredArgsConstructor

3-0-spring-framework/3-0-1-hello-spring-mvc/src/main/java/com/bobocode/mvc/controller/NoteController.java

@@ -9,21 +9,21 @@
  * (YOU DON'T NEED TO KNOW IT). And the purpose of the controller is to power that UI and wire it to the storage that
  * is already provided as a field of class {@link Notes}. The base URL is `/notes`.
  * <p>
- * This controller handles the HTTP GET request that should list all notes. It order to do that, it fetches the list
+ * This controller handles the HTTP GET request that should list all notes. In order to do that, it fetches the list
  * of notes, adds that list as an attribute to the {@link org.springframework.ui.Model}, and returns a corresponding view.
  * The view (which is Thymeleaf HTML template) expects to receive an attribute called `noteList`.
  * In classical Spring MVC, controller methods return a string value which stores a view name.
- * A {@link org.springframework.web.servlet.ViewResolver} is already configured to look for a HTML template in
- * `/resources/templates`. So the method should just return a html file name without `.html`.
+ * A {@link org.springframework.web.servlet.ViewResolver} is already configured to look for an HTML template in
+ * `/resources/templates`. So the method should just return an HTML file name without `.html`.
  * <p>
  * In order to add a new note, this controller handles HTTP POST request that is sent by HTML form. After submitting,
  * the request will have to POST parameters called `title` and `text` accordingly. So this controller retrieves those
- * params from he request and use them in order to create and add a new note. Once a new note is added, it redirects the
+ * params from the request and use them in order to create and add a new note. Once a new note is added, it redirects the
  * request to the notes page.
  * <p>
  * Such controllers are used when both back-end and the UI are provided by the same Spring MVC application. In reality,
  * most application that have a rich and powerful UI, are not built like that. They have separate front-end and
- * back-end applications. The the back-end app, will only need to provide data and don't care about view. In that case
+ * back-end applications. The back-end app, will only need to provide data and don't care about view. In that case
  * the same controller will look like {@link com.bobocode.mvc.api.NoteRestController}
  */
 @RequiredArgsConstructor