From 5cc5d710dd65a8926f1c81d3b0e8ce742f2f625a Mon Sep 17 00:00:00 2001
From: VBouiller <31282661+vbouiller@users.noreply.github.com>
Date: Tue, 23 Apr 2024 14:34:24 +0200
Subject: [PATCH] Fix CLI typo in recommended-architecture.mdx (#4694)

---
 .../install-boundary/architecture/recommended-architecture.mdx  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/install-boundary/architecture/recommended-architecture.mdx b/website/content/docs/install-boundary/architecture/recommended-architecture.mdx
index 138c5c41b..96e1e2af5 100644
--- a/website/content/docs/install-boundary/architecture/recommended-architecture.mdx
+++ b/website/content/docs/install-boundary/architecture/recommended-architecture.mdx
@@ -11,7 +11,7 @@ Boundary has two main user workflows to consider when you deploy it to productio
 
 ## Administrative workflow
 
-The first is the Boundary administration workflow, where an administrator uses either the Boundary CI or GUI to configure Boundary.
+The first is the Boundary administration workflow, where an administrator uses either the Boundary CLI or GUI to configure Boundary.
 In this scenario, the administrator interfaces solely with the Boundary controllers, and a load balancer can be used to balance requests across multiple controllers.
 The Boundary controllers do not directly communicate with one another, all configuration and state is managed through an RDBMS, in this case PostgreSQL.