fix/writing-styleguide

docs/guides/Integration-Guides/session-manager/adding-telesales-impersonated-email-using-the-session-manager.md

@@ -11,7 +11,7 @@ In order to allow this type of selling, VTEX offers the telesales feature, throu
 
 ## Telesales Toolbar 
 
-The [telesales toolbar](https://help.vtex.com/en/tutorial/telesales-toolbar--tutorials_5500) is the most straightforward way to use the telesales feature. A top bar appears on the store's front end once the registered operator logs in to the store environment. It is displayed in all site areas, except on the [My Orders screen](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#orders).
+The [telesales toolbar](https://help.vtex.com/en/tutorial/telesales-toolbar--tutorials_5500) is the most straightforward way to use the telesales feature. A top bar appears on the store's frontend once the registered operator logs in to the store environment. It is displayed in all site areas, except on the [My Orders screen](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#orders).
 
 These are the steps required to use the telesales toolbar:
 1. [Create a telesales user](https://help.vtex.com/tutorial/como-criar-um-usuario-de-televendas--frequentlyAskedQuestions_4227).

docs/release-notes/search-graphql.md

@@ -8,7 +8,7 @@ The giant `store-graphql` app was segmented and gave way to the new `search-grap
 
 ## What has changed
 
-**Previously, the** `store-graphql` **was a monolith app** responsible for sending GraphQL queries to all [VTEX APIs](https://help.vtex.com/developer-docs), meaning that all information required by the store's front end would necessarily go through `store-graphql`.
+**Previously, the** `store-graphql` **was a monolith app** responsible for sending GraphQL queries to all [VTEX APIs](https://help.vtex.com/developer-docs), meaning that all information required by the store's frontend would necessarily go through `store-graphql`.
 
 The issue was that the constant and rapid platform evolution meant that the app centralized a very large number of different requests, from getting product data from the Search API (a fast operation having a short timeout and a lot of cache) to adding items in the cart (whose timeout is long due to the delay in Checkout responsiveness along with the inexistent cache, since it's a operation performed by the user).
 

docs/vtex-io/Reference/graphql-apis/search-graphql.md

@@ -19,7 +19,7 @@ To use it in your app, declare it on your `manifest.json` file, as demonstrated
 }
 ```
 
-You may then use it in your front end component queries, for example, write file `productQuery.gql`:
+You may then use it in your frontend component queries, for example, write file `productQuery.gql`:
 
 ```graphql
 query ProductQuery($slug: String) {