From df03db47ceede7ba7a5434cc59e61729a7dd4cd0 Mon Sep 17 00:00:00 2001 From: John Cowen Date: Mon, 25 Jun 2018 11:33:07 +0100 Subject: [PATCH] tenenacy > tenancy --- website/source/docs/connect/security.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/connect/security.html.md b/website/source/docs/connect/security.html.md index 7171173d3..182d875dc 100644 --- a/website/source/docs/connect/security.html.md +++ b/website/source/docs/connect/security.html.md @@ -85,7 +85,7 @@ network namespacing techniques provided by the underlying operating system. For scenarios where multiple services are running on the same machine without isolation, these services must all be trusted. We call this the -**trusted multi-tenenacy** deployment model. Any service could theoretically +**trusted multi-tenancy** deployment model. Any service could theoretically connect to any other service via the loopback listener, bypassing Connect completely. In this scenario, all services must be trusted _or_ isolation mechanisms must be used.