From 4f70f74cda61cfcca03cb0dab44f28d698a32222 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Sun, 28 Jan 2024 22:09:00 +0000
Subject: [PATCH] Auto-fix Markdown files

---
 rules/use-mass-transit/rule.md | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/rules/use-mass-transit/rule.md b/rules/use-mass-transit/rule.md
index ab7ac23518b..e2d1a9ecbba 100644
--- a/rules/use-mass-transit/rule.md
+++ b/rules/use-mass-transit/rule.md
@@ -23,18 +23,19 @@ When building distributed applications messaging is a common pattern to use.  Of
 ✅ Open-source and free to use
 ✅ Enables swapping of messaging transports by providing a common abstraction layer
 ✅ Supports multiple messaging concepts
-  * Point-to-Point
-  * Publish/Subscribe
-  * Request/Response
+
+* Point-to-Point
+* Publish/Subscribe
+* Request/Response
 ✅ Supports multiple messaging transports
-  * In-Memory
-  * RabbitMQ
-  * Azure Service Bus
-  * Amazon SQS
-  * ActiveMQ
-  * Kafka
-  * gRPC
-  * SQL/DB
+* In-Memory
+* RabbitMQ
+* Azure Service Bus
+* Amazon SQS
+* ActiveMQ
+* Kafka
+* gRPC
+* SQL/DB
 ✅ Supports complex messaging patterns such as Sagas
 
 ## Scenarios