From 637ad1fdcb0188901d4d856d7a3c3b9b74c51c15 Mon Sep 17 00:00:00 2001
From: Mert <101130780+mertalev@users.noreply.github.com>
Date: Mon, 31 Mar 2025 12:34:29 -0400
Subject: [PATCH] docs: minor typo (#17258)

three -> two
---
 docs/docs/features/searching.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/features/searching.md b/docs/docs/features/searching.md
index 7c7e387218..0ee1d01000 100644
--- a/docs/docs/features/searching.md
+++ b/docs/docs/features/searching.md
@@ -62,7 +62,7 @@ The first step of choosing the right model for you is to know which languages yo
 
 If your users will only search in English, then the [CLIP][huggingface-clip] section is the first place to look. This is a curated list of the models that generally perform the best for their size class. The models here are ordered from higher to lower quality. This means that the top models will generally rank the most relevant results higher and have a higher capacity to understand descriptive, detailed, and/or niche queries. The models are also generally ordered from larger to smaller, so consider the impact on memory usage, job processing and search speed when deciding on one. The smaller models in this list are not too different in quality and many times faster.
 
-[Multilingual models][huggingface-multilingual-clip] are also available so users can search in their native language. Use these models if you expect non-English searches to be common. They can be separated into three search patterns:
+[Multilingual models][huggingface-multilingual-clip] are also available so users can search in their native language. Use these models if you expect non-English searches to be common. They can be separated into two search patterns:
 
 - `nllb` models expect the search query to be in the language specified in the user settings
 - `xlm` and `siglip2` models understand search text regardless of the current language setting