docs: fix grammar in Azure generator docstring examples

[Aarkin7]

Related Issues

N/A — trivial docstring grammar fix.

Proposed Changes:

Fixes a missing word and a stray double space in the docstring code examples for AzureOpenAIGenerator and AzureOpenAIChatGenerator:

• "<this a model name, e.g. gpt-4.1-mini>" → "<this is a model name, e.g. gpt-4.1-mini>" in haystack/components/generators/azure.py

• "<this a model name, e.g. gpt-4.1-mini>" → "<this is a model name, e.g. gpt-4.1-mini>" in haystack/components/generators/chat/azure.py

These docstrings are rendered in the public API reference and are commonly copy-pasted by users setting up Azure OpenAI deployments.

How did you test it?

Visual review of the diff. No behavior change — string-literal content inside docstring code blocks. No unit tests apply.

Notes for the reviewer

Release note added under releasenotes/notes/ following the precedent set by codespell-d4a32b9c589ca26e.yaml. Happy to drop it if you'd prefer to label the PR ignore-for-release-notes.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run pre-commit hooks and fixed any issue.

[vercel]

@Aarkin7 is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[sjrl]

Thanks!

[sjrl]

@Aarkin7 thanks for the contribution! Please make sure to sign the CLA agreement #11337 (comment) so we can accept your contribution.

[Aarkin7]

Thanks for the fast turnaround @sjrl. Glad to get a first contribution in. Will keep an eye out for more.