From 84acf358d4038763008182f356a8f4a9a877426e Mon Sep 17 00:00:00 2001
From: Xiang Dai <764524258@qq.com>
Date: Thu, 13 Feb 2020 09:37:45 +0800
Subject: [PATCH] feedback

Signed-off-by: Xiang Dai <764524258@qq.com>
---
 docs/sharding.md | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/docs/sharding.md b/docs/sharding.md
index d450f9bd650..652d95b8126 100644
--- a/docs/sharding.md
+++ b/docs/sharding.md
@@ -2,14 +2,10 @@
 title: Sharding
 type: docs
 menu: thanos
-slug: /Sharding.md
+slug: /sharding.md
 ---
 
-# Store and Compactor Sharding
-
-Store and Compactor Sharding is for Long Term Retention Storage.
-
-## Background
+# Background
 
 Currently all components that read from object store assume that all the operations and functionality should be done based
 on **all** the available blocks that are present in the certain bucket's root directory.
@@ -21,7 +17,7 @@ This means that with time you might want to scale out certain components e.g:
 
 * Compactor: Larger number of objects does not matter much, however compactor has to scale (CPU, network, disk, memory) with number of Sources pushing blocks to the object storage.
 
-### Relabelling
+# Relabelling
 
 Similar to [promtail](https://github.com/grafana/loki/blob/master/docs/promtail.md#scrape-configs) this config will follow native
 [Prometheus relabel-config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) syntax.
@@ -60,6 +56,8 @@ Example usages would be:
 
 We can shard by adjusting which labels should be included in the blocks.
 
-### Time Partitioning
+# Time Partitioning
 
 For store gateway, we can specify `--min-time` and `--max-time` flags to filter for what blocks store gateway should be responsible for.
+
+More details can refer to "Time based partitioning" chapter in  [Store gateway](components/store.md).