Merge pull request #612 from lincolnarrais/patch-2

Suggestions that I think may improve documentation just a little bit. /docs/intro/

Author: raphaelbarbosaqwerty

doc/docs/intro.md

@@ -8,23 +8,23 @@ Let's find out how to implement a Modular structure in your project.
 
 ## What is Modular?
 
-The Modular proposes to solve two problems:
+Modular proposes to solve two problems:
 - Modularized routes.
 - Modularized Dependency Injection.
 
-In a monolithic, where we have our entire application as a single module, we design our software quickly and
-elegant taking advantage of all the amazing features of Flutter💙. However, producing a larger app in a "monolithic" way
-can generate technical debt in both maintenance and scalability. With this in mind, the developers adopted architectural strategies to better divide the code, minimizing the negative impacts on the project's maintainability and scalability..
+In a monolithic architecture, where we have our entire application as a single module, we design our software in a quick and
+elegant way, taking advantage of all the amazing features of Flutter💙. However, producing a larger app in a "monolithic" way
+can generate technical debt in both maintanance and scalability. With this in mind, developers adopted architectural strategies to better divide the code, minimizing the negative impacts on the project's maintainability and scalability..
 
 By better dividing the scope of features, we gain:
 
 - Improved understanding of features.
-- Less break changes.
+- Less breaking changes.
 - Add new non-conflicting features.
 - Less blind spots in the project's main business rule.
 - Improved developer turnover.
 
-With the most readable code, we extend the life of the project. See example of a standard MVC with 3 features(Auth, Home, Product):
+With a more readable code, we extend the life of the project. See example of a standard MVC with 3 features(Auth, Home, Product):
 
 ### A typical MVC
 
@@ -75,17 +75,17 @@ Let's see how the structure looks when we divide by scope:
 
 What we did in this structure was to continue using MVC, but this time in scope. This means that
 each feature has its own MVC, and this simple approach solves many scalability and maintainability issues.
-We call this approach "Smart Structure". There were still two things that were Global and that clashed with the structure itself and so we created Modular to solve this impasse.
+We call this approach "Smart Structure". But two things were still Global and clashed with the structure itself, so we created Modular to solve this impasse.
 
 In short: Modular is a solution to modularize the route and dependency injection system, making each scope have
 its own routes and injections independent of any other factor in the structure.
-We create an object to group the Routes and Injections and call it **Modules**.
+We create objects to group the Routes and Injections and call them **Modules**.
 
 
 
 ## Ready to get started?
 
-Modular is not only ingenious for doing something amazing like componentizing Routes and Dependency Injections, it's amazing.
+Modular is not only ingenious for doing something amazing like componentizing Routes and Dependency Injections, it's amazing
 for being able to do all this simply!
 
 Go to the next topic and start your journey towards an intelligent structure.
@@ -94,15 +94,15 @@ Go to the next topic and start your journey towards an intelligent structure.
 
 - Does Modular work with any state management approach?
     - Yes, the dependency injection system is agnostic to any kind of class
-     including the reactivity that make up state management.
+     including the reactivity that makes up state management.
 
 - Can I use dynamic routes or Wildcards?
     - Yes! The entire route tree responds as on the Web. Therefore, you can use dynamic parameters,
      query, fragments or simply include a wildcard to enable a redirect
      to a 404 page for example.
 
 - Do I need to create a Module for all features?
-    - No. You can create a module only when you think it's necessary or when the feature is no longer a part
-    the scope in which it is being worked.
+    - No. You can create a module only when you think it's necessary or when the feature is no longer a part of
+    the scope in which it is being worked on.