fix(docs): typo of docs in loadtest

[highpon]

Description

This PR fixes typo of docs in loadtest.

Related Issue

None

Versions

• Vald Version: v1.7.15
• Go Version: v1.23.4
• Rust Version: v1.83.0
• Docker Version: v27.4.0
• Kubernetes Version: v1.32.0
• Helm Version: v3.16.3
• NGT Version: v2.3.5
• Faiss Version: v1.9.0

Checklist

• I have read the CONTRIBUTING document and completed our CLA agreement.
• I have checked open Pull Requests for the similar feature or fixes?

Special notes for your reviewer

Summary by CodeRabbit

• Documentation
  • Corrected terminology in load testing documentation from "steamsearch" to "streamsearch" to improve clarity of configuration options.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves a minor documentation correction in the docs/performance/loadtest.md file. Specifically, the change corrects a typo in the operation configuration option, replacing the term "steamsearch" with the correct spelling "streamsearch". This modification ensures accurate terminology in the load testing tools documentation, helping users understand the available operations more precisely.

Changes

File	Change Summary
docs/performance/loadtest.md	Corrected typo from "steamsearch" to "streamsearch" in the operation configuration example

Possibly related PRs

• fix links #2500: Fixing links in documentation
• fix indent and link #2501: Link modifications in documentation
• fix link #2502: Hyperlink reference correction
• fix: typo in index job #2708: Typo fix in index job documentation

Suggested labels

type/documentation, priority/low, size/S

Suggested reviewers

• kmrmt
• datelier

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c73960 and a09e90c.

📒 Files selected for processing (1)

• docs/performance/loadtest.md (1 hunks)

🔇 Additional comments (1)

docs/performance/loadtest.md (1)

36-36: LGTM! Typo fix looks correct.

The correction from "steamsearch" to "streamsearch" makes sense and improves documentation accuracy.

Let's verify if this typo appears elsewhere in the codebase:

✅ Verification successful

Typo fix verified - no other instances found

The correction from "steamsearch" to "streamsearch" is consistent with the rest of the codebase, where "streamsearch" is used throughout the API definitions, implementations, and documentation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any remaining instances of the typo
rg -i "steamsearch"

# Search for correct term to ensure consistency
rg -i "streamsearch"

Length of output: 52195

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.