s/feature/use-case

library/ai-gateway/index.md

@@ -37,7 +37,7 @@ Because the API of the AI-gateway will be consumed by a wide variety
 of GitLab instances, it is important that we design a stable, yet
 flexible API.
 
-To do this, we can implement an API-endpoint per feature we
+To do this, we can implement an API-endpoint per use-case we
 build. This means that the interface between GitLab and the AI-gateway
 is one that we build and own, and we don't tie ourselves to the
 AI-provider used for a certain feature. This will allow us to change
@@ -77,7 +77,7 @@ GitLab instances, they differ on these items:
 features that already partially exist does not mean we need to exclude
 new features using gRPC or Websockets. For example: Chat features
 might be better served by streaming requests and responses. Since we
-are suggesting an endpoint per feature, different features could also
+are suggesting an endpoint per use-case, different features could also
 opt for different protocols, as long as we keep cross-version
 compatibility in mind.