Correct spelling

[ravi-chandra3197]

Description (*)

correct spelling

Fixed Issues (if relevant)

1. magento/magento2#<issue_number>: Issue title

Manual testing scenarios (*)

N/A

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[magento-engcom-team]

Hi @ravi-chandra3197. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[magento-engcom-team]

Hi @VladimirZaets, thank you for the review.
ENGCOM-3656 has been created to process this Pull Request

[orlangur]

@ravi-chandra3197 please do not produce useless merge commits.

[ravi-chandra3197]

Hello @orlangur
Any suggestion for how to remove merge commits.

[orlangur]

@ravi-chandra3197 sure, here is simple way: https://coderwall.com/p/ysor6a/git-merge-squash-for-merging-without-commit-history

[ravi-chandra3197]

@orlangur Thanks for the response but my concern is how to remove commit from an existing branch or rewrite branch history.

[orlangur]

@ravi-chandra3197 simply squash all changes into single commit and force push as provided article shows.

[ravi-chandra3197]

Hello, @orlangur I have removed merge commits. can review it.

[orlangur]

@ravi-chandra3197 very nice, thank you! 👍

[magento-engcom-team]

Hi @ravi-chandra3197. Thank you for your contribution.
We will aim to release these changes as part of 2.3.1.
Please check the release notes for final confirmation.