[kimclow]

Removes the repeated “added” from the documentation for WP_Error::$additional_data.

Before: “Stores previously added data added for error codes, oldest-to-newest by code.”

After: “Stores previously added data for error codes, oldest-to-newest by code.”

Documentation only; no executable code changes.

Trac ticket: https://core.trac.wordpress.org/ticket/65860

Validation

Codex checked the prepared local change: PHP syntax and whitespace checks passed, and executable PHP tokens were identical before and after the edit.

Use of AI Tools

AI assistance: Yes
Tool(s): Codex
Model(s): GPT-6
Used for: Finding the repeated word, checking related pull requests, preparing the correction and PR description, and validating the local change.

This is my first ever PR, so I asked Codex to help me through the steps. I reviewed the wording and made the submitted edit myself.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props kimclow.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.