Fixed capitalization and minor formatting issues

Author: maayanbar13

content/graphql/sharing-models.md

@@ -4,11 +4,11 @@
 
 One of the biggest advantages of using Typescript for the backend of your project is the ability to reuse the same models in a Typescript-based frontend application, by using a common Typescript package.    
 
-but there's a problem: the models created using the Code first approach are heavily decorated with graphql related decorators. Those decorators are irrelevant in the frontend, negatively impacting performance.
+But there's a problem: the models created using the code first approach are heavily decorated with GraphQL related decorators. Those decorators are irrelevant in the frontend, negatively impacting performance.
 
 #### Using the model shim
 
-To solve this issue, nest provides a "shim" which allows you to replace the original decorators with inert code by using a `webpack` (or similar) configuration.    
+To solve this issue, NestJS provides a "shim" which allows you to replace the original decorators with inert code by using a `webpack` (or similar) configuration.
 To use this shim, configure an alias between the `@nestjs/graphql` package and the shim.
 
 For example, for webpack this is resolved this way: