CODE RUB: Fix Language

3. Exposers/3.1 Communication Protocols/3.1.1 RESTful APIs/3.1.1 RESTful APIs.md

@@ -461,9 +461,9 @@ Home controllers are not required to have any security. They open a gate for hea
 There are three different types of tests that cover API controllers as well as any other exposure layer. These tests are: unit tests, acceptance tests and integration or end-to-end (E2E) tests. Integration tests can vary between smoke testing, availability testing, performance testing and many others. But for the purpose of this chapter, we will focus on unit and acceptance tests.
 
 ### 3.1.1.5.0 Unit Tests
-Controllers have a similar type of logic that exists in Services, this logic is the mapping between exceptions coming from a dependency or internally and what these exceptions are being mapped to for the consumer of these APIs. For instance, a `StudentValidationException` can be mapped to a `BadRequest` status code. This logic is tested in unit tests. Let's take a look at an example:
+Controllers have a similar type of logic that exists in Services. This logic is the mapping between exceptions coming from a dependency or internally and what these exceptions are being mapped to for the consumer of these APIs. For instance, a `StudentValidationException` can be mapped to a `BadRequest` status code. This logic is tested in unit tests. Let's take a look at an example:
 
-Starting with the test before the implementation, let's assume we have a controller `StudentsController` that retrieves all students. When the call succeeds the controller should return `200 OK` status code. Let's write a test for that:
+Starting with the test before the implementation, let's assume we have a controller `StudentsController` that retrieves all students. When the call succeeds, the controller should return a `200 OK` status code. Let's write a test for that:
 
 First, let's setup our `StudentsController` class as follows: