From 6f06bb10b632701e911f02d6e8da22012480cff0 Mon Sep 17 00:00:00 2001
From: ChrisluRoblox <95021397+ChrisluRoblox@users.noreply.github.com>
Date: Wed, 9 Feb 2022 02:00:22 -0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FAQ.md b/FAQ.md
index 5ac5be1..df47aad 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -54,7 +54,7 @@ It is also important to leave some disk space for a couple of volume size, so th
 
 If one volume has large number of small files, the memory usage would be high in order to keep each entry in memory or in leveldb.
 
-To reduce memory usage, one way is to convert the older volumes into Erasure-Coded volumes, which are read only. The volume server can will sort the index and store it as a sorted index file (with extension `.sdx`). So looking up one entry costs a binary search within the sorted index file, instead of O(1) memory lookup.
+To reduce memory usage, one way is to convert the older volumes into [Erasure-Coded volumes](https://github.com/chrislusf/seaweedfs/wiki/Erasure-Coding-for-warm-storage), which are read only. The volume server can will sort the index and store it as a sorted index file (with extension `.sdx`). So looking up one entry costs a binary search within the sorted index file, instead of O(1) memory lookup.
 
 ### How to configure volumes larger than 30GB?