From 2713fb736a2384edb5598b231c9f16e5f578e074 Mon Sep 17 00:00:00 2001
From: fvromera <32909196+fvromera@users.noreply.github.com>
Date: Fri, 7 May 2021 08:17:42 +0200
Subject: [PATCH] Fix some wrong words

Fixed some possible wrong words.
---
 en/application-micro.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/en/application-micro.md b/en/application-micro.md
index d124907a79c2..f0020bcdee64 100644
--- a/en/application-micro.md
+++ b/en/application-micro.md
@@ -1753,7 +1753,7 @@ $app->after(
 );
 ```
 
-You can also use classes and attach them to the Events Manager as listener. Using this approach offers more flexibility are reduces the bootstrap file size, since the middleware logic is encapsulated in one file per middleware.
+You can also use classes and attach them to the Events Manager as listener. Using this approach offers more flexibility and reduces the bootstrap file size, since the middleware logic is encapsulated in one file per middleware.
 
 ```php
 <?php
@@ -1939,7 +1939,7 @@ class FirewallMiddleware implements MiddlewareInterface
 
 **Not Found (404) Middleware**
 
-When this middleware is processed, this means that the requesting IP is allowed to access our application. The application will try and match the route and if not found the `beforeNotFound` event will fire. We will stop the processing then and send back to the user the relevant 404 response. This middleware is attached to the `before` event of our Micro application
+When this middleware is processed, this means that the requesting IP is allowed to access our application. The application will try to match the route and if not found the `beforeNotFound` event will fire. We will stop the processing then and send back to the user the relevant 404 response. This middleware is attached to the `before` event of our Micro application
 
 ```php
 <?php