Small changes

guides/v2.2/cloud/project/project-integrate-blackfire.md

@@ -235,11 +235,11 @@ By simply defining a set of key requests for Blackfire to profile— `/home`, `/
 
 ### Writing your first automated tests and scenarios
 
-You can easily write tests and scenarios for Blackfire to execute. Create a `.blackfire.yml` file and store it at your project root directory.
+You can easily write tests and scenarios for Blackfire to execute. Create a `.blackfire.yaml` file and store it at your project root directory.
 
 Try adding the following scenarios in the file:
 
-> .blackfire.yml
+> .blackfire.yaml
 
 ```yaml
 scenarios:
@@ -257,7 +257,7 @@ See the Blackfire documentation on [Writing tests](https://blackfire.io/docs/coo
 
 ### Running your tests automatically {#automation}
 
-Once you create and deploy your `.blackfire.yml` file, you can enable Blackfire to run your tests automatically in various ways:
+Once you create and deploy your `.blackfire.yaml` file, you can enable Blackfire to run your tests automatically in various ways:
 
 -  **Automated builds on Integration**—Whenever you push code on an Integration, Staging, or Production branch, Blackfire automatically runs your tests. You can receive a notification of the results in various ways, such as a commit status level when using GitHub or Bitbucket. See Blackfire notifications.
 

guides/v2.2/contributor-guide/templates/basic_template.md

@@ -20,9 +20,10 @@ Parameter | Description
 `functional_areas:`  |  Optional. Adds facets for search results. Available facets include: Sales, Products, Carts, Customers, Marketing, Account, Content, Reports, Stores, System, Catalog, Orders, Frontend, Theme, Staging, Search, Configurations, Integration, Services, Tools, Setup, Testing, test, Standards, Install, Upgrade, B2B, Cloud, and Bundled extensions. These facets are case sensitive and support multiple facets separated by commas. For example: `functional_areas: Install`.
 `redirect_from`  | Optional. Add a list of other pages in DevDocs that should redirect to this page. The link should start with the `/guides` directory. For an example, see the source code for this template page.
 `ee_only:` | Optional. If set to `true`, graphics/cues display on the page indicating it applies to {{site.data.var.ee}}.
+`contributor_name`  | Optional. Add a contributor's name to the metadata to add a "Thanks for contributing to this topic!" attribution in the top right corner of a topic.
+`contributor_link:` | Optional. Add a link to the contributor's GitHub profile or website. The attribution will include this link.
 
-{% include note.html type='info' content='If you need help with metadata, we can help in your submitted pull requests.'
-%}
+If you need help with metadata, we can assist!
 
 ## Basic Markdown Syntax {#basic}
 

guides/v2.2/extension-dev-guide/cache/partial-caching/create-cache-type.md

@@ -10,7 +10,7 @@ The tag *scope* provides a mechanism for a cache type.
 To create a new cache type:
 
 ```php
-class %Namespace%\%Module%\Model\Cache\Type extends \Magento\Framework\Cache\Frontend\Decorator\TagScope
+class VendorName\ModuleName\Model\Cache\Type extends \Magento\Framework\Cache\Frontend\Decorator\TagScope
 {
   const TYPE_IDENTIFIER = '%cache_type_id%';
   const CACHE_TAG = '%CACHE_TYPE_TAG%';
@@ -24,7 +24,7 @@ class %Namespace%\%Module%\Model\Cache\Type extends \Magento\Framework\Cache\Fro
 
 You must specify the following parameters:
 
-*  `Namespace\Module` defines the name of a [module](https://glossary.magento.com/module) that uses a cache type. A module can use several cache types and a cache type can be used in several modules.
+*  `VendorName\ModuleName` defines the name of a [module](https://glossary.magento.com/module) that uses a cache type. A module can use several cache types and a cache type can be used in several modules.
 *  `%cache_type_id%` defines unique identifier of a cache type.
 *  `%CACHE_TYPE_TAG%` defines unique tag to be used in the cache type scoping.
 

guides/v2.2/extension-dev-guide/cache/partial-caching/database-caching.md

@@ -47,24 +47,24 @@ To modify `di.xml`:
 1. Open `di.xml` in a text editor and locate the following block:
 
    ```xml
-   <type name="Magento\Framework\App\Cache\Frontend\Pool">
-          <arguments>
-             <argument name="frontendSettings" xsi:type="array">
-                 <item name="page_cache" xsi:type="array">
-                     <item name="backend_options" xsi:type="array">
-                       <item name="cache_dir" xsi:type="string">page_cache</item>
-                     </item>
-                 </item>
-             </argument>
-          </arguments>
-       </type>
-       <type name="Magento\Framework\App\Cache\Type\FrontendPool">
-          <arguments>
-             <argument name="typeFrontendMap" xsi:type="array">
-               <item name="full_page" xsi:type="string">page_cache</item>
-             </argument>
-          </arguments>
-       </type>
+    <type name="Magento\Framework\App\Cache\Frontend\Pool">
+        <arguments>
+            <argument name="frontendSettings" xsi:type="array">
+                <item name="page_cache" xsi:type="array">
+                    <item name="backend_options" xsi:type="array">
+                    <item name="cache_dir" xsi:type="string">page_cache</item>
+                    </item>
+                </item>
+            </argument>
+        </arguments>
+    </type>
+    <type name="Magento\Framework\App\Cache\Type\FrontendPool">
+        <arguments>
+            <argument name="typeFrontendMap" xsi:type="array">
+            <item name="full_page" xsi:type="string">page_cache</item>
+            </argument>
+        </arguments>
+    </type>
    ```
 
    The `<type name="Magento\Framework\App\Cache\Frontend\Pool">` node configures options for the in-memory pool of all frontend cache instances.

guides/v2.2/frontend-dev-guide/themes/theme-create.md

@@ -54,7 +54,7 @@ The folder name conventionally matches naming used in the theme's code: any alph
 
 ## Declare your theme {#fedg_create_theme_how-to_declare}
 
-After you create a directory for your theme, you must create `theme.xml` containing at least the theme name. Optionally, you can specifiy the parent theme name (if the theme [inherits]({{page.baseurl}}/frontend-dev-guide/themes/theme-inherit.html) from one) and, if necessary, where the theme preview image is stored.
+After you create a directory for your theme, you must create `theme.xml` containing at least the theme name. Optionally, you can specify the parent theme name (if the theme [inherits]({{page.baseurl}}/frontend-dev-guide/themes/theme-inherit.html) from one) and, if necessary, where the theme preview image is stored.
 
 1. Add or copy from an existing `theme.xml` file to your theme directory `app/design/frontend/<Vendor>/<theme>`.
 

guides/v2.2/howdoi/checkout/checkout_customize.md

@@ -10,7 +10,7 @@ functional_areas:
   - Checkout
 ---
 
-This topic contains the basic information about how to customize the view of an existing [checkout](https://glossary.magento.com/checkout) step. In the Magento application, checkout is implemented using UI components. You can customize each step by [changing the [JavaScript](https://glossary.magento.com/javascript) implementation or template](#change-component) for a component, [adding](#add), [disabling](#disable), or [removing](#remove) a component.
+This topic contains the basic information about how to customize the view of an existing [checkout](https://glossary.magento.com/checkout) step. In the Magento application, checkout is implemented using UI components. You can customize each step by [changing the JavaScript implementation or template](#change-component) for a component, [adding](#add), [disabling](#disable), or [removing](#remove) a component.
 
 ## Change the component's .js implementation and template {#change-component}
 

guides/v2.2/javascript-dev-guide/widgets/widget_collapsible.md

@@ -8,7 +8,7 @@ The Magento collapsible widget converts a header/content pair into an accordion,
 
 Unlike the accordion widget which is initialized for a set of title/contents pairs, the collapsible widget is initialized for one title/content pair.
 
-To "bind" several instances of collapsible widget, the [`collateral`] option is used.
+To "bind" several instances of a collapsible widget, the [`collateral`] option is used.
 
 Once it is expanded, the content can be updated using Ajax. The collapsed/expanded state can be saved into local storage, or cookies if the browser does not support local storage.
 

guides/v2.3/extension-dev-guide/prepare/lifecycle.md

@@ -34,7 +34,7 @@ If the `schema_version` for your module is found in the `setup_module` table, Ma
 **Example:** InstallSchema.php
 
 ```php
-class \VendorName\ModuleName\Setup\InstallSchema implements \Magento\Framework\Setup\InstallSchemaInterface
+class VendorName\ModuleName\Setup\InstallSchema implements \Magento\Framework\Setup\InstallSchemaInterface
 {
     /**
      * {@inheritdoc}

guides/v2.3/frontend-dev-guide/themes/theme-create.md

@@ -54,7 +54,7 @@ The folder name conventionally matches naming used in the theme's code: any alph
 
 ## Declare your theme {#fedg_create_theme_how-to_declare}
 
-After you create a directory for your theme, you must create `theme.xml` containing at least the theme name. Optionally, you can specifiy the parent theme name (if the theme [inherits]({{page.baseurl}}/frontend-dev-guide/themes/theme-inherit.html) from one) and, if necessary, where the theme preview image is stored.
+After you create a directory for your theme, you must create `theme.xml` containing at least the theme name. Optionally, you can specify the parent theme name (if the theme [inherits]({{page.baseurl}}/frontend-dev-guide/themes/theme-inherit.html) from one) and, if necessary, where the theme preview image is stored.
 
 1. Add or copy from an existing `theme.xml` file to your theme directory `app/design/frontend/<Vendor>/<theme>`.
 

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

@@ -45,6 +45,18 @@ Attribute |  Data Type | Description
 
 The `deleteCustomerAddress` mutation returns a Boolean value that indicates whether the operation was successful.
 
+## Errors
+
+Error | Description
+--- | ---
+`Address "id" value should be specified` | The `id` attribute is zero.
+`Could not find a address with ID "XXX"` | The customer address specified in the `id` attribute does not exist.
+`Customer Address XXX is set as default billing address and cannot be deleted` | You cannot delete a default billing address.
+`Customer Address XXX is set as default shipping address and cannot be deleted` | You cannot delete a default shipping address.
+`Field "deleteCustomerAddress" argument "id" requires type Int!, found "XXX".` | The specified `id` attribute value has the wrong type.
+`Syntax Error: Expected Name, found )` | The `id` attribute was omitted or does not have a value.
+`The current customer isn't authorized.` | The current customer is not currently logged in, or the customer's token does not exist in the `oauth_token` table.
+
 ## Related topics
 
 *  [customer query]({{page.baseurl}}/graphql/queries/customer.html)

guides/v2.3/graphql/mutations/update-customer-address.md

@@ -61,6 +61,19 @@ The `updateCustomerAddress` mutation returns the `CustomerAddress` object.
 
 {% include graphql/customer-address-output.md %}
 
+## Errors
+
+Error | Description
+--- | ---
+`Address "id" value should be specified` | The `id` attribute is zero.
+`Could not find a address with ID "XXX"` | The customer address specified in the `id` attribute does not exist.
+`Current customer does not have permission to address with ID "XXX"` | The customer tries to update the address of another customer.
+`Field "updateCustomerAddress" argument "id" of type "Int!" is required but not provided.` | The `id` attribute was omitted.
+`Field "updateCustomerAddress" argument "id" requires type Int!, found "XXX".` | The specified `id` attribute value has the wrong type.
+`"input" value must be specified` | The `input` attribute was omitted or was specified but is empty.
+`Syntax Error: Expected Name, found )` | The `id` and `input` attributes are omitted.
+`The current customer isn't authorized.` | The current customer is not currently logged in, or the customer's token does not exist in the `oauth_token` table.
+
 ## Related topics
 
 *  [customer query]({{page.baseurl}}/graphql/queries/customer.html)