[DOC] Programmatically fix (all) typos

docs/source/_static/js/dynamic_table.js

@@ -13,7 +13,7 @@ function includeHTML() {
   z = document.getElementsByTagName("*");
   for (i = 0; i < z.length; i++) {
 	elmnt = z[i];
-	/*search for elements with a certain atrribute:*/
+	/*search for elements with a certain attribute:*/
 	file = elmnt.getAttribute("w3-include-html");
 	if (file) {
 	  /*make an HTTP request using the attribute value as the file name:*/

docs/source/api_reference/datasets.rst

@@ -13,7 +13,7 @@ The ``datasets`` module contains:
 Loaders from dataset repositories
 ---------------------------------
 
-These loaders access dataset respositories on the internet and fetch one or multiple
+These loaders access dataset repositories on the internet and fetch one or multiple
 datasets from there, individual datasets specifiable as strings.
 
 These loaders can be used to access reference datasets for benchmarking.

docs/source/api_reference/dists_kernels.rst

@@ -181,7 +181,7 @@ See docstring of ``AggrDist`` and ``FlatDist``.
     AggrDist
     FlatDist
 
-Advanced time series kernels that cannot be expressed as aggrgates or flat applicates:
+Advanced time series kernels that cannot be expressed as aggregates or flat applicates:
 
 .. currentmodule:: sktime.dists_kernels.gak
 

docs/source/api_reference/file_specifications/ts.rst

@@ -55,11 +55,11 @@ String identifiers refer to strings beginning with ``@`` in the file.
       See :ref:`subsection on metadata block <metadata description>` for further details.
 3. A dataset block.
       It contains list of float values that represent the dataset. In the simplest case (when timestamps are absent),
-      the values for a series are expressed in a comma-seperated list and the index of each value is relative to its
+      the values for a series are expressed in a comma-separated list and the index of each value is relative to its
       position in the list (0, 1, ..., m). An instance may contain 1 to many dimensions, where instances are
       line-delimited and dimensions within an instance are colon-delimited (:). In case timestamps are present,
       individual data of the series is enclosed within round brackets as ``(YYYY-MM-DD HH:mm:ss,<value>)``.
-      The response variable is at the end of each instance and is seperated via a colon.
+      The response variable is at the end of each instance and is separated via a colon.
       To understand data representation, visit `loading data`_.
 
 Here is an extract from `Basic Motion.ts`_ that shows all three blocks:
@@ -189,7 +189,7 @@ Here is a short description of every column found in the table:
     * - ``@classlabel``
       - Whether class labels are present.
       - ``false`` / ``true`` ``<string-1> <string-2> ..``
-      - Exclusive to classification data; when ``true``, also contains space-seperated int/strings as labels.
+      - Exclusive to classification data; when ``true``, also contains space-separated int/strings as labels.
       - ``true Standing Running Walking Badminton``
     * - ``@data``
       - Marks the beginning of data.
@@ -237,7 +237,7 @@ Few points to keep in mind while creating the dataset:
 
    b. Classification-based: add ``@classlabel`` identifier.
       If there is no response variable it will have a value of ``false``. If ``true``, you can optionally provide the class labels
-      in space seperated manner:
+      in space separated manner:
 
       - eg: Three string labels: ``@classlabel true good bad neutral``
       - eg: Two integer labels:  ``@classlabel true 0 1``

docs/source/changelog.rst

@@ -391,7 +391,7 @@ Benchmarking, Metrics, Splitters
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 * [ENH] speed up ``BaseSplitter`` boilerplate (:pr:`5063`) :user:`fkiraly`
-* [ENH] Allow unrestriced ID string for ``BaseBenchmarking`` (:pr:`5130`) :user:`hazrulakmal`
+* [ENH] Allow unrestricted ID string for ``BaseBenchmarking`` (:pr:`5130`) :user:`hazrulakmal`
 
 Data loaders
 ^^^^^^^^^^^^
@@ -913,7 +913,7 @@ Users should use a new, temporary ``legacy_interface`` argument to handle the ch
 * Users - change period. The two forecaster methods ``predict_quantiles`` and ``predict_intervals``
   will have a new boolean argument, ``legacy_interface``. If ``True``, the methods
   produce returns with the current naming convention. If ``False``, the methods produce
-  returns with the future, post-change naming covention.
+  returns with the future, post-change naming convention.
 * Users - early and late phase. In the early phase (0.21.X), the default value of ``legacy_interface``
   will be ``True``. In the late phase (0.22.X), the default value of ``legacy_interface`` will be ``False``.
   This change of default will occur in 0.22.0, and may be breaking for users who do not specify the argument.
@@ -1389,7 +1389,7 @@ Probability distributions
 * specification of default sample sizes for Monte Carlo approximations now
   use the ``scikit-base`` config system
 * a ``quantile`` method was added, which returns a table of quantiles in
-  the same format as ``BaseForecaster.predict_quantiles`` returne quantile forecasts
+  the same format as ``BaseForecaster.predict_quantiles`` return quantile forecasts
 * a ``ppf`` method was added for returning quantiles
 
 Enhancements
@@ -1439,7 +1439,7 @@ Time series distances and kernels
 Transformations
 ^^^^^^^^^^^^^^^
 
-* [ENH] remove unneccesary conversion in ``TSFreshFeatureExtractor`` (:pr:`4571`) :user:`fkiraly`
+* [ENH] remove unnecessary conversion in ``TSFreshFeatureExtractor`` (:pr:`4571`) :user:`fkiraly`
 
 Testing framework
 ^^^^^^^^^^^^^^^^^
@@ -2500,7 +2500,7 @@ Data types, checks, conversions
 * [ENH] ``dask`` mtypes - part 1, ``Series`` (:pr:`3554`) :user:`fkiraly`
 * [ENH] ``dask`` mtypes - part 2, ``Panel`` and ``Hierarchical`` (:pr:`4011`) :user:`fkiraly`
 * [ENH] speed up mtype check for ``pandas`` based mtypes with ``pd.PeriodIndex`` (:pr:`3991`) :user:`fkiraly`
-* [ENH] improve performance of ``pandas`` based panel and hierachical mtype checks (:pr:`3935`) :user:`danbartl`
+* [ENH] improve performance of ``pandas`` based panel and hierarchical mtype checks (:pr:`3935`) :user:`danbartl`
 * [ENH] Speed up hierarchical checks and unify with panel approach (:pr:`4061`) :user:`danbartl`
 
 Distances, kernels
@@ -3741,7 +3741,7 @@ Highlights
 
 * forecasting reducers constructed via ``make_reduction`` now fully support global/hierarchical forecasting (:pr:`2486`) :user:`danbartl`
 * forecasting metric classes now fully support hierarchical data and hierarchy averaging via ``multilevel`` argument (:pr:`2601`) :user:`fkiraly`
-* probabilisitic forecasting functionality for ``DynamicFactor``, ``VAR`` and ``VECM`` (:pr:`2925`, :pr:`3105`) :user:`AurumnPegasus`, :user:`lbventura`
+* probabilistic forecasting functionality for ``DynamicFactor``, ``VAR`` and ``VECM`` (:pr:`2925`, :pr:`3105`) :user:`AurumnPegasus`, :user:`lbventura`
 * ``update`` features for ``AutoARIMA``, ``BATS``, ``TBATS``, and forecasting tuners (:pr:`3055`, :pr:`3068`, :pr:`3086`) :user:`fkiraly`, :user:`jelc53`
 * new transformer: ``ClearSky`` transformer for solar irradiance time series (:pr:`3130`) :user:`ciaran-g`
 * new transformer: ``Filter`` transformer for low/high-pass and band filtering, interfaces ``mne`` ``filter_data`` (:pr:`3067`) :user:`fkiraly`, :user:`sveameyer13`
@@ -4628,7 +4628,7 @@ Distances, kernels
 Forecasting
 ^^^^^^^^^^^
 
-* [ENH] Extended sliding and expanding window splitters to allow timdelta forecasting horizon (:pr:`2551`) :user:`khrapovs`
+* [ENH] Extended sliding and expanding window splitters to allow timedelta forecasting horizon (:pr:`2551`) :user:`khrapovs`
 * [ENH] Removed ``interval_width`` parameter of Prophet (:pr:`2630`) :user:`phershbe`
 
 Time series classification
@@ -4804,7 +4804,7 @@ Clustering
 Data types, checks, conversions
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-* [BUG] fixing direct conversions from/to ``numpyflat`` mtype being overriden by indirect ones (:pr:`2517`) :user:`fkiraly`
+* [BUG] fixing direct conversions from/to ``numpyflat`` mtype being overridden by indirect ones (:pr:`2517`) :user:`fkiraly`
 
 Distances, kernels
 ^^^^^^^^^^^^^^^^^^
@@ -4919,7 +4919,7 @@ Highlights
 * GSoC 2022 application instructions - apply by Apr 19 for GSoC with sktime! (:pr:`2373`) :user:`lmmentel` :user:`Lovkush-A` :user:`fkiraly`
 * enhancements and bugfixes for probabilistic and hierarchical forecasting features introduced in 0.11.0
 * reconciliation transformers for hierarchical predictions (:pr:`2287`, :pr:`2292`) :user:`ciaran-g`
-* pipeline, tuning and evaluation compabitility for probabilistic forecasting (:pr:`2234`, :pr:`2318`) :user:`eenticott-shell` :user:`fkiraly`
+* pipeline, tuning and evaluation compatibility for probabilistic forecasting (:pr:`2234`, :pr:`2318`) :user:`eenticott-shell` :user:`fkiraly`
 * interface to ``statsmodels`` ``SARIMAX`` (:pr:`2400`) :user:`TNTran92`
 * reduction with transform-on-y predictors (e.g., lags, window summaries), and for hierarchical data (:pr:`2396`) :user:`danbartl`
 
@@ -5030,7 +5030,7 @@ Documentation
 ~~~~~~~~~~~~~
 
 * [DOC] fix 0.11.0 release note highlights formatting (:pr:`2310`) :user:`fkiraly`
-* [DOC] typo fix contsructor -> constructor in extension templates (:pr:`2348`) :user:`fkiraly`
+* [DOC] typo fix constructor -> constructor in extension templates (:pr:`2348`) :user:`fkiraly`
 * [DPC] fixed the issue with ``'docs/source/developer_guide/testing_framework.rst'`` (:pr:`2335`) :user:`0saurabh0`
 * [DOC] Updated conda installation instructions (:pr:`2365`) :user:`RISHIKESHAVAN`
 * [DOC] updated extension templates: link to docs and reference to `check_estimator` (:pr:`2303`) :user:`fkiraly`
@@ -5221,7 +5221,7 @@ Fixed
 ~~~~~
 
 *  [BUG] fixed state change caused by `ThetaForecaster.predict_quantiles` (:pr:`2108`) :user:`fkiraly`
-*  [BUG] ``_make_hierachical`` is renamed to ``_make_hierarchical`` (typo/bug) issue #2195 (:pr:`2196`) :user:`Vasudeva-bit`
+*  [BUG] ``_make_hierarchical`` is renamed to ``_make_hierarchical`` (typo/bug) issue #2195 (:pr:`2196`) :user:`Vasudeva-bit`
 *  [BUG] fix wrong output type of ``PaddingTransformer._transform`` (:pr:`2217`) :user:`fkiraly`
 *  [BUG] fixing ``nested_dataframe_has_nans`` (:pr:`2216`) :user:`fkiraly`
 *  [BUG] Testing vectorization for forecasters, plus various bugfixes (:pr:`2188`) :user:`fkiraly`
@@ -5590,7 +5590,7 @@ Testing module
 * [ENH] Test refactor with scenarios (:pr:`1833`) :user:`fkiraly`
 * [ENH] Test scenarios for advanced testing	(:pr:`1819`) :user:`fkiraly`
 * [ENH] pytest conditional fixtures	(:pr:`1839`) :user:`fkiraly`
-* [ENH] Test enhacements documentation (:pr:`1922`) :user:`fkiraly`
+* [ENH] Test enhancements documentation (:pr:`1922`) :user:`fkiraly`
 * [ENH] split tests in series_as_features into classification and regression (:pr:`1959`) :user:`tonybagnall`
 * [ENH] Testing for metadata returns of ``check_is_mtype`` (:pr:`1748`) :user:`fkiraly`
 * [ENH] Extended deep_equals, with precise indication of why equality fails	(:pr:`1844`) :user:`fkiraly`
@@ -5610,7 +5610,7 @@ Maintenance
 
 * [MNT] Switch the extra dependency from `fbprophet` to `prophet` (:pr:`1958`) :user:`lmmentel`
 * [MNT] Updated code dependency version, i.e. `numpy` and `statsmodels` to reduce dependency conflicts (:pr:`1921`) :user:`lmmentel`
-* [MNT] Move all the CI/CD worfklows over to github actions and drop azure pipelines and appveyor (:pr:`1620`, :pr:`1920`) :user:`lmemntel`
+* [MNT] Move all the CI/CD workflows over to github actions and drop azure pipelines and appveyor (:pr:`1620`, :pr:`1920`) :user:`lmemntel`
 * [MNT] Refactor legacy test config	(:pr:`1792`) :user:`lmmentel`
 * [FIX] Add missing init files (:pr:`1695`) :user:`mloning`
 * [MNT] Add shellcheck to pre-commit (:pr:`1703`) :user:`mloning`
@@ -5998,7 +5998,7 @@ Fixed
 * [BUG] incorrect/missing weighted geometric mean in forecasting ensemble (:pr:`1370`) :user:`fkiraly`
 * [BUG] :pr:`1469`: stripping names of index X and y  (:pr:`1493`) :user:`boukepostma`
 * [BUG] W-XXX frequency bug from :pr:`866` (:pr:`1409`) :user:`xiaobenbenecho`
-* [BUG] Pandas.NA for unpredictible insample forecasts in AutoARIMA (:pr:`1442`) :user:`IlyasMoutawwakil`
+* [BUG] Pandas.NA for unpredictable insample forecasts in AutoARIMA (:pr:`1442`) :user:`IlyasMoutawwakil`
 * [BUG] missing :code:`extract_path` in :code:`_data_io` (:pr:`1475`) :user:`yairbeer`
 * [BUG] Refactor sktime/.../_panels/_examples.py for tsai compatibility (:pr:`1453`) :user:`bobbys-dev`
 * [BUG] Grid/random search tag fix (:pr:`1455`) :user:`fkiraly`
@@ -6173,7 +6173,7 @@ Fixed
 * [DOC] Update ColumnwiseTransformer and TabularToSeriesAdaptor docstrings (:pr:`1322`) :user:`GuzalBulatova`
 * [DOC] Update transformer docstrings (:pr:`1314`) :user:`RNKuhns`
 * [DOC] Description and link to cosine added (:pr:`1326`) :user:`AreloTanoh`
-* [DOC] naive forcasting docstring edits (:pr:`1333`) :user:`AreloTanoh`
+* [DOC] naive foreasting docstring edits (:pr:`1333`) :user:`AreloTanoh`
 * [DOC] Update .all-contributorsrc (:pr:`1336`) :user:`pul95`
 * [DOC] Typo in transformations.rst fixed (:pr:`1324`) :user:`AreloTanoh`
 * [DOC] Add content to documentation guide for use in docsprint (:pr:`1297`) :user:`RNKuhns`

docs/source/conf.py

@@ -399,7 +399,7 @@ def adds(pth):
 nbsphinx_allow_errors = False  # False
 nbsphinx_timeout = 600  # seconds, set to -1 to disable timeout
 
-# add Binder launch buttom at the top
+# add Binder launch button at the top
 current_file = "{{ env.doc2path( env.docname, base=None) }}"
 
 # make sure Binder points to latest stable release, not main

docs/source/contributing/reviewer_guide.rst

@@ -29,8 +29,8 @@ Code
 
 .. _reviewer_guide_doc:
 
-Documenation
-============
+Documentation
+=============
 
 * Are the docstrings complete and understandable to users?
 * Do they follow the NumPy format and sktime conventions?

docs/source/developer_guide/dependencies.rst

@@ -23,7 +23,7 @@ We try to keep the number of core dependencies to a minimum and rely on other pa
 Handling soft dependencies
 --------------------------
 
-This section explains how to handle existing soft depencies.
+This section explains how to handle existing soft dependencies.
 For adding a new soft dependency, see the section "adding a new soft dependency".
 
 Soft dependencies in ``sktime`` should usually be isolated to estimators.
@@ -53,7 +53,7 @@ Estimators with a soft dependency need to ensure the following:
    See ``forecasting.arima.ARIMA`` as as an example. If concerned that skipping the test will reduce test coverage,
    consider exposing the doctest example as a pytest test function instead, see below how to handle soft dependencies in pytest functions.
 *  Decorate all ``pytest`` tests that import soft dependencies with a ``@pytest.mark.skipif(...)`` conditional on a check to ``_check_soft_dependencies``
-   for your new soft depenency, with ``severity="none"``.  Be sure that all soft dependencies imported for testing are imported within the test function itself,
+   for your new soft dependency, with ``severity="none"``.  Be sure that all soft dependencies imported for testing are imported within the test function itself,
    rather than for the whole module!  This decorator will then skip your test, including imports, unless the system has the required packages installed.
    This prevents crashes for any users running ``check_estimator`` on all estimators, or a full local ``pytest`` run without the required soft dependency.
    See the tests in ``forecasting.tests.test_pmdarima`` for a concrete example.
@@ -85,7 +85,7 @@ lower bounds for a single package when present in different extras, and can be m
 
 Upper bounds will be preferred to be set up as the next ``minor`` release of the
 packages, as ``patch`` updates should never contain breaking changes by convention of
-semantic versioning. For stable packages, next ``major`` verion can be used as well.
+semantic versioning. For stable packages, next ``major`` version can be used as well.
 
 Upper bounds will be automatically updated using ``dependabot``, which has been set up
 to run daily based on releases on ``PyPI``. The CI introducing newer upper bound will be

docs/source/developer_guide/deprecation.rst

@@ -81,7 +81,7 @@ The release manager process happens at every release and is as follows:
 Special deprecations
 ====================
 
-This section outlines the deprecation process for some advaned cases.
+This section outlines the deprecation process for some advanced cases.
 
 Deprecating tags
 ----------------

docs/source/developer_guide/documentation.rst

@@ -99,8 +99,8 @@ Again developers are encouraged to add important content to the user guide and l
 See Also
 ~~~~~~~~
 
-This section should reference other ``sktime`` code artifcats related to the code artifact being documented by the docstring. Developers should use
-judgement in determining related code artifcats. For example, rather than listin all other performance metrics, a percentage error based performance metric
+This section should reference other ``sktime`` code artifacts related to the code artifact being documented by the docstring. Developers should use
+judgement in determining related code artifacts. For example, rather than listin all other performance metrics, a percentage error based performance metric
 might only list other percentage error based performance metrics.  Likewise, a distance based classifier might list other distance based classifiers but
 not include other types of time series classifiers.
 
@@ -149,7 +149,7 @@ Examples
 
 Most code artifacts in sktime should include an examples section. At a minimum this should include a single example that illustrates basic functionality.
 The examples should use either a built-in sktime dataset or other simple data (e.g. randomly generated data, etc) generated using an sktime dependency
-(e.g. NumPy, pandas, etc) and whereever possible only depend on sktime or its core dependencies. Examples should also be designed to run quickly where possible.
+(e.g. NumPy, pandas, etc) and wherever possible only depend on sktime or its core dependencies. Examples should also be designed to run quickly where possible.
 For quick running code artifacts, additional examples can be included to illustrate the affect of different parameter settings.
 
 Examples of Good sktime Docstrings

docs/source/developer_guide/testing_framework.rst

@@ -299,12 +299,12 @@ This base class defines generics such as ``is_applicable``, or tag handling, for
 Scenarios should usually define:
 
 * an ``args`` parameter: a dictionary, with arbitrary keys (usually names of methods).
-* The ``args`` parameter may be set as a class variable, or set by the contructor.
+* The ``args`` parameter may be set as a class variable, or set by the constructor.
 * optionally, a ``default_method_sequence`` and a ``default_arg_sequence``, lists of strings.
   These define the sequence in which methods are called, with which argument set,
   if ``run`` is called. Both may be class variables, or object variable set in the constructor.
 * side note: a ``method_sequence`` and ``arg_sequence`` can also be specified in ``run``.
-  If not passed, defaulting will take place (first to each other, then to the ``detault_etc`` variables)
+  If not passed, defaulting will take place (first to each other, then to the ``default_etc`` variables)
 * optionally, a ``_tags`` dictionary, which is a ``BaseObject`` tags dictionary and behaves exactly like that of estimators.
 * optionally, a ``get_args`` method which allows to override key retrieval from ``args``.
   For instance, to specify rules such as "if the key starts with ``predict_``, always return ..."

docs/source/get_involved/code_of_conduct.rst

@@ -34,7 +34,7 @@ sktime is a community-oriented and -led project.
 We value the involvement of everyone in the community, and strive to be an open
 community. We commit to provide fair and rewarding opportunities for everyone without
 restriction, to participate, learn, and become leaders of the community. We expect from
-leaders of our community to create such opportunities for others, and we stronly encourage
+leaders of our community to create such opportunities for others, and we strongly encourage
 all members of our community to create opportunities as have been created for them.
 
 We are committed to scientific quality and strive to be an open forum on matters

docs/source/get_involved/governance.rst

@@ -98,7 +98,7 @@ algorithm. They have the same voting rights as core developers with
 regard to their algorithm.
 
 In sktime, algorithms are encapsulated in classes with specific
-interface requirements and are called estimators. To faciliate
+interface requirements and are called estimators. To facilitate
 maintainership questions, we try to write algorithms in separate files
 when possible.