From fbbf997e174c56c9de47b89544ba9dc11d5a9bf2 Mon Sep 17 00:00:00 2001
From: cycneuramus <56681631+cycneuramus@users.noreply.github.com>
Date: Tue, 10 Jan 2023 18:08:47 +0100
Subject: [PATCH] Remove redundant heading

---
 SeaweedFS-in-Docker-Swarm.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/SeaweedFS-in-Docker-Swarm.md b/SeaweedFS-in-Docker-Swarm.md
index 0bfee46..7a7fc21 100644
--- a/SeaweedFS-in-Docker-Swarm.md
+++ b/SeaweedFS-in-Docker-Swarm.md
@@ -1,5 +1,3 @@
-# Docker Swarm
-
 This is an example stack for a Docker Swarm consisting of three nodes (`node1, node2, node3`). There is one SeaweedFS [Master](https://github.com/seaweedfs/seaweedfs/wiki/Components#master-service) in total, with one [Filer](https://github.com/seaweedfs/seaweedfs/wiki/Components#filer-service) per node and one [Volume](https://github.com/seaweedfs/seaweedfs/wiki/Components#volume-concept) per node as well. The Filers are configured to prefer writing to Volumes on the same node as itself—if one exists—and likewise with the globally deployed [Mounts](https://github.com/seaweedfs/seaweedfs/wiki/Components#volume-concept) (see "Optional Services" below) preferring to connect to a local Filer. 
 
 The settings and configurations are just examples. Here, for instance, the default is a volume replication of `200`, meaning that all writes will be replicated on two nodes on two different datacenters. In the case of our example three nodes, this means the same volumes will be present on every node. Additionally, volumes are configured to be smaller (`1 GB`) than the default (`30 GB`), garbage collection is more aggressive than usual (`-garbageThreshold=0.01`), and the Filers are configured to use `leveldb3` as an embedded store for easy [replication](https://github.com/seaweedfs/seaweedfs/wiki/Filer-Store-Replication).