Fix a few typos in PHPDoc comments

[artttj]

Description (*)

Fix a few typos in PHPDoc comments:

\Magento\ConfigurableProduct\Block\Product\View\Type::_getAdditionalConfig() \Magento\ConfigurableProduct\Block\Adminhtml\Product\Composite\Fieldset\Configurable::_getAdditionalConfig() 

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)
• 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] Fix a few typos in PHPDoc comments #40042: Fix a few typos in PHPDoc comments

[m2-assistant]

Hi @artttj. Thank you for your contribution!
Here are some useful tips on 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 give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ 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.

[artttj]

@magento run all tests

[artttj]

@magento run all tests

[artttj]

@magento run all tests

[artttj]

@magento run all tests

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Hello @artttj,

Thanks for the contribution!

As I can see in this PR, you have tried to fix some typos but we have some static test failures. We request you to fix those.

Other failures seems flaky to me.

Thanks

[engcom-Dash]

Hello @artttj

I wanted to check if you are working on the static failures. If not, Can I take care of them? Just let me know what works best for you.

[engcom-Dash]

Hello @artttj I am taking care of the changes. Thank You!

[engcom-Dash]

@magento run all tests

[artttj]

@engcom-Hotel I have fixed the static failures. Other failures are not related to this PR changes hence moving this PR for review.

Thanks for resolving, I appreciate it!

[engcom-Bravo]

Hi @artttj,

Thanks for the collaboration & contribution!

✔️ QA Passed

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks.

[engcom-Bravo]

@magento create issue

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

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

[engcom-Dash]

The consistent Functional B2B Tests failure is known issue and Jira has been raised for the same. Other failures are inconsistent and flaky. They neither part of PR nor failing because of the PR changes.

Build 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38809/1112b7f0a864e9f9477c9307b2efd19b/Functional/allure-report-b2b/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Build 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38809/308fb65189ccbeb2751f3ff22143f866/Functional/allure-report-b2b/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Known Issue: StorefrontProductNoLongerVisibleInWishlistOnceUserUnassignedFromCompanyTest ACQE-8287

The Functional EE failures are inconsistent and flaky. They neither part of PR nor failing because of the PR changes.

Build 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38809/b7e6412fff40d0e4e1eb49b640aed50f/Functional/allure-report-ee/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Build 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38809/bf65c242189680c6b719e0b707abea40/Functional/allure-report-ee/index.html#categories/bdbf199525818fae7a8651db9eafe741

Hence moving this PR in Merge In Progress.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

Hi @artttj ,

Thank you for your contribution! I just wanted to let you know that your pull request is now in the merge in progress stage. From this point onward, our team will take care of the remaining steps.

No further action is required from your end.

Thanks!