clarify sentence2

v-thpra · v-thpra · commit 8a663fdbfee7 · 2025-03-11T12:31:28.000-07:00
diff --git a/learn-pr/aspnetcore/introduction-dotnet-aspire/includes/3-learn-about-components.md b/learn-pr/aspnetcore/introduction-dotnet-aspire/includes/3-learn-about-components.md
@@ -1,4 +1,4 @@
-Although each microservice in your app is likely to be unique, they frequently have similar requirements for backing services such as databases and caches. It can be challenging to write code in each microservice that interfaces with these backing services. In .NET Aspire, that code is reduced as you add a .NET Aspire integration instead. There are built-in integrations in .NET Aspire for many common backing requirements that you're likely to need in microservices.
+Although each microservice in your app is likely to be unique, they frequently have similar requirements for backing services such as databases and caches. It can be challenging to write code in each microservice that interfaces with these backing services. There are built-in integrations in .NET Aspire for many of the common backing requirements that you're likely to need in microservices. With .NET Aspire, your code is reduced as you add a .NET Aspire integration instead.
 
 Imagine you work for an outdoor clothing and equipment company. Your development teams are beginning to design their microservices for the new eShop web app. Each microservice might need services such as databases, messaging services, and caches. You want to assess how .NET Aspire can help interact with these services.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-Although each microservice in your app is likely to be unique, they frequently have similar requirements for backing services such as databases and caches. It can be challenging to write code in each microservice that interfaces with these backing services. In .NET Aspire, that code is reduced as you add a .NET Aspire integration instead. There are built-in integrations in .NET Aspire for many common backing requirements that you're likely to need in microservices.`
	`1`	`+Although each microservice in your app is likely to be unique, they frequently have similar requirements for backing services such as databases and caches. It can be challenging to write code in each microservice that interfaces with these backing services. There are built-in integrations in .NET Aspire for many of the common backing requirements that you're likely to need in microservices. With .NET Aspire, your code is reduced as you add a .NET Aspire integration instead.`
`2`	`2`
`3`	`3`	`Imagine you work for an outdoor clothing and equipment company. Your development teams are beginning to design their microservices for the new eShop web app. Each microservice might need services such as databases, messaging services, and caches. You want to assess how .NET Aspire can help interact with these services.`
`4`	`4`