message: chore(docs): update docs/introduction/modules.md
  Fixes a few grammatical errors, fixes syntax tabbing in code blocks, and a little rewording for clarity.
diff: @@ -4,17 +4,17 @@ title: What's a module?
  sidebar_label: What's a module?
  ---
  -GraphQL Modules approach let you separate your backend implementation to small, reusable, easy-to-implement and easy-to-test pieces.
  +The GraphQL Modules approach lets you separate your backend implementation to small, reusable, easy-to-implement and easy-to-test pieces.
  -In GraphQL Modules,Each module have it's own GraphQL type definitions and resolvers implementation.
  +In GraphQL Modules, each module has it's own GraphQL type definitions and resolver implementations.
  -GraphQL `type`s, `enum`s and `union`s that declared using GraphQL Modules are also extendable, so modules can re-declare types and extend them as they wish.
  +GraphQL `type`s, `enum`s and `union`s that are declared using GraphQL Modules are also extendable, so modules can re-declare types and extend them as they wish.
  -The idea behind it to implement **[Separation of Concerns](https://deviq.com/separation-of-concerns/)** design pattern in GraphQL, and to allow you to write simple modules that does only what it needs. This way it's easier to write, maintain and test.
  +The idea behind it is to implement the **[Separation of Concerns](https://deviq.com/separation-of-concerns/)** design pattern in GraphQL, and to allow you to write simple modules that only does what it needs to. This way it's easier to write, maintain and test.
  ## Module Structure
  -Each GraphQL `module` is built the basics of GraphQL:
  +Each GraphQL `module` is built behind the basics of GraphQL:
  - Type definitions
  - Resolvers
  @@ -27,7 +27,7 @@ And as your application grows, modules can have:
  ## Modules Example
  -To get a better understanding of modules structure and it's extendability, let's take for example an app with 3 imports:
  +To get a better understanding of modules structure and it's extendability, let's take an example app with 3 imports:
  - Authentication (defines only what it needs for users' authentication)
  - Users (define what user in our app should have)
  @@ -88,7 +88,7 @@ type User {
  #### Gallery Module
  -The gallery module is similar to `profile` module, and it only declares the parts of the schema that required by the gallery feature:
  +The gallery module is similar to the `profile` module, and it only declares the parts of the schema that are required by the gallery feature:
  ```graphql
  type Image {
  