From 59b477645cc1b09d2ca2acd836dddfab36e47da5 Mon Sep 17 00:00:00 2001 From: orangeng <33560939+orangeng@users.noreply.github.com> Date: Sun, 5 Oct 2025 19:53:09 -0700 Subject: [PATCH] [Doc] Edited minor typo (#26266) Signed-off-by: Orange Ng --- docs/design/plugin_system.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/plugin_system.md b/docs/design/plugin_system.md index 37193809776a..a384c6289f4f 100644 --- a/docs/design/plugin_system.md +++ b/docs/design/plugin_system.md @@ -49,7 +49,7 @@ Every plugin has three parts: - **Platform plugins** (with group name `vllm.platform_plugins`): The primary use case for these plugins is to register custom, out-of-the-tree platforms into vLLM. The plugin function should return `None` when the platform is not supported in the current environment, or the platform class's fully qualified name when the platform is supported. -- **IO Processor plugins** (with group name `vllm.io_processor_plugins`): The primary use case for these plugins is to register custom pre/post processing of the model prompt and model output for poling models. The plugin function returns the IOProcessor's class fully qualified name. +- **IO Processor plugins** (with group name `vllm.io_processor_plugins`): The primary use case for these plugins is to register custom pre/post processing of the model prompt and model output for pooling models. The plugin function returns the IOProcessor's class fully qualified name. ## Guidelines for Writing Plugins