Merge pull request #2616 from magento-commerce/db_recommend

"Magento recommends" to "We recommend"

Author: dobooth

src/guides/v2.3/extension-dev-guide/build/build.md

@@ -13,7 +13,7 @@ Building your component involves laying out the file structure, creating the nec
 
 Before you begin creating your new component, make sure that you have a working installation of Magento 2, and the Magento [System Requirements]({{ page.baseurl }}/install-gde/system-requirements.html).
 
-Also, Magento recommends that you disable caching while setting up the component file structure and adding configuration files.
+Also, we recommend that you disable caching while setting up the component file structure and adding configuration files.
 
 The following details the component building process:
 

src/guides/v2.3/extension-dev-guide/build/optimal-dev-environment.md

@@ -40,7 +40,7 @@ The following is a list of the different ways you can install Magento 2 locally:
 
 The following is a list of optimizations you can make on your local development machine
 
-*  Magento recommends installing and using the latest supported version of [PHP](https://glossary.magento.com/php) 7 to increase performance.
+*  We recommend installing and using the latest supported version of [PHP](https://glossary.magento.com/php) 7 to increase performance.
 *  Replace your MySQL database with [Percona](https://www.percona.com/software/mysql-database/percona-server){:target="_blank"}.
 *  Make sure you install and enable [PHP OPcache](http://php.net/manual/en/intro.opcache.php){:target="_blank"}.
 *  Xdebug is off by default. Enable this feature only when you need it because it requires a lot of memory and degrades performance.

src/guides/v2.3/extension-dev-guide/cache/page-caching/private-content.md

@@ -11,7 +11,7 @@ This example displays a customer's name on a cacheable page.
 
 ## Create a section source {#config-cache-priv-how-source}
 
-The section source class is responsible for retrieving data for the section. As a best practice, Magento recommends that you put your code within the `Vendor/ModuleName/CustomerData` namespace. Your classes must implement the [`Magento\Customer\CustomerData\SectionSourceInterface`]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Customer/CustomerData/SectionSourceInterface.php){:target="_blank"} interface.
+The section source class is responsible for retrieving data for the section. As a best practice, we recommend that you put your code within the `Vendor/ModuleName/CustomerData` namespace. Your classes must implement the [`Magento\Customer\CustomerData\SectionSourceInterface`]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Customer/CustomerData/SectionSourceInterface.php){:target="_blank"} interface.
 
 The public method `getSectionData` must return an array with data for a private block.
 

src/guides/v2.3/graphql/develop/resolvers.md

@@ -23,7 +23,7 @@ A GraphQL resolver must implement one of the following interfaces:
 
 -  [`\Magento\Framework\GraphQl\Query\ResolverInterface`]({{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/GraphQl/Query/ResolverInterface.php)
 
-The first two interfaces provide a way to resolve multiple branches/leaves at once (known as batching), while the last one resolves one request at a time. Magento recommends using batch resolvers for queries because they improve performance by fetching information required to resolve multiple GraphQL requests with a single operation.
+The first two interfaces provide a way to resolve multiple branches/leaves at once (known as batching), while the last one resolves one request at a time. We recommend using batch resolvers for queries because they improve performance by fetching information required to resolve multiple GraphQL requests with a single operation.
 
 ## Query resolvers
 

src/guides/v2.3/graphql/mutations/change-customer-password.md

@@ -5,7 +5,7 @@ title: changeCustomerPassword mutation
 
 Use the `changeCustomerPassword` mutation to change the password for the logged-in customer.
 
-To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
+To return or modify information about a customer, we recommend you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
 
 ## Syntax
 

src/guides/v2.3/graphql/mutations/create-customer-address.md

@@ -5,7 +5,7 @@ title: createCustomerAddress mutation
 
 Use the `createCustomerAddress` mutation to create the customer's address.
 
-To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
+To return or modify information about a customer, we recommend you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
 
 ## Syntax
 

src/guides/v2.3/graphql/mutations/create-customer.md

@@ -5,7 +5,7 @@ title: createCustomer mutation
 
 Use the `createCustomer` mutation to create a new customer.
 
-To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
+To return or modify information about a customer, we recommend you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
 
 ## Syntax
 

src/guides/v2.3/graphql/mutations/delete-customer-address.md

@@ -5,7 +5,7 @@ title: deleteCustomerAddress mutation
 
 Use the `deleteCustomerAddress` mutation to delete the specified customer address.
 
-To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
+To return or modify information about a customer, we recommend you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
 
 ## Syntax
 

src/guides/v2.3/graphql/mutations/generate-customer-token.md

@@ -5,7 +5,7 @@ title: generateCustomerToken mutation
 
 Use the `generateCustomerToken` mutation to create a new customer token.
 
-To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
+To return or modify information about a customer, we recommend you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
 
 ## Syntax
 

src/guides/v2.3/graphql/mutations/revoke-customer-token.md

@@ -5,7 +5,7 @@ title: revokeCustomerToken mutation
 
 Use the `revokeCustomerToken` mutation to revokes the customer's token.
 
-To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
+To return or modify information about a customer, we recommend you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html).
 
 ## Syntax