ok

Signed-off-by: Takeshi Yoneda <[email protected]>
envoyproxy · Dec 18, 2024 · c6fe488 · c6fe488
1 parent e668b35
commit c6fe488
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/api/v1alpha1/api.go b/api/v1alpha1/api.go
@@ -13,7 +13,7 @@ import (
 // This serves as a way to define a "unified" LLM API for a Gateway which allows downstream
 // clients to use a single schema API to interact with multiple LLM backends.
 //
-// The `inputSchema` is used to determine the structure of the requests that the Gateway will
+// The inputSchema field is used to determine the structure of the requests that the Gateway will
 // receive. And then the Gateway will route the traffic to the appropriate LLMBackend based
 // on the output schema of the LLMBackend while doing the other necessary jobs like
 // upstream authentication, rate limit, etc.

diff --git a/manifests/charts/ai-gateway-helm/crds/aigateway.envoyproxy.io_llmroutes.yaml b/manifests/charts/ai-gateway-helm/crds/aigateway.envoyproxy.io_llmroutes.yaml
@@ -23,7 +23,7 @@ spec:
           This serves as a way to define a "unified" LLM API for a Gateway which allows downstream
           clients to use a single schema API to interact with multiple LLM backends.
 
-          The `inputSchema` is used to determine the structure of the requests that the Gateway will
+          The inputSchema field is used to determine the structure of the requests that the Gateway will
           receive. And then the Gateway will route the traffic to the appropriate LLMBackend based
           on the output schema of the LLMBackend while doing the other necessary jobs like
           upstream authentication, rate limit, etc.