Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Updated the typos spell checker from v1.28.0 to v1.39.2. The newer version detected 13 typos across Python and Markdown files that are now fixed.

Version Update:

• bin/install.py: Updated typos download URLs to v1.39.2 for Linux x86_64 and Darwin arm64

Configuration:

• pyproject.toml: Added false positives to ignore list:
  • tpe/TPE - Tree-structured Parzen Estimator algorithm names (hyperopt/optuna)
  • indx - Intentional shorthand for index
  • livin' - Song lyrics with apostrophe

Typo Fixes:

• compatiblility → compatibility (CHANGELOG.md)
• secury → security (docs)
• metrix_prefix → metric_prefix (mlflow/models/evaluation/base.py)
• DBConncet → DBConnect (mlflow/pyfunc/init.py)
• decsribes → describes (mlflow/pyfunc/model.py)
• avg_metris → avg_metrics (mlflow/pyspark/ml/init.py)
• loosing → losing (mlflow/transformers/peft.py)
• confg → config (tests, 4 occurrences)
• retreiver/retriver → retriever (tests, 12 occurrences)
• Additional fixes in examples/README files

Scope:
Only files checked by the pre-commit typos hook (Python and Markdown files) are modified. Changes to other file types (notebooks, JS, CSS, CSV) were not included.

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

Pre-commit typos hook passes on all Python and Markdown files.

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.