[DOC] Fix typos and enhance clarity in getting_started.md

[PoojasPatel013]

Title: [DOC] Fix typos, formatting inconsistencies, and garbled text in getting_started.md

Description

While working through the getting_started.md guide to familiarize myself with the project, I encountered a few typos, a formatting issue, and a sentence that appeared to be corrupted by a copy-paste error.

This PR addresses these issues to improve the linguistic quality and visual consistency of the documentation. Ensuring the "Getting Started" guide is error-free is crucial as it is often the first touchpoint for new developers adopting the library.

Detailed Changes

1. Fix Garbled Text in "Segmentation" Description (Line 34)

Issue: The description for the Segmentation module was unclear and contained the phrase "sofind areas...", which appears to be a text-editor artifact or copy-paste error.
Fix: Replaced the confusing sentence with a precise definition.

Before: "...sofind areas..."
After: "...series into regions that are dissimilar to each other"

2. Grammar Correction (Line 40)

Issue: A redundant article was present in the sentence structure.
Fix: Removed the extra "a".

Before: "...where a either a single series..."
After: "...where either a single series..."

3. List Indentation Fix (Line 45)

Issue: The "Networks" list item was not indented correctly, causing it to break the visual hierarchy of the module list.
Fix: Adjusted whitespace to align "Networks" with the preceding and succeeding list items.

4. Spelling Correction (Line 203)

Issue: The word "multivariate" was misspelled.
Fix: Corrected spelling.

Before: "...mutlivariate..."
After: "...multivariate..."

[aeon-actions-bot]

Thank you for contributing to aeon

I did not find any labels to add based on the title. Please add the [ENH], [MNT], [BUG], [DOC], [REF], [DEP] and/or [GOV] tags to your pull requests titles. For now you can add the labels manually.

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 mypy typecheck tests
• 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)
• Disable numba cache loading
• Regenerate expected results for testing
• Push an empty commit to re-run CI checks