Update provider titles

[mrubens]

Important

Add sidebar_label to provider documentation files for improved navigation.

• Documentation Updates:
  • Added sidebar_label to the front matter of provider documentation files for better navigation.
  • Affected files include anthropic.md, bedrock.md, deepseek.md, and gemini.md among others.

^{This description was created by for b1c1bea. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to b1c1bea in 58 seconds

More details

• Looked at 219 lines of code in 15 files
• Skipped 0 files when reviewing.
• Skipped posting 11 drafted comments based on config settings.

1. docs/providers/openai-compatible.md:28

• Draft comment:
  Typo: 'Chooose' should be 'Choose'.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

2. PULL_REQUEST:1

• Draft comment:
  The PR description is empty. Please provide a detailed description including what is changed, why, and how it was tested.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

3. docs/providers/openai-compatible.md:28

• Draft comment:
  Typo: 'Chooose a model' should be corrected to 'Choose a model'.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

4. docs/providers/deepseek.md:23

• Draft comment:
  There's an inconsistency in the bullet indentation and spacing in the Supported Models section. Line 22 uses three spaces after the asterisk, but Line 23 appears to use a tab or different spacing. Consider standardizing the spacing for better readability.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. docs/providers/mistral.md:14

• Draft comment:
  Typographical error: In step 2, it should read "Create an API Key:" rather than "Create an API Keys:".
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

6. docs/providers/ollama.md:33

• Draft comment:
  Minor typographical note: In the sentence 'You need to have at least 12k to get decent results, ideally - 32k.', consider removing the space before and after the dash (e.g., 'ideally 32k' or rephrase for clarity). This will make the text look cleaner.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

7. docs/providers/openai-compatible.md:28

• Draft comment:
  Typo: 'Chooose a model' should be corrected to 'Choose a model'.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

8. docs/providers/openai-compatible.md:17

• Draft comment:
  Inconsistency: The text on line 17 states "configure two main settings", but then three items (Base URL, API Key, Model ID) are listed. Please adjust the description or the list to maintain consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

9. docs/providers/requesty.md:7

• Draft comment:
  There is a double space after the period in the sentence ending with 'LLM applications.' (Line 7). Consider using a single space for consistency.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 20% <= threshold 50%
  The comment is about a minor formatting issue, specifically a double space after a period. While consistency in spacing is generally good, this comment is purely informative and does not address a significant issue or provide a meaningful suggestion for improvement. It does not align with the rules for useful comments, which should focus on code functionality, structure, or adherence to development standards.

10. docs/providers/requesty.md:14

• Draft comment:
  The link text for "API Management" has a trailing space (Line 14). Removing the extra space could help maintain consistent formatting.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

11. docs/providers/unbound.md:19

• Draft comment:
  Typographical error: The sentence 'Unbound allows you configure a list of supported models in your application...' is missing the word 'to'. It should read 'Unbound allows you to configure a list of supported models in your application...'
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_yceu9SEVAMT7Lfum

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.