From 4e9d7fd5ac5b75a6b14c542a1d85cf1a27c6ec34 Mon Sep 17 00:00:00 2001 From: Ryan Nowak Date: Tue, 16 Mar 2021 20:57:27 -0700 Subject: [PATCH] Update daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-tye.md Co-authored-by: Aaron Crawfis --- .../dotnet-development/dotnet-development-tye.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-tye.md b/daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-tye.md index 621e74c2..0517e66d 100644 --- a/daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-tye.md +++ b/daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-tye.md @@ -16,9 +16,9 @@ Tye is advantageous for a .NET Dapr developer because: - Tye understands .NET's conventions and requires almost no configuration for .NET services - Tye can manage the lifetime of your dependencies in containers -**Pro:** Tye can automate all of the steps described above. You no longer need to think about concepts like ports or app-ids. - -**Pro:** Since Tye can also manage containers for you, you can make those part of the application definition and stop the long-running containers on your machine. +Pros/cons: +- **Pro:** Tye can automate all of the steps described above. You no longer need to think about concepts like ports or app-ids. +- **Pro:** Since Tye can also manage containers for you, you can make those part of the application definition and stop the long-running containers on your machine. ### Using Tye