Remove duplicate words in Javadoc and test comments

[growfrow]

Remove duplicated words in Javadoc and test comments

Testing done

No automated tests because the changes only affect Javadoc comments. Confirmed that no new warnings or errors are reported by Javadoc generation.

Proposed changelog entries

N/A

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

N/A

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[MarkEWaite]

Fixes in documentation. Thanks.

[MarkEWaite]

The duplicated words should not be removed from our copy of the YahooUI JavaScript library because it will make later comparisons with upstream more difficult.

I've completed the "Testing done" section of the pull request template. It is not optional. I also checked that no new errors or warnings were generated by the Javadoc changes.

[MarkEWaite]

Thanks for the pull request @growfrow. Could you complete the requested changes so that it can be reviewed again?

[MarkEWaite]

When submitting future pull requests, please be sure to complete the pull request template. It assures that you've done the things that are needed for pull request review and it helps the maintainers understand what is intended by the change.

[growfrow]

When submitting future pull requests, please be sure to complete the pull request template. It assures that you've done the things that are needed for pull request review and it helps the maintainers understand what is intended by the change.

Thank you for your suggestion.

[MarkEWaite]

Thanks. Changes look good to me.