From a568b4e2110a145f8a96c81ab5e7e6017b0d4612 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Thu, 22 Feb 2024 05:05:20 -0800
Subject: [PATCH] Update LAB_09b-Implement_Azure_Container_Instances.md

---
 .../Lab/LAB_09b-Implement_Azure_Container_Instances.md        | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/New Instructions/Lab/LAB_09b-Implement_Azure_Container_Instances.md b/New Instructions/Lab/LAB_09b-Implement_Azure_Container_Instances.md
index a564778e..80de5895 100644
--- a/New Instructions/Lab/LAB_09b-Implement_Azure_Container_Instances.md	
+++ b/New Instructions/Lab/LAB_09b-Implement_Azure_Container_Instances.md	
@@ -101,7 +101,9 @@ If you are working with **your own subscription** take a minute to delete the la
 
 Congratulations on completing the lab. Here are the main takeaways for this lab. 
 
-+ Azure Container Instances (ACI) is a service that enables you to deploy containers on the Microsoft Azure public cloud. ACI doesn't require you to provision or manage any underlying infrastructure. The service supports both Linux containers and Windows containers.
++ Azure Container Instances (ACI) is a service that enables you to deploy containers on the Microsoft Azure public cloud.
++ ACI doesn't require you to provision or manage any underlying infrastructure.
++ ACI supports both Linux containers and Windows containers.
 + Workloads on ACI are usually started and stopped by some kind of process or trigger and are usually short-lived. 
 
 ## Learn more with self-paced training