[DOC] Converging towards numpy doc standards V2 - issue #1540

[IRKnyazev]

Reference Issues/PRs

Fixes #1540

What does this implement/fix? Explain your changes.

Docstrings weren't following numpy style guide. Corrected the sections titled Arguments to be Parameters. In the base.y there is a use of Arguments however this is correct, classes can use a section with this title.

Does your contribution introduce a new dependency? If yes, which one?

No.

Any other comments?

I found the first instance as described by @aadya940 then used the case-sensitive search in vscode for the remaining inconsistencies.
This is a continuation of an earlier PR for which not all changes were accepted.

PR checklist

For all contributions

• I've added myself to the list of contributors. Alternatively, you can use the @all-contributors bot to do this for you.
• The PR title starts with either [ENH], [MNT], [DOC], [BUG], [REF], [DEP] or [GOV] indicating whether the PR topic is related to enhancement, maintenance, documentation, bugs, refactoring, deprecation or governance.

[aeon-actions-bot]

Thank you for contributing to aeon

I have added the following labels to this PR based on the title: [ $\color{#F3B9F8}{\textsf{documentation}}$ ].
I have added the following labels to this PR based on the changes made: [ $\color{#31FCCD}{\textsf{forecasting}}$, $\color{#379E11}{\textsf{networks}}$ ]. Feel free to change these if they do not properly represent the PR.

The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.

If our pre-commit code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.

Don't hesitate to ask questions on the aeon Slack channel if you have any.

PR CI actions

These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.

• Run pre-commit checks for all files
• Run all pytest tests and configurations
• Run all notebook example tests
• Run numba-disabled codecov tests
• Stop automatic pre-commit fixes (always disabled for drafts)
• Push an empty commit to re-run CI checks

[TonyBagnall]

LGTM, thanks

[TonyBagnall]

@all-contributors add @IRKnyazev for docs

[allcontributors]

@TonyBagnall

@IRKnyazev already contributed before to doc