Merge branch 'master' into ds_rm-obsolete-page

Author: dshevtsov

.github/CODE_OF_CONDUCT.md

@@ -14,21 +14,21 @@ religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+*  Using welcoming and inclusive language
+*  Being respectful of differing viewpoints and experiences
+*  Gracefully accepting constructive criticism
+*  Focusing on what is best for the community
+*  Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* Using sexualized language or imagery and unwelcome sexual attention or
+*  Using sexualized language or imagery and unwelcome sexual attention or
   advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
+*  Trolling, insulting/derogatory comments, and personal or political attacks
+*  Public or private harassment
+*  Publishing others' private information, such as a physical or electronic
   address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+*  Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities

.github/ISSUE_TEMPLATE/COMMUNITY_ISSUE_TEMPLATE.md

@@ -9,28 +9,28 @@ about: Create an issue related to a community engineering effort
 
 Type of Doc:
 
-- [ ] New topic
-- [ ] Topic Update, Devdoc link:
-- [ ] Other
+-  [ ] New topic
+-  [ ] Topic Update, Devdoc link:
+-  [ ] Other
 
 Magento 2 GitHub Issue: https://github.com/magento/devdocs/issues/link
 
 Magento 2 GitHub PR: https://github.com/magento/devdocs/pull/link
 
 Magento 2 version:
 
-- [ ] 2.1.X
-- [ ] 2.2.X
-- [ ] 2.3.X
-- [ ] back port
-- [ ] forward port
+-  [ ] 2.1.X
+-  [ ] 2.2.X
+-  [ ] 2.3.X
+-  [ ] back port
+-  [ ] forward port
 
 Notifications of Changes:
 
-- [ ] Changes to Admin interface?
-- [ ] New software requirements?
-- [ ] New REST endpoints or updated GraphQL query syntax?
-- [ ] New command line option?
+-  [ ] Changes to Admin interface?
+-  [ ] New software requirements?
+-  [ ] New REST endpoints or updated GraphQL query syntax?
+-  [ ] New command line option?
 
 ## Content
 

.github/ISSUE_TEMPLATE/NEW_TOPIC.md

@@ -15,10 +15,10 @@ about: Create a request to add missing information to devdocs
 
 <!-- Use the following checklist template as a starting point -->
 
-- [ ] The topic provides an explanation of how ____ works.
-- [ ] The topic provides steps for ____.
-- [ ] The topic contains code samples that shows ____.
-- [ ] Other (please specify)
+-  [ ] The topic provides an explanation of how ____ works.
+-  [ ] The topic provides steps for ____.
+-  [ ] The topic contains code samples that shows ____.
+-  [ ] Other (please specify)
 
 ## Additional information/resources
 

.github/MAINTAINER_GUIDELINES.md

@@ -17,11 +17,11 @@ Labels are important because they help us identify pull requests and ensure that
 
 Here is a brief summary of the most important labels:
 
-- `New Topic`: Entirely new documents
-- `Major Update`: Significant new info: new section in existing topic, etc.
-- `Technical`: Changes to technical content/code/processes/naming conventions (any change to technical content)
-- `Editorial`: Typos, grammatical inconsistencies, or minor rewrites
-- `small changes`: See [Small changes workflow](#small-changes-workflow)
+-  `New Topic`: Entirely new documents
+-  `Major Update`: Significant new info: new section in existing topic, etc.
+-  `Technical`: Changes to technical content/code/processes/naming conventions (any change to technical content)
+-  `Editorial`: Typos, grammatical inconsistencies, or minor rewrites
+-  `small changes`: See [Small changes workflow](#small-changes-workflow)
 
 We also use version labels when appropriate.
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,13 +6,13 @@ This pull request (PR) ...
 
 <!-- REQUIRED List the affected pages on devdocs.magento.com (URLs). Not needed for large numbers of files. -->
 
-- ...
+-  ...
 
 ## Links to Magento source code
 
 <!--  OPTIONAL - REMOVE THIS SECTION IF NOT USED. If this pull request references a file in a Magento codebase repository, add it here. -->
 
-- ...
+-  ...
 
 <!--
 If you are fixing a GitHub issue, note it using GitHub keyword format (https://help.github.com/en/articles/closing-issues-using-keywords#closing-an-issue-in-a-different-repository) to close the issue when this pull request is merged. Example: `Fixes #1234`

_checks/styles/style-rules-prod

@@ -23,7 +23,7 @@ exclude_rule 'MD026'
 exclude_rule 'MD027'
 exclude_rule 'MD028'
 rule 'MD029'
-exclude_rule 'MD030'
+rule 'MD030', :ul_single => 2, :ol_single => 1, :ul_multi => 2, :ol_multi => 1
 exclude_rule 'MD031'
 exclude_rule 'MD032'
 exclude_rule 'MD033'

_includes/cache/page-cache-checklists.md

@@ -1,21 +1,21 @@
 ## Cacheable page checklist
 
--   Pages use GET requests
+-  Pages use GET requests
 
--   Pages render only cacheable blocks
+-  Pages render only cacheable blocks
 
--   Pages render without sensitive private data; session and customer DTO objects are empty
+-  Pages render without sensitive private data; session and customer DTO objects are empty
 
--   Functionality specific to both current session (customer) and page should be written using JavaScript (e.g., related product listing should exclude items that are already in the shopping cart)
+-  Functionality specific to both current session (customer) and page should be written using JavaScript (e.g., related product listing should exclude items that are already in the shopping cart)
 
--   Model and block level should identify themselves for invalidation support
+-  Model and block level should identify themselves for invalidation support
 
--   Declare a custom [context variable]({{ page.baseurl }}/extension-dev-guide/cache/page-caching/public-content.html#configure-page-variations) if you plan to show different public content with the same URL
+-  Declare a custom [context variable]({{ page.baseurl }}/extension-dev-guide/cache/page-caching/public-content.html#configure-page-variations) if you plan to show different public content with the same URL
 
 ## Non-cacheable page checklist
 
--   Use POST requests to modify Magento state (e.g., adding to shopping cart, wishlist, etc.)
+-  Use POST requests to modify Magento state (e.g., adding to shopping cart, wishlist, etc.)
 
--   Blocks that can't be cached should be marked as non-cacheable in the layout. However, be aware that adding a non-cacheable block to a page prevents the full page cache from caching that page.
+-  Blocks that can't be cached should be marked as non-cacheable in the layout. However, be aware that adding a non-cacheable block to a page prevents the full page cache from caching that page.
 
--   Controllers that don't use layouts should set `no-cache` HTTP headers
+-  Controllers that don't use layouts should set `no-cache` HTTP headers

_includes/cache/page-cache-overview.md

@@ -2,18 +2,18 @@
 
 Caching is one of the most effective ways to improve website performance. Generally speaking, there are two methods of caching content:
 
--   Client-side (browser)
--   Server-side
+-  Client-side (browser)
+-  Server-side
 
 Retrieving stored ([cached](https://glossary.magento.com/cache)) content from a previous request for the same client instead of requesting files from your server every time someone visits your site is a more efficient use of network bandwidth.
 
 The Magento page cache library contains a simple PHP reverse proxy that enables full page caching out of the box. A reverse proxy acts as an intermediary between visitors and your application and can reduce the load on your server.
 
 We recommend using [Varnish]({{ page.baseurl }}/config-guide/varnish/config-varnish.html), but you can use Magento's default caching mechanism instead, which stores cache files in any of the following:
 
--   File system (You don't need to do anything to use file-based caching.)
--   [Database]({{ page.baseurl }}/extension-dev-guide/cache/partial-caching/database-caching.html)
--   [Redis]({{ page.baseurl }}/config-guide/redis/redis-pg-cache.html)
+-  File system (You don't need to do anything to use file-based caching.)
+-  [Database]({{ page.baseurl }}/extension-dev-guide/cache/partial-caching/database-caching.html)
+-  [Redis]({{ page.baseurl }}/config-guide/redis/redis-pg-cache.html)
 
 ## Cacheable and uncacheable pages {#cache-over-cacheable}
 
@@ -32,6 +32,6 @@ Do not configure content pages (i.e., catalog, product, and CMS pages) to be unc
 
 Reverse proxies serve "public" or shared content to more than one user. However, most Magento websites generate dynamic and personalized "private" content that should only be served to one user, which presents unique caching challenges. To address these challenges, Magento can distinguish between two types of content:
 
--   **[Public]({{ page.baseurl }}/extension-dev-guide/cache/page-caching/public-content.html)** - Public content is stored server side in your reverse proxy cache storage (e.g., file system, database, Redis, or Varnish) and is available to multiple customers. Examples of public content include header, footer, and category listing.
+-  **[Public]({{ page.baseurl }}/extension-dev-guide/cache/page-caching/public-content.html)** - Public content is stored server side in your reverse proxy cache storage (e.g., file system, database, Redis, or Varnish) and is available to multiple customers. Examples of public content include header, footer, and category listing.
 
--   **[Private]({{ page.baseurl }}/extension-dev-guide/cache/page-caching/private-content.html)** - Private content is stored client side (e.g., browser) and is specific to an individual customer. Examples of private content include wishlist, shopping cart, customer name, and address. You should limit stored private content to a small portion of the page's total content.
+-  **[Private]({{ page.baseurl }}/extension-dev-guide/cache/page-caching/private-content.html)** - Private content is stored client side (e.g., browser) and is specific to an individual customer. Examples of private content include wishlist, shopping cart, customer name, and address. You should limit stored private content to a small portion of the page's total content.

_includes/cloud/admin-ui-login-step.md

@@ -1 +1 @@
-1.  [Log in]({{ page.baseurl }}/cloud/onboarding/onboarding-tasks.html#admin) to the Magento Admin UI.
+1. [Log in]({{ page.baseurl }}/cloud/onboarding/onboarding-tasks.html#admin) to the Magento Admin UI.

_includes/cloud/cloud-fastly-manage-vcl-from-admin.md

@@ -14,7 +14,7 @@
 
 1. After the upload completes, refresh the cache according to the notification at the top of the page.
 
-{: .bs-callout .bs-callout-warning}
+{: .bs-callout-warning }
 The *Custom VCL snippets* UI option shows only the snippets added through the Admin UI. You must use the Fastly API to [manage custom snippets added through the API]({{ page.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-custom-vcl-snippets-using-the-api).
 
 ## Delete the custom VCL snippet
@@ -27,8 +27,7 @@ You can delete custom VCL snippet code from your Fastly configuration by uploadi
    -  Save the configuration.
    -  Upload the VCL to Fastly to apply your changes.
 
--  Use the Fastly API [Delete custom VCL snippet]({{ page.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-vcl) operation
- to delete the snippet completely, or submit a Magento support ticket to request deletion.
+-  Use the Fastly API [Delete custom VCL snippet]({{ page.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-vcl) operation to delete the snippet completely, or submit a Magento support ticket to request deletion.
 
 [Manage custom VCL snippets]: {{site.baseurl}}/common/images/cloud/cloud-fastly-manage-snippets.png
 {: width="650px"}