From ad5c6d836eb4149efd41346ad0613e37707a823a Mon Sep 17 00:00:00 2001
From: XingLu Wang <95828202+xingluw@users.noreply.github.com>
Date: Wed, 22 Feb 2023 10:46:52 -0800
Subject: [PATCH] Update service-discovery.mdx (#2995)

---
 website/content/docs/concepts/service-discovery.mdx | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/website/content/docs/concepts/service-discovery.mdx b/website/content/docs/concepts/service-discovery.mdx
index a37e4dec1..8d145531e 100644
--- a/website/content/docs/concepts/service-discovery.mdx
+++ b/website/content/docs/concepts/service-discovery.mdx
@@ -40,8 +40,7 @@ infrastructure providers into Boundary. Boundary hosts are automatically
 created, updated and added to host sets in order to reflect the connection 
 information maintained in these providers. This removes the need to know 
 host connection info or reapply infrastructure as code templates to 
-configure new or changed resources.This removes the need to know host connection 
-info or reapply infrastructure as code templates to configure new or changed resources.
+configure new or changed resources.
 
 # Dynamic Host Catalogs
 Dynamic host catalogs are an agentless workflow for Boundary to 
@@ -56,4 +55,4 @@ external resources should be ingested into the catalog by
 Currently, Boundary supports dynamic host catalog implementations for AWS and 
 Azure and we will continue to grow this ecosystem to support additional providers. 
 
-You can get started with dynamic host catalogs [here](/boundary/tutorials/access-management/azure-host-catalogs).
\ No newline at end of file
+You can get started with dynamic host catalogs [here](/boundary/tutorials/access-management/azure-host-catalogs).