From 9b91e719e9598ab758fc40d08ef0e1543783301f Mon Sep 17 00:00:00 2001
From: minsungoh <167170885+minsungoh@users.noreply.github.com>
Date: Wed, 21 Aug 2024 14:53:46 +0900
Subject: [PATCH] remove unused asterisk

---
 content/engine/swarm/key-concepts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/engine/swarm/key-concepts.md b/content/engine/swarm/key-concepts.md
index f790047c1a..c6b7035872 100644
--- a/content/engine/swarm/key-concepts.md
+++ b/content/engine/swarm/key-concepts.md
@@ -49,7 +49,7 @@ including nodes, services, tasks, and load balancing.
 A node is an instance of the Docker engine participating in the swarm. You can also think of this as a Docker node. You can run one or more nodes on a single physical computer or cloud server, but production swarm deployments typically include Docker nodes distributed across multiple physical and cloud machines.
 
 To deploy your application to a swarm, you submit a service definition to a
-manager node*. The manager node dispatches units of work called
+manager node. The manager node dispatches units of work called
 [tasks](#services-and-tasks) to worker nodes.
 
 Manager nodes also perform the orchestration and cluster management functions