From 1bb2590e964f5cc4cc45c66db868046813d4f013 Mon Sep 17 00:00:00 2001
From: Liisa Lado-Villar <47525503+lilachic@users.noreply.github.com>
Date: Wed, 15 Nov 2023 10:48:22 +0200
Subject: [PATCH] fix typo

---
 docs/guides/deploy-k8s.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guides/deploy-k8s.md b/docs/guides/deploy-k8s.md
index a406cc5..60811bf 100644
--- a/docs/guides/deploy-k8s.md
+++ b/docs/guides/deploy-k8s.md
@@ -22,8 +22,8 @@ This guide explains how to deploy the Sensitive Data Archive (SDA) in kubernetes
 For secure deployment of the system one can think it by what can be accessed from where, for all ways of deploying two trust boundaries can be used, external and internal. For an extra layer of security also the storage trust boundary can be separate. The service is provided for customers on the internet therefore an example of deploying the service is using two separate Kubernetes clusters, one for responding customers and other communication outside, and the other cluster is more secure storage facing internal cluster. One thing to consider is where to release the data, that could be closed protected environment with tightly restricted access, Data out can be put in internal cluster.
 
 The services could be divided into two trust boundaries
-- The services in external in external cluster are Inbox and MQ
-- The services in internal cluster are  Intercept, Ingest, Verify, Mapper, Finalize, Backup and Data out.
+- The services in external cluster are Inbox and MQ
+- The services in internal cluster are Intercept, Ingest, Verify, Mapper, Finalize, Backup and Data out.
 
 The innermost trust zone contains the database and the archive, which be accessed only from internal cluster.