Copyedit: change "coping" to "copying"

[ckd]

Description (*)

Minor copyedit to correct spelling of "copying"

Related Pull Requests

n/a

Fixed Issues (if relevant)

n/a

Manual testing scenarios (*)

n/a

Questions or comments

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)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Copyedit: change "coping" to "copying" #39311: Copyedit: change "coping" to "copying"

[m2-assistant]

Hi @ckd. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Hotel]

@magento create issue

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Hello @ckd,

Thanks for the contribution!

The changes seem good to us but please fix the static test failures.

Also I want to suggest to fix a typo in the below line as well (startegt to strategy):

magento2/app/code/Magento/ImportExport/Model/Import.php

Line 82 in 0057e06

* Validation startegt field name

[ckd]

Hi @engcom-Hotel! Added the additional typo correction to the PR, but the static test failures seem to be upstream and unrelated to this change

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Thanks @ckd, for making the changes.

But we are still having static test failures. Please fix those.

[ckd]

@engcom-Hotel those failures are out of scope for this PR, they need to be fixed upstream

[engcom-Hotel]

Hello @ckd, we can see the copywrite failures on the files in this PR. You just need to make the changes in the file as follows:

Copyright [year code created] Adobe All Rights Reserved. 

[engcom-Hotel]

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B, Unit Tests

[engcom-Hotel]

Hello @ckd,

Thanks for fixing the issues!

But we are still having some static test failures. Please fix those and then run all tests to verify.

Thanks

[engcom-Hotel]

Hello @ckd,

We are picking this PR for further processing.

Thanks

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

@magento run Static Tests

[engcom-Bravo]

Hi @ckd,

Thanks for the collaboration & contribution!

✔️ QA Passed

Thanks.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests B2B, Functional Tests CE

[engcom-Dash]

Few test failures in recent 2 builds for functional CE are not consistent. For Functional B2B the consitent test failure is the known issue and Jira raised for the same. Hence moving this PR to Merge in Progress

Build 1:
Functional Tests B2B: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39307/e460afd8d6a37b08d8a9c594bb5fbaba/Functional/allure-report-b2b/index.html#categories/45dbe0d46e96664d663d093b248a272b/6928e81e6c8450d2/

Build 2:
Functional Tests B2B: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39307/eccb216ff0aa7c354ca445f7d101fdf3/Functional/allure-report-b2b/index.html#categories/45dbe0d46e96664d663d093b248a272b/4f01d090add31805/

Build 1:
Functiona Tests CE: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39307/fd46e1d9d69254dadaabc1dfb9a0903b/Functional/allure-report-ce/index.html#categories/a644910ae0cb11e839a98baa21929b76/b2f13416764bbc1f/

Build 2:
Functiona Tests CE: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39307/e7e360d534b06b7bd6e8a670311d2c1b/Functional/allure-report-ce/index.html#categories/c5e17feaf80ce819bae3628b8541c514/20be3b24b1e79581/

Known Issue: AdminValidateMixedNestedCategoryInWidgetTest https://jira.corp.adobe.com/browse/ACQE-7641