diff --git a/hadoop-hdds/docs/content/feature/Quota.md b/hadoop-hdds/docs/content/feature/Quota.md
index 19b8930946d..9f243f49921 100644
--- a/hadoop-hdds/docs/content/feature/Quota.md
+++ b/hadoop-hdds/docs/content/feature/Quota.md
@@ -45,6 +45,8 @@ e. If the cluster is upgraded from old version less than 1.1.0, use of quota on
 
 f. If volume's quota is enabled then bucket's quota cannot be cleared. 
 
+g. Volume having linked bucket do not consume space quota for keys within linked bucket. Linked bucket keys will consume space quota of source volume and source bucket.
+
 2. Namespace quota
 
 Administrators should be able to define how many namespace a Volume or Bucket can use. The following settings for namespace quota are supported: 
@@ -55,9 +57,14 @@ b. When volume namespace quota is enabled, the total number of buckets under the
 
 c. When bucket namespace quota is enabled, the total number of keys under the bucket, cannot exceed the bucket namespace quota.
 
-d. Linked buckets do not consume namespace quota.
+d. Linked buckets do not define separate namespace quota, it is referred by namespace quota of source bucket for keys inside linked bucket.
+
+e. Linked bucket will consume namespace quota of volume.
+
+f. If the cluster is upgraded from old version less than 1.1.0, use of quota on older volumes and buckets(We can confirm by looking at the info for the volume or bucket, and if the quota value is -2 then volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's namespace quota, the quota setting is inaccurate at this point.
 
-e. If the cluster is upgraded from old version less than 1.1.0, use of quota on older volumes and buckets(We can confirm by looking at the info for the volume or bucket, and if the quota value is -2 then volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's namespace quota, the quota setting is inaccurate at this point.
+### Note:
+- For FSO bucket with recursive deletion of directory, release of quota happens asynchronously after sub directories and files are removed (when directory is removed, recursive deletion can be in-progress in background).
 
 ## Client usage
 ### Storage Space level quota
diff --git a/hadoop-hdds/docs/content/feature/Quota.zh.md b/hadoop-hdds/docs/content/feature/Quota.zh.md
index a92ce434cc2..f00b3f64649 100644
--- a/hadoop-hdds/docs/content/feature/Quota.zh.md
+++ b/hadoop-hdds/docs/content/feature/Quota.zh.md
@@ -43,6 +43,8 @@ menu:
  
  f. 如果volume quota被启用，那么bucket quota将不能被清除。
 
+ g. Volume内的linked bucket不消耗Volume的空间配额。linked bcuket将消耗源Volume和源Bucket的空间配额。
+
 2. 命名空间配额
 
  管理员应当能够定义一个Volume或Bucket可以使用多少命名空间。目前支持命名空间的配额设置为：
@@ -53,9 +55,14 @@ menu:
 
  c. 当bucket的命名空间配额启用时，该bucket的key数目不能超过此配额。
 
- d. Linked bucket不消耗命名空间配额。
+ d. Linked bucket 上不支持定义单独的命名空间配额，它直接引用源bucket的命名空间配额。
+
+ e. Linked bucket将消耗卷的命名空间配额。
+
+ f. 如果集群从小于1.1.0的旧版本升级而来，则不建议在旧volume和bucket(可以通过查看volume或者bucket的info确认，如果quota值是-2，那么这个volume或者bucket就是旧的)上使用配额。由于旧的key没有计算到bucket的命名空间配额中，所以此时配额设置是不准确的。
 
- e. 如果集群从小于1.1.0的旧版本升级而来，则不建议在旧volume和bucket(可以通过查看volume或者bucket的info确认，如果quota值是-2，那么这个volume或者bucket就是旧的)上使用配额。由于旧的key没有计算到bucket的命名空间配额中，所以此时配额设置是不准确的。
+### 笔记
+- 对于FSO bucket，当递归删除目录时，配额将在子目录和文件被异步删除后释放（当目录被删除时，递归删除在后台进行）。
 
 ## 客户端用法
 ### Storage space级别配额